Quantcast

Part 6: SFDC / Eloqua data priority & account linkage

Aug 6, 2020

This is part six of the Eloqua SFDC native integration guide.  To begin this tutorial at the start please use this link.

Configuring Data Priority

Data Priority in Eloqua can be shared by multiple Data Sources, and determines whether Eloqua will update fields based on the priority of the data source as compared to previously used data sources. The Data Priority needs to be configured with the ‘Deleted’ Auto Synchs having the same data priority as the ‘Get’ Auto Synchs. This ensures that Eloqua will blank out the specified ID values and also allows for the ID values to be repopulated should the deleted entity be recreated in SFDC.

To configure Data Priority:

  1. Navigate to Settings > Setup > Integration.
  2. Click the Inbound tab.
  3. From the Management sub-menu, select Data Priority Order. In the Data Import Source Priority make the following changes:
  • Rename the Data Priority Order CRM Integration* to Get CRM Accounts
  • Rename the Data Priority Order CRM Integration* to Get CRM Contacts and change the Evaluation order to after Get CRM Accounts
  • Create a new Data Priority Order for Get CRM Leads and set the Evaluation order to after Get CRM Contacts
    * You can create a new Priority if the recommended Data Import Priority does not exist.
Eloqua Salesforce Integration Data Prority

The Data Priority Order should now look like this:

Eloqua Salesforce integraiton data priority
  1. While in the Inbound tab, click on the Data Source corresponding to each auto synch.
Eloqua Salesforce Data Upload Source
  1. For each data source below, update the priority order as shown below.

Data Source

Data Priority

Get Accounts

Get CRM Accounts

Get Deleted Accounts

Get CRM Accounts

Get Contacts

Get CRM Contacts

Get Deleted Contacts

Get CRM Contacts

Get Leads

Get CRM Leads

Get Deleted Leads

Get CRM Leads

Get Converted Leads

Get CRM Leads

Linking Contacts to Accounts on the System Level

To set up account linkage:

  1. Navigate to Settings > Setup > Account Linkage.
  2. Unless you’ve already linked a contact field to an account field, by default, No Linkage is selected. To map fields, click Link by mapping.

 

Eloqua Salesforce Account Linkage
  1. Select the Contact Field ‘SFDC AccountID’. Click on the button, then search for and select the field in the Search window. Click OK once you have selected it.
  2. Select the Account Field ‘SFDC AccountID’. Click on the button, then search for and select the field in the Search window and click OK once you have selected it.
  3. Select the Perform a case-sensitive match checkbox, as Salesforce uses case-sensitive matches.
  4. You must carry out a verification; you can also view dependencies on the account field selected:
    • Unique Account Verification – Click this button to ensure that all of the values in the linked account field are unique in Eloqua. If the verification fails, you will see a message indicating that there are duplicates. If the verification passes, you’ll see a green indicator next to the Check button.
    • Check Account Dependency – View all of the marketing objects and processes in Eloqua® that have the Account Field you selected as a dependency. This may include update source records, program ownership rules, deduplication or match rules, and any automated marketing programs that use any of these rules. You must resolve all of these dependencies (either edit out the dependency or delete the dependent object or process) before you can proceed with system-level linking.
  5. Once the verification has been carried out successfully, you are ready to set up this linkage.
    Warning! Make sure that you select the correct Contact Field and Account Field, or contacts may end up being mapped to the wrong account, which could affect contact processing. Note that once processing for the mappings has begun, it cannot be undone (rolled back or unmapped).
  6. Click Apply to begin processing the linkage between the Contact and Account fields selected.
Eloqua Salesforce Integration Update
error: Content is protected !!