Connect Oracle Eloqua (V2) to Experience Platform in the UI

The Oracle Eloqua (V2) source connector empowers you to connect your Oracle Eloqua account with Adobe Experience Platform, enabling automated and scalable ingestion of key B2B marketing data, including contacts, accounts, campaigns, and engagement activities.

Use this source connector to configure secure authentication, select the exact Eloqua data entities you need, and map them to standardized Experience Data Model (XDM) schemas. Flexible scheduling options allow you to set up both initial data loads and recurring, incremental syncs, ensuring your marketing data remains current and actionable.

Built on Adobe’s enterprise ingestion framework, the Oracle Eloqua (V2) source connector provides a reliable, extensible foundation for campaign optimization, performance measurement, and cross-channel personalization.

Read this guide to learn how to connect your Oracle Eloqua account to Adobe Experience Platform using the sources workspace in the Experience Platform user interface.

Get started

This tutorial requires a working understanding of the following components of Experience Platform:

Gather required credentials credentials

Read the Eloqua overview for information on authentication.

In the Experience Platform UI, select Sources from the left navigation to access the Sources workspace. Choose a category or use the search bar to find your source.

To connect to Eloqua, go to the Marketing Automation category, select the (V2) Oracle Eloqua source card, and then select Set up.

TIP
Sources in the sources catalog display the Set up option when a given source does not yet have an authenticated account. Once an authenticated account is created, this option changes to Add data.

The Eloqua source card in the sources catalog with the Set up button highlighted.

Use an existing account existing

To use an existing account, select Existing account and then select the Eloqua account that you want to use.

The Existing account option selected in the account creation interface.

Create a new account new

To create a new account, select New account and provide a name and description under your Source connection details. Next, under Account authentication, provide values for your Client ID, Client secret, Username, Password, and Base endpoint. You can read the authentication guide for more information on these credentials. When finished, select Connect to source and allow for a few seconds for your connection to establish.

The New account interface with fields for source connection details and authentication credentials.

Select data

Use the select data interface to select the Eloqua entity that you want to ingest to Experience Platform.

TIP
When selecting data, you will notice that, except for campaigns, the other entities display representative sample data. This approach ensures you can preview available fields and structure, as Eloqua public APIs currently retrieve real data for campaigns only. For the remaining entities, sample data is provided to support your configuration workflow.

The data selection interface showing available Eloqua data entities.

Dataset and dataflow details details

Next, you must provide information on your dataset and dataflow. During this step, you can either use an existing dataset or create a new dataset. Additionally, you can optionally enable your dataset for ingestion to Real-Time Customer Profile during this step.

The dataset and dataflow details interface with options to configure dataset properties.

Mapping mapping

Mappings for Eloqua are organized into four main entity types:

  • Accounts - Company/organization records from Eloqua.
  • Activities - Marketing activity and engagement events from Eloqua.
  • Campaigns - Marketing campaign records from Eloqua.
  • Contacts - Individual person records from Eloqua.

If you require access to extra fields beyond those provided by default, you can add these fields using Data Prep mapping process in Experience Platform. If the default (standard) schema does not support some of your required fields, you have the option to define a custom schema in Experience Platform. Use this feature to create and map the necessary fields so you can seamlessly ingest all relevant data from Eloqua into Experience Platform.

Summary of next steps:

  • Review the default mapped fields available with the integration.
  • During the mapping step, include any additional fields needed from Eloqua.
  • If new fields are not present in the standard schema, extend or create a custom schema in Experience Platform that includes these fields.
  • Complete the mapping to ensure all desired data is ingested.

To ensure your external CRM information is accurately reflected, simply use the calculated field function in Data Prep to update the {CRM_INSTANCE_ID} placeholder with your specific CRM instance ID in the source data field. This gives you the flexibility to tailor the integration to your organization’s unique setup.

To use the calculated field editor, select the source field that you want to update.

The Eloqua source field with calculated fields.

Salesforce

For Salesforce users, use the calculated field editor and update the {CRM_INSTANCE_ID} with the appropriate instance ID.

The calculated field for Salesforce.

Microsoft Dynamics

For Microsoft users, use the calculated field editor and update the {CRM_INSTANCE_ID} with the appropriate instance ID.

The calculated field for Dynamics.

Once you finish updating your calculated fields, select Next to continue.

The mapping interface showing field mappings for Eloqua data entities.

Scheduling

NOTE
The following are the delta fields used internally for incremental data loading:
  • Contacts: C_DateModified
  • Accounts: M_DateModified
  • Activity: CreatedAt
  • Custom Objects: UpdatedAt
  • Campaign: updatedAt

With your mapping complete, you can now configure an ingestion schedule for your dataflow. Set your Frequency to Once to configure a one-time ingestion run. For incremental ingestion, you can set your Frequency to Hour, Day, or Week. When using incremental ingestion, you must also configure the Interval to define the amount of time that occurs between ingestion runs. For example, an ingestion frequency set to Day and an interval set to 15 means that your dataflow is scheduled to ingest data every 15 days.

Per-minute ingestion frequency is not available for the Eloqua source. The most frequent schedule you can choose is hourly. Select a schedule that matches your data freshness needs. Keep in mind that selecting a more frequent schedule will increase compute costs.

The scheduling interface with options to configure ingestion frequency and interval.

Review

With the ingestion schedule configured, use the Review interface to confirm the details of your dataflow. Select Finish to complete the setup and allow for a few moments for your dataflow to initiate.

The review interface displaying a summary of the dataflow configuration before completion.

Monitor

Once the dataflow is selected it will do a one-time backfill of data and subsequent incremental sync on the schedule specified. The status of sync can be monitored by navigating to the dataflow. For more information, read the guide on monitoring sources dataflows in the UI.

Next steps

You’ve now completed the setup and configuration of your Eloqua source in Experience Platform. With your dataflow established, your Eloqua data will be ingested according to your chosen schedule and mapped to standard Experience Data Model (XDM) schemas. Continue monitoring your dataflows and explore your ingested data within Platform to drive insights and activate your marketing use cases. For more advanced configurations and troubleshooting, consult the related documentation or reach out to Adobe support resources.

For additional information, read the following documentation:

recommendation-more-help
337b99bb-92fb-42ae-b6b7-c7042161d089