Eloqua
Oracle Eloqua equips marketers with best-in-class lead and campaign management tools that help marketers engage the right audience at the right time in the buyer's journey while providing real-time reporting and insights.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | CAMPAIGN, EMAIL, and FORM tables.* |
| History mode | check | VISITOR table only |
| Custom data | check | |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | check | CONTACT_ACTIVITY and custom object tables |
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
*NOTE: For the
CAMPAIGN,FORMtables, we do not sync records that were created and deleted in between two consecutive syncs.
Setup guide
Follow our step-by-step Eloqua setup guide to connect Eloqua with your destination using Fivetran connectors.
Schema information
This schema applies to all Eloqua connections.
To zoom, open the ERD in a new window.Sync overview
Fivetran uses both the REST API and Bulk API to sync your data from Eloqua.
We use the REST API to sync the following tables:
ACCOUNTCAMPAIGNCONTACTCONTACT_FILTERCONTACT_FILTER_SEGMENT_ELEMENTCONTACT_LISTCONTACT_LIST_SEGMENT_ELEMENTEMAILEMAIL_FORMEMAIL_HYPERLINKFORMFORM_SUBMISSIONSEGMENTUSER_INFOVISITOR
We use the Bulk API to sync the following:
- Custom objects.
CONTACT_ACTIVITYtable. For more information, see Eloqua's exporting activities documentation.CONTACT_SEGEMENTtable.CONTACT_LIST_CONTACTtable.
For more information, see Eloqua's export data documentation.
Sync strategy for CONTACT_SEGMENT and CONTACT_LIST_CONTACT tables
During historical syncs, we retrieve the entire data for all segments and contact lists.
During incremental syncs, we retrieve all the contacts only for the segments and lists for which the updatedAt parameter value has changed. However, the value of the updatedAt parameter does not change when a contact is added to or removed from a segment or list, unless there is a change in the filter criteria. In such cases, Eloqua may not allow us to sync the latest data. To resolve the data discrepancies in such a scenario, perform a full re-sync.
We maintain the live contacts associated with a contact segment or list. We delete all the records that are no longer part of the segment or list from your destination.
We also delete the contact export definitions for the CONTACT_SEGMENT and CONTACT_LIST_CONTACT tables at the end of each sync. We do this because the export definitions for these tables are linked to the contacts in your Eloqua account and this linkage prevents you from deleting the contacts from your account.
We may skip some records in the CONTACT_SEGMENT and CONTACT_LIST_CONTACT tables if any export error occurs while syncing these tables. Incorrect configurations in your Eloqua account, such as using invalid parameter values in the filter criteria of a segment, may result in such export errors. Contact Eloqua's support team to resolve the export errors. We will sync the skipped records and tables once you resolve the errors.
UTC conversion
We don't convert source timestamps to Universal Time Coordinated (UTC) in your destination.
Limit historical data sync
You can opt to limit the amount of historical data you want to sync for the CONTACT_ACTIVITY and custom object tables. You can:
- Use the Historical Sync Limit drop-down menu in the connector setup form
- Specify the value for the
historical_sync_limitparameter in the REST API config
You can select or specify one of the following time ranges:
- Three months
- Six months
- One year
- Two years
- Five years
- All Time (Default)