Skip to main content

Overriding the Salesforce Contact or Lead Creation Rules

Override the default rules when contacts or leads are created or updated in Salesforce

Ariane Ramirez avatar
Written by Ariane Ramirez
Updated over 2 weeks ago

Override the Default Contact or Lead Creation Rules

Aside from customizing your update policy for each mapped field, we have other options to override the default contact or lead creation rules depending on you needs.

Before You Begin

Before you begin make sure you've already done the following:


Override Settings in the Salesforce Configure Menu

Below are some settings you can enable to change some contact/lead creation rules. This can be done through the Configure Salesforce Mapping menu.

  • Go to Settings > Integrations in your event's admin console

  • Click Configure under Salesforce

  • Go to the Contact or Lead Creation section

By default, these toggles are turned off in this section. You can enable them if it applies to your integration goals.

Overriding Feature

What happens when the toggle is turned on?

Create a new contact or lead for every ticket holder

When the toggle is turned on, a new contact or lead will be created regardless of whether it’s a duplicate registration or if a matching contact or lead exists.

Notes:

  • This may create duplicate contact and lead records if this is enabled

  • This should be enabled if you want Add On purchases to have a Salesforce record

  • If you're using this feature, please map the "Ticket Id" in the configure menu so that if updates are done to attendees with multiple tickets, the correct Salesforce record will be updated.

Create a contact or lead for the ticket buyer if it doesn't exist

Turn this on to create a contact/lead record for the TICKET BUYER if there is no linear record with a matching email address. This toggle also adds the ticket buyer as a campaign member.

Note: The default rule is that a contact/lead record will only be created for TICKET HOLDERS, so turning this on will create a record even if the ticket buyer is not a ticket holder as long as the record does not exist.

Other Rules when this is enabled:

  • The TICKET BUYER is added as a campaign member.

  • It will not update the existing record with a matching email, even if there are valid mapped items.

  • If a new record is created, the Ticket Name, Ticket ID, Paid Amount, and Barcode ID will not be added to the TICKET BUYER'S contact/lead record, even if it's mapped, as these are the ticket holder's information. It will update the other mapped items.

Create a new contact or lead when the existing ticket holder's email address is updated in the order

Turn this on to create a new contact/lead instead of updating the existing record when the ticket holder's email address is changed in the order.

We recommend turning this on so that if someone buys multiple tickets under 1 email address, new records will be created when the buyer updates the order with the attendees' email addresses and information.

Create a new contact/lead for add-on purchases

Turn this on if you want a new record to be created for the add-on purchase. This will cause duplicate records in your Salesforce account.

Cross Matching Records

The Cross Matching Records feature is an optional setting that overrides the default rules and behavior when contacts or leads are created or updated in Salesforce. Instead of just searching for linear matches, it searches both contacts and leads for matches, and you may also add more criteria for matching aside from the email address.


Create Contacts or Leads for Attendees Without Email Addresses

If you allow the attendee's email address to be left blank during registration, contact or lead records will not be created for these attendees. To ensure records without email addresses are created, follow the steps below:

  • In the configure menu, map the Ticket ID for the contact or lead

  • In the configure menu, map the Ticket ID for the campaign member

  • In the configure menu, enable the toggle to Create a new contact or lead when the ticket holder's email address is updated in the order

Notes:

  • If the attendee email is blank, it will create a Salesforce record.

  • If the attendee's last name and email are blank, it will create a Salesforce record with the attendee's first name and the buyer's last name.

  • If the attendee's first name and email are blank, it will not create a Salesforce record.

  • When updates are done to the order, the created Salesforce record will update too.

  • If the first name, last name, and email were left blank during registration, and the first name and last name are updated after registration, no new Salesforce record will be created; it will only trigger a creation when the email address is added. We're improving this behavior. Stay tuned for updates.

Did this answer your question?