Data imports from Salesforce to Oracle Eloqua
Important: The Salesforce native integration was deprecated February 1, 2021. We recommend using the
Oracle Eloqua imports existing account, contact, and lead data from Salesforce. After the initial import, any changed data is imported using an incremental process.
Oracle Eloqua uses auto synchs and external calls to mange the imports. When to import the data and what data to import depends on how you setup your implementation.
Note: When an account, contact, lead, or opportunity is imported to Oracle Eloqua, the Oracle Eloqua record includes the ID of the original Salesforce record.
The following table provides key details about the synchronization of different data types:
Salesforce entity | Details |
---|---|
Contacts | Salesforce contacts are stored in the Eloqua contact database. CRM records are matched with Eloqua records using the email address.
If a contact exists with the same email address, the contact record is updated with the latest CRM data. If there is no contact record with the same email address, a new contact record is created in Oracle Eloqua. See Duplicate record processing. |
Leads | In Salesforce, a lead is a person identified as a potential customer. Oracle Eloqua stores leads as contacts in the Oracle Eloqua contact database. CRM records are matched with Oracle Eloqua records using the email address. If a lead exists with the same email address, the contact record is updated with the latest CRM data. If there is no contact record with the same email address, a new contact record is created in Oracle Eloqua. |
Accounts | Salesforce accounts are added to the Oracle Eloqua account database. CRM records are matched with the Oracle Eloqua account database using the account ID. If there is an Oracle Eloqua account with the same ID, the account record is updated with the latest CRM data. If there is no account record in Oracle Eloqua with the same ID, a new account is created.
In Oracle Eloqua contacts are linked to accounts using the account ID. If a contact is associated with more than one account in Salesforce, only the primary account is associated with the contact in Oracle Eloqua. Note: It is recommended that you only synch accounts from Salesforce to Oracle Eloqua. |
Opportunities |
|
Duplicate record processing
Note: It is recommended that you remove duplicate sales records before integrating with Oracle Eloqua. Duplicate data history is not maintained.
Oracle Eloqua uniquely identifies records based on email address. When Salesforce contact records with the same email address are imported into Oracle Eloqua at the same time, duplicates are merged into a single record, with the highest ASCII value retained on a field-by-field basis (Z is higher than A; 9 is higher than 1; letters are higher than numbers; lowercase is higher than uppercase).
The following table illustrates the duplicate record processing.
First name | Last Name | Company | Address | Job Title | |
---|---|---|---|---|---|
Salesforce contact records | |||||
bob@example.com | Bob | Smith | Example Inc. | 401 Island Parkway Redwood Shores, CA |
Marketing Director |
bob@example.com | Robert | Smith | Example Ltd. | 104 Island Parkway Redwood Shores, CA |
Director of Marketing |
Oracle Eloqua contact record | |||||
bob@example.com | Robert | Smith | Example Ltd. | 401 Island Parkway Redwood Shores, CA |
Marketing Director |
Data exports from Oracle Eloqua to Salesforce
Data exports from Oracle Eloqua to Salesforce
Configuring data imports from Salesforce