D&B provides a cloud feeder app that you can install in Eloqua. Once installed, users can create multiple campaigns with-in Eloqua with each campaign containing an instance of the cloud feeder.
The cloud feeder app is designed to look for CDP campaign updates and pull them at user defined intervals.
At a high level, here is how data from the CDP synchronizes to Eloqua
- User in the CDP launches a campaign.
- CDP generate accounts and contacts and store this snapshot for Eloqua app.
- User in Eloqua creates and activates an Eloqua campaign with the cloud feeder application.
- Assuming the user in Eloqua has setup the cloud feeder app to sync with CDP daily, the Eloqua app calls an API to get the latest accounts and contacts
- The contacts are then synced with-in Eloqua using the Eloqua's bulk API
Data transfer between CDP & Eloqua
The Eloqua app constantly polls the CDP for launch update. So, if the user has new data in CDP, but does not launch the campaign, the Eloqua app does not receive any updates to its leads.
For new leads to be updated in Eloqua, two things must happen
- The user should launch the campaign. This will make the latest data available to Eloqua
- The Eloqua app schedule needs to kick in for the app to sync this data in Eloqua
Note: The Eloqua app does not store any account or contact data. Data from the CDP is passed directly to Eloqua. Any temporary data created to facilitate transfer is cleared with-in 24 hours.
Data Sync Frequency: When does the Eloqua app sync data from the CDP?
The user has a choice (Daily, Weekly, Monthly) to set the sync frequency. But the clock starts immediately after the user activates the campaign.
As soon as the user activates the campaign, the Eloqua app will immediately sync data from the CDP. As long as the campaign remains active, the Eloqua app will try to sync on the user defined schedule e.g if the schedule is daily, the next sync will occur 24 hrs after the current one.
Hint: If you are looking to test syncing data from the CDP, deactivating and activating the campaign is a good way to reset the clock and initiate Eloqua app syncing from the CDP.
Creating New contacts vs. updating existing contacts
The Eloqua app will create new contacts if they don't already exist in the Eloqua lead database. If the lead does exist, those contacts will be updated.
Note: The CDP support custom fields on a contact object, but does not supports writing to Eloqua's custom object.
Contact counts between the CDP & Eloqua
The number of contacts can be different between what is synced in Eloqua vs. what was launched in Lattice.
Different Contacts in Lattice share the same email
Eloqua does not support create leads with the same email. If the campaign from the CDP contains contacts with the same email id, they will be deduped.
Contact's Email is not a valid Email
Eloqua automatically rejects leads that don't have a valid email. If a contact in the CDP has an invalid email, they will automatically be skipped from syncing to Eloqua. Users can see the number of contacts that has invalid email in the recommendation dashboard with-in the Eloqua App.
API and Conflicts with other integrations
The Eloqua app from the CDP uses the Bulk APIs from Eloqua. These are efficient using 1API call per 100K contacts.
The app uses the same Eloqua Bulk APIs that are shared across the account, so if several parallel large data imports (>500k) are queued, Eloqua will spend additional time processing. This will not "block" other integrations though. The import priority is managed by Eloqua Administrators.