By default, the integration matches Eventbrite attendees to Salesforce records using the standard email address field. For many customers, this is enough. But if you need more control, you can switch to using your own Salesforce Matching Rules in Mappings settings.

Matching Rules and Duplicate Rules are standard Salesforce platform features. We can't set them up or support building them for you, as this sits outside of what we can help with. Typically your Salesforce administrator or consultant will build them. If you need a recommendation, contact us.

Best Practices

Match on a single rule: We recommend creating a dedicated Matching Rule for the integration, separate from other rules that help avoid duplicates during data entry.

Keep it simple: Simpler Matching Rules are easier to troubleshoot and maintain.

Active Duplicate Rule required: A Matching Rule always needs a corresponding active Duplicate Rule. Without one, matching won't work.

Mapped fields only: The Matching Rule can only include Attendee and Order fields that are mapped to Salesforce object fields (including Default Values). Custom question data can't be included in this matching step, as those are processed after the Salesforce records are upserted.

Testing is key: In Mappings settings, you can test the Matching Rules for each object via the Check Matching Rules button.

Notes on Duplicate Rules

We use the specified Matching Rule during the matching step. After that, any record updates or creates will need to pass all Duplicate Rules that apply to the action (per Duplicate Rule filters) and their related Matching Rules.

We recommend limiting which Duplicate Rules fire during mapping and record creation by filtering them to the integration. For example, filter rules to the sync user or a default lead source.

Duplicate Rules that trigger during Salesforce record upserts should be set to Report Only, not set to block record upserts.

Related Articles