What to Expect

Engagio will pull in the following types of engagement from Eloqua:
- Page Views
- Form Submits
- Email Opens
- Email Clicks

Don't forget to assign engagement to these actions once you've set up your integration. 

Engagio will also pull in all contacts from Eloqua, regardless of whether they exist in Salesforce or not.

How does Engagio import Eloqua Activities

Engagio uses the asynchronous Bulk API, which is specifically designed for high volume data transfers. The Oracle Eloqua documentation for the Bulk API begins by stating: "The Bulk API is a RESTful API designed to support high volume data transfers. It can be used for CRM and data warehousing integrations." (Link is here: https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAB/Developers/BulkAPI/bulk-API.htm)

Unlike the Application API (which Engagio does not use), the Bulk API is set up to operate in an asynchronous fashion. First, an integration such as Engagio's issues an export request describing the data to be transferred. Then, the Eloqua system prepares the data to be exported in a staging area. This occurs asynchronously. Later, after the export file has been prepared, the Engagio integration retrieves the exported records in chunks of 50,000 rows.

The Engagio integration only makes use of a small number of export requests per day (typically 7). This is well below the soft limit of 2,000 syncs per day, as documented here: https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAB/Developers/BulkAPI/Reference/bulk-limits.htm

Our integration is written following the Eloqua recommended best practices for retrieving large volumes of data, as documented here: https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAB/Developers/BulkAPI/Tutorials/Retrieving_Large_Volumes.htm

Adding Eloqua as an Integration

Step 1: Administrators head over to the Integrations page

Step 2: Click Create Data Source at the bottom of the screen

Step 3: Click the Eloqua Icon

Step 4: Enter your Company Name, Username, and Password

Step 5: Click Save