Mappings

You can map Eventbrite Attendee fields to Salesforce Leads and Contacts. You can also create and update Salesforce Leads, Contacts, Accounts, Campaigns and Campaign Members for Eventbrite Attendees. By default this is all turned off so we do not impact your Salesforce data.

Mappings for Leads / Contacts and Campaigns

  • On the Salesforce App Launcher Select Eventbrite Admin, then select the Evenbrite Settings tab
  • On the left side of the page select Mappings
  • At the top of the screen you will notice the page is split between Leads / Contacts and Campaigns
  • The page shows three main headings and steps you can amend but are all optional: Matching Rules, Creation Rule, Mappings.
  • To unlock the page to make changes to each section, on the top right of the page click Edit.

Matching Rules for Leads and Contacts

  • The first step is to decide how you want to match Eventbrite Attendees to Salesforce records.
  • The default match is made by using the standard Salesforce email address field found on the Contact or Lead objects. For many customers this is enough but you can choose to build your own Salesforce Duplication and Matching Rules and use those instead.
  • Once you have clicked Edit on the top right hand side of the screen, under matching rules you can click on the arrows to select the two options to match leads and contacts by.
  • Remember to Save any changes before leaving the page
  • If you are not familiar with Salesforce Matching Rules click here. You need to have configured both Salesforce Duplication Rules and Salesforce Matching Rules. You can test these rules by simply manually enter Leads or Contacts in Salesforce and checking if you rules warn you of matches.

Creation Rule

As mentioned above by default we do not create records on standard Salesforce objects without your input. Auto create Lead, Contacts, Accounts and Campaigns using the steps below.

  1. The first step is to choose what to do if no match can be made.  

  2. If you choose to create Lead Records then simply select Create a Lead the icon next to the dropdown box is optional it allows you to select a Salesforce Lead record type.

  3. If you choose to create a Contact the process is slightly more complex. Generally Salesforce requires a contact to be linked to  an Account.

  4. In addition to creating a Contact we can also match to an existing Salesforce Account, using the Eventbrite Company Field or Salesforce matching rules.

  5. If no match can be found the integration can create the Account. If you decide to create an Account you can specify how the name is built up the default is [Company]. The value is encased in [ ] to allow you to specify a variable in this case the Eventbrite Company. You can also put plain text in e.g. Eventbrite Account or combine the two to give you [Company] Eventbrite Account

  6. In addition to creating a Contact we can also match to an existing Salesforce Account, using the Eventbrite Company Field or Salesforce matching rules.

Mapping Rules for Leads and Contacts

Mappings are split between Leads and Contacts but the process for each is identical. You can either manually select which fields correspond or click the Auto Map button which will align fields based on name.

  1. If you need to reset the mappings simply click Clear Mappings.

  2. Validate is a useful feature that will allow you to test to see if a record can be updated or created. Once validated a message will appear showing you any mapping errors.

  3. Default Values are useful if you want to update a Salesforce field but do not have a value in Eventbrite. For example if an event was for one company and you were not capturing that information you could set a default value.

  4. First you need to choose what to do if no match can be made.  

  5. If you choose to create lead records then simply select Create a Lead the icon next to the dropdown box is optional it allows you to select a Salesforce Lead record type.

  6. If you choose to Create a Contact the process is slightly more complex. Generally Salesforce requires a contact to be linked to a an Account.

  7. In addition to creating a Contact we can also match to an existing Salesforce Account, using the Eventbrite Company field or Salesforce matching rules.

  8. If no match can be found, the integration can create the Account. If you decide to create an Account you can specify how the name is built up the default is [Company]. The value is encased in [ ] to allow you to specify a variable in this case the Eventbrite Company. You can also put plain text in e.g. Eventbrite Account or combine the two to give you [Company] Eventbrite Account

  9. In addition to creating a Contact we can also match to an existing Salesforce Account, using the Eventbrite Company field or Salesforce matching rules.

Campaigns Mappings and Campaign Statuses

In Campaign Settings you can choose to activate auto create Salesforce Campaigns from your Eventbrite Events and link the two together. Salesforce Campaigns will be created when the main sync runs. Mappings are split between Campaign Mappings and Campaign Statuses.

When an Eventbrite Event is linked to a Salesforce Campaign it will use these mappings to update the Salesforce Campaign fields. This happens each time the sync runs.

  1. If you need to reset the mappings simply click Clear Mappings.

  2. You can either manually select which fields correspond or click the Auto Map button which will align fields based on name.

  3. Validate is a useful feature that will allow you to test to see if a record can be updated or created. Once validated a message will appear showing you any mapping errors.

  4. Default Values are useful if you want to update a Salesforce field but do not have a value in Eventbrite. For example if an event was for one company and you were not capturing that information you could set a default value.

Campaign Statuses

The Eventbrite sync can auto create Salesforce Member Statuses and map them based on Eventbrite attendee statuses. In some cases you may only want the status to be updated once. This avoids manual status updates being overridden by the primary Eventbrite sync.

In this article