Eloqua Integration for Data Studio

Prerequisites 

The information in this article pertains to Terminus Data Studio customers that also have a registered instance of Eloqua.

Integration Overview 

Most information in Terminus Data Studio will be pulled from your connected CRM. However, there may be some pertinent marketing data that is not pushed from Eloqua to your CRM today. In order to capture the full picture of your Marketing team’s efforts, Terminus’s Eloqua integration was created to make sure all relevant data is accounted for in your Terminus reporting.

While your CRM will be the primary data source for Data Studio, the Eloqua integration was built to supplement your Terminus instance with additional Marketing Activity data.

What is Terminus Data Studio?

The Terminus Engagement Hub is designed to enable everyone in marketing, sales, and leadership to address the challenges facing ABM teams today. Within the platform, users can identify and prioritize target accounts, engage the buying committee with multichannel programs, send actionable insights to sales, measure results, and report on success to their entire organization.

The Engagement Hub includes Data Studio, which is your central account intelligence data platform. It automatically ingests account-level firmographic and behavioral intelligence to give you a 360-degree view of all of your accounts. From there, you can easily build actionable target account lists, identify gaps in marketing or sales coverage, and prioritize your ABM efforts across marketing and sales. The Engagement Hub also offers a robust account-based analytics suite, called Measurement Studio, which includes the Campaign Analytics, Opportunity Insights, and Account Scorecard views, so it’s easy to assess and optimize individual campaigns, and report on holistic program success to your leadership team.

Integration Details

Terminus’s MAS integrations are designed to supplement data gaps in your CRM with Campaign, Campaign Response, and Lead/Contact Data. The Eloqua integration can also be configured to pull in Custom Data Objects. These integrations are not designed to ingest Account, Opportunity, or Sales Activity Data. 

Eloqua-integrated customers are not able to leverage the following configuration options in Data Studio: 

• Self-serve Validity Rules and Global Filters on Eloqua Data
• Self-serve / Custom Fields on Standard Eloqua objects (configured by the Terminus Professional Services team)
• Self-serve Campaign Type mapping on Eloqua Data
• Sandbox Testing

Connection Method

Terminus links to your Eloqua instance via OAuth protocol (OAuth 2.0 information). Any time that you may need to connect Data Studio with Eloqua, follow the below steps.

1. Either clear browser's cache/cookies or open an incognito browser window. This ensures all users are logged out of Data Studio and Eloqua.

2. Log into https://home.terminusplatform.com/ with your email/username and password.

3. Drill into Data Studio.

4. Copy/Paste the following link into the address bar: https://studio.terminusplatform.com/eloqua 

5. Follow the integration instructions on screen to connect Data Studio with your organization's Eloqua instance. When the login page appears, make sure to use the API Integration User's credentials, instead of your own.

APIs Leveraged 

Terminus will connect to the client’s Eloqua instance via Oauth to create a read-only API connection (via REST API).

Data Accessed

Terminus will pull the following data from Eloqua and merge it with the customer’s CRM data to drive reports in Measurement Studio:

• Campaign Data
• Activity Data
• Contact Data
• Custom Data Object Data

The following information is not accessed/applicable for this integration:

• Account Data
• Opportunity Data
• Sales Activity Data
• Product Line Data
• Custom Field Data

FAQs

How frequently does Terminus pull data from Eloqua?

• All of the data objects/entities are pulled once per 24 hours. 
  
  

How many API calls should Eloqua-integrated customers expect per day?

• Our daily maximum should not exceed 100 API calls per day.