(API) Oracle Eloqua connection

Oracle Eloqua enables marketers to plan and execute campaigns while delivering a personalized customer experience for their prospects. With integrated lead management and easy campaign creation, it helps marketers engage the right audience at the right time in their buyer’s journey and elegantly scales to reach audiences across channels including email, display search, video, and mobile. Sales teams can close more deals at a faster rate, increasing marketing ROI through real-time insight.

This Adobe Experience Platform destination leverages the Update a contact operation from the Oracle Eloqua REST API, which allows you to update identities within an audience into Oracle Eloqua.

Oracle Eloqua uses Basic Authentication to communicate with the Oracle Eloqua REST API. Instructions to authenticate to your Oracle Eloqua instance are further below, in the Authenticate to destination section.

Use cases use-cases

The marketing department of an online platform wants to broadcast an email based marketing campaign to a curated audience of leads. The platform’s marketing team can update existing lead information through Adobe Experience Platform, build audiences from their own offline data, and send these audiences to Oracle Eloqua, which can then be used to send the marketing campaign email.

Prerequisites prerequisites

Experience Platform prerequisites prerequisites-in-experience-platform

Before activating data to the Oracle Eloqua destination, you must have a schema, a dataset, and segments created in Experience Platform.

Refer to the Experience Platform documentation for Audience Membership Details schema field group if you need guidance on audience statuses.

Oracle Eloqua prerequisites prerequisites-destination

In order to export data from Platform to your Oracle Eloqua account you need to have an Oracle Eloqua account.

Additionally, you need, at a minimum, the “Advanced Users - Marketing permissions” for your Oracle Eloqua instance. Refer to the “Security Groups” section on the Secured user access page for guidance. The access is required by the destination to programmatically determine your base URL when invoking the Oracle Eloqua API.

Gather Oracle Eloqua credentials gather-credentials

Note down the items below before you authenticate to the Oracle Eloqua destination:

Refer to the Signing in to Oracle Eloqua for guidance.

Guardrails guardrails

Supported identities supported-identities

Oracle Eloqua supports update of identities described in the table below. Learn more about identities.

Export type and frequency export-type-frequency

Refer to the table below for information about the destination export type and frequency.

Connect to the destination connect

To connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.

Within Destinations > Catalog search for (API) Oracle Eloqua. Alternatively you can locate it under the Email Marketing category.

Authenticate to destination authenticate

Fill in the required fields below. Refer to the Gather Oracle Eloqua credentials section for any guidance.

To authenticate to the destination, select Connect to destination.

If the details provided are valid, the UI displays a Connected status with a green check mark. You can then proceed to the next step.

Fill in destination details destination-details

To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.

Enable alerts enable-alerts

You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.

When you are finished providing details for your destination connection, select Next.

Activate audiences to this destination activate

Read Activate profiles and audiences to streaming audience export destinations for instructions on activating audiences to this destination.

Mapping considerations and example mapping-considerations-example

To correctly send your audience data from Adobe Experience Platform to the Oracle Eloqua destination, you need to go through the field mapping step. Mapping consists of creating a link between your Experience Data Model (XDM) schema fields in your Platform account and their corresponding equivalents from the target destination.

To map your XDM fields to the Oracle Eloqua destination fields, follow these steps:

{
   "type":"ObjectValidationError",
   "container":{
      "type":"ObjectKey",
      "objectType":"Contact"
   },
   "property":"emailAddress",
   "requirement":{
      "type":"EmailAddressRequirement"
   },
   "value":"<null>"
}

When you are finished providing the mappings for your destination connection, select Next.

Validate data export exported-data

To validate that you have correctly set up the destination, follow the steps below:

Data usage and governance data-usage-governance

All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, see the Data Governance overview.

Errors and troubleshooting errors-and-troubleshooting

When creating the destination, you might receive one of the following error messages: 400: There was a validation error or 400 BAD_REQUEST. This happens when you exceed the 250 custom contact fields limit, as described in the guardrails section. To fix this error, make sure you are not exceeding the custom contact field limit in Oracle Eloqua.

Refer to the Oracle Eloqua HTTP status codes and Oracle Eloqua Validation errors pages for a comprehensive list of status and error codes with explanations.

Additional resources additional-resources

For additional details, see the Oracle Eloqua documentation:

Changelog

This section captures the functionality and significant documentation updates made to this destination connector.