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.
Featureslink
| Feature Name | Supported | Notes |
|---|---|---|
| Capture Deletes | ||
| Custom Data | check | All tables and fields |
| Data Blocking | check | Column level |
| Column Hashing | check | |
| Re-sync | check | Connector level |
| History | check | VISITOR table only |
| API Configurable | check | |
| Priority-first sync | ||
| dbt Package |
Setup guidelink
Follow our step-by-step Eloqua setup guide to connect Eloqua with your destination using Fivetran connectors.
Schema informationlink
This schema applies to all Eloqua connections.
To zoom, open the ERD in a new window.Sync overviewlink
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.NOTE: The
CONTACT_SEGEMENTandCONTACT_LIST_CONTACTtables are part of our Contact list endpoints and Contact segment endpoints support. If you want to sync these tables, contact our support team.
For more information, see Eloqua’s export data documentation.
Sync notelink
We can’t use the time criteria in our activities requests because the Eloqua Bulk API only allows date values for the createdAt parameter.
Therefore, we sync the CONTACT_ACTIVITY table once a day. For example, we can query the CONTACT_ACTIVITY table using startDate > 30-04-2020 to endDate < 10-05-2020. However, we can’t use time-based queries, such as startDate > 30-04-2020 01:00:00 to endDate < 30-04-2020 23:59:59.