Skip to content
English
  • There are no suggestions because the search field is empty.

Overview of Custom Objects for Ambassador Salesforce Manage Package

Learn about the custom objects included with the Ambassador Salesforce Managed Package

The Ambassador Managed Package for Admin 3 includes the following custom objects included in the initial and incremental sync. 

  1. Ambassador Setup - Salesforce Admin setup page. *Only in Ambassador Admin app interface

  2. Companies - A table that lists each account you have with Ambassador. Most clients only have one company account. *Only found in Ambassador Admin app interface

  3. Ambassadors - A table of all contact records that exist in your Ambassador account(s). The “ambassador” status can range between enrolled, prospect, unsubscribed, or banned. Within the Ambassador product, you can locate all contacts of all status in the All tab of the Contacts table.

    • If an ambassador record is created in Salesforce, there must be an “External ID” populated on the ambassador salesforce record to confirm it was successfully created in Ambassador as a contact.

    • To find a ambassador’s share link in Salesforce, look at their related objects for “Campaign Member”. They could have one or more depending on your use-case.

  4. Campaigns - A table of each campaign record in your Ambassador account with details about the campaign itself.

  5. Campaign Members - A table of records for each campaign that an enrolled contact is a member of in the Ambassador platform. This record contains their default share link and shortcode for that campaign.

    • The concept of a “Campaign Member” record does not exist in the Ambassador platform UI. Instead, you can look at a contact record in the Ambassador platform and scroll down to the Campaigns section to see which campaigns they are a member of and the sharelink(s) for each.

  6. Segments - A table of all Segments from your Ambassador account. Segments are how contacts are grouped in Ambassador. A contact must have a status of enrolled and be a member of a campaign segment to generate a share link/code. Alternatively, a segment could exist to group contacts outside of a campaign as well.

  7. Segment Members - A table of all records where an ambassador contact is a member of a segment in the Ambassador platform. (ex. If a contact is assigned to 3 segments in Ambassador, they will have 3 segment member records in Salesforce.)

    • A record called “segment member” does not exist in the Ambassador platform, however you can navigate to the Contacts table there and look for the "Segment" column/field or within their Contact record in the Ambassador platform.

  8. Commissions - (only applicable for non v.3 companies using Commissions). If you previously used Ambassador 1 or 2, this is a table of legacy Commission records.

    • If you are a new company that started on v.3 or newer, you will not utilize the Commission object/records.

    • If you are an existing company that will or has migrated to Ambassador v.3, your historical commission records will be mapped to the new v3 objects for Referral Attribution, Orders, and Rewards. Once your migration is complete, you can disable the legacy Ambassador app in Salesforce to hide the Commissions object and utilize the new Ambassador 3 app.

  9. Journeys - If utilized, this object can be used to track and update the current stage of a referred contact in your sales cycle with their journey stage in Ambassador, as well as manually update a “current-step” if needed.

    • In standard practice, we recommend creating a Journey in Ambassador with stages that mirror your sales cycle for referred-contact’s. Then utilize an Ambassador flow template to create Salesforce flow that triggers stage changes of referred contacts to update their “current-step” (journey stage) in Ambassador.

    • The Ambassador Journey feature can also be utilized for other use-cases your team may have for tracking progress stages, such as Case Studies and more.

  10. Referral Attributions - Links a prospect/customer to the advocate who referred them—usually at the first tracked stage a customer takes after clicking a referral link or entering a code.

    • If you are not using a coupon code widget or jsAPI to create the referral attribution from your website, the standard practice is to trigger a Salesforce flow to create a referral attribution at the earliest stage possible in your sales cycle.

  11. Orders - In standard practice, Orders are created when an opportunity is closed won or other final conversion event in your sales cycle.

    • For most use-cases, an Ambassador Flow template is utilized to create an Order in Ambassador when an opportunity is closed won with a referring shortcode. Then, an Ambassador automation is triggered to create rewards, send communications, and more. When an Order is successfully created in Ambassador, the record will sync back to this object with an external ID.

    • Orders will not reflect the final conversion event if your use-case calls for creating the Order at an earlier stage without revenue, such as when the Opportunity is created or another stage is met. If that’s the case, we recommend adding another flow to update the Order with revenue once the final stage/criteria is met so that any Order with revenue can be classified as the final conversion, especially if you are not utilizing Ambassador Journeys.

  12. Rewards - (only available on v.3.23 or later) - This table is a transaction history for all rewards created for a contact in Ambassador, including the status, amount, related order, fulfillment type (once fulfilled), and more.

  13. Logs - An archive of activity and errors associated with the Ambassador to Salesforce sync (Ambassador Admin app interface only)