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

Salesforce integration set up

This contains all the useful information to help you easily join your Salesforce org with Emma and start mapping data from one to the other.

A. Connecting Emma to your Salesforce Org

Follow the steps below to initiate your integration with Salesforce:

  • Go to Accounts > Integrations section on your Emma menu on the lefthand side
  • Click Add Integration
  • Select Salesforce
  • Connect your Salesforce org by using your my.salesforce URL – see below an example
  • Once connected make it Active and Save
  • You can then connect an event, and select the fields that you want to map across to the Campaign (event) and opportunity (activity type). See section B below for more information on mapping.
    • Note: If you have multiple events in Emma, we suggest starting with a single event as All Events will be difficult for you to check. All Events can be enabled once you have got the mapping correctly configured and tested.

B) Suggested order of field mapping

The recommended order of Salesforce Actions depends on how much has been set up on EMMA/Salesforce to ensure the ID's are correctly sync'd.

  1. If the Salesforce Campaign has already been created but the event doesn't exist in Emma then the 'Read Events Details From Salesforce' action can be used to create the event in Emma.
  2. If the Salesforce Campaign has already been created and the Event exists in Emma then you will need to manually copy the Salesforce ID of the Campaign into the Event. This is done under Settings > Integration by setting the CRM as Salesforce and then inputting the Campaign ID into the CRM UID field.

 

C) Account, Contact and Activity Type mapping 

  1. If Salesforce Accounts are required the next action would be: 'Read Guest Account Details From Salesforce'. 
    1. The export Salesforce action would be: 'Send Guest Account Details To Salesforce'.
  2. If Salesforce Contacts are required, the next action would be: 'Read Guest Details From Salesforce'.
    1. The export Salesforce action would be: 'Send Guest Details To Salesforce'.
  3. If Emma Tickets need to be exported to Salesforce, the next action would be: 'Send Ticket Details To Salesforce'.
  4. If Emma Bids need to be exported to Salesforce, the next action would be: 'Send Bid Details To Salesforce'.
  5. If Emma Pledges need to be exported to Salesforce, the next action would be: 'Send Pledge Details To Salesforce'.

 

D) How do datasets work?

Datasets are the linked maps to the Salesforce action. These linked maps determine the tables and fields that will be exported from Emma to Salesforce or vice versa.

 

E) Preventing duplicate contacts

In order to prevent duplicate contacts it is important to first import Contacts from Salesforce into Emma. This way the EMMA guests will be created with the Salesforce ID and any further activity will be linked to this unique ID.

If Contacts already exist in Salesforce and have not been imported into Emma as Guests, the integration will first check if the Guest email matches any Contacts to update before creating a new Contact.

 

F) What is a Daily Cron?

If the Daily cron is enabled the Salesforce Action will be run every day at 08h00 AM (GMT) to ensure the data between Emma and Salesforce remains up to date. 

This is only required where data may be changing or new records are added after the initial sync, for example, new contacts being added to Salesforce that need to be exported to Emma so that the guest records are kept up to date.
 

G) Testing the mapping

On the Salesforce Action, you can use the Row Limit field to set the amount of rows to send to Salesforce. Setting this Row Limit to a low number allows you to test the mapping, ensuring there are no errors and the data is correctly exported to Salesforce.