Send audiences to Oracle Eloqua

Oracle Eloqua is a marketing automation platform that helps your brand design and manage cross-channel marketing campaigns.

Send audiences from Amperity to manage shared lists . Shared lists are static lists of contacts that can be used across Oracle Eloqua. Each shared list should contain a list of contacts with a clearly defined relationship to the campaign or program that is managed from Oracle Eloqua.

Amperity will add and remove audience members from a shared list, and then update any contact attributes that are associated with members of that shared list.


The first audience that is sent from Amperity to Oracle Eloqua should be to a new or empty shared list.


This destination uses the Bulk Loader API to send shared lists to Oracle Eloqua.

Review the Bulk API Best Practices to help ensure that Amperity will be successful when importing your shared lists to Oracle Eloqua.

This topic describes the steps that are required to send audiences to Oracle Eloqua from Amperity:

  1. Get details

  2. Add destination

  3. Add data template

Get details

Oracle Eloqua requires the following configuration details:

Detail one.

Login information for Oracle Eloqua. This includes:

  • Username The username for your Oracle Eloqua account.

  • Password The password associated with your username.

  • Company name The name of your company, as used with your Oracle Eloqua account.

Detail one.

The name of the shared list to be managed by Amperity.

Use filename templates and/or data templates to configure Amperity to support managing more than one shared list. For example:

  • A timestamp at the end of a filename template — Early_Purchasers_{{format:’MM-dd-yyyy’}}.csv — will create a new shared list each time an audience is sent from Amperity. The shared list will always be titled “Early Purchasers”, but will have a unique datestamp.

  • A campaign that is configured only for campaign name and group name — {{ campaign_name }} - {{ group_name }} — will update the same shared list each time the audience is sent from Amperity.


You may add custom attributes to the shared list as long as each custom attribute is mapped to the database name that was assigned to the custom contact field by Oracle Eloqua.

This approach requires adding an empty shared list to Oracle Eloqua, and then adding any custom contact fields to that shared list. This will generate the database name, which is typically (but not always) prefixed with C_.

Use a query to build the results your brand wants to send to Oracle Eloqua. Be sure to map each field in the query results to the database name in Oracle Eloqua.

A campaign must use the Edit Attributes dialog box to configure the attributes to be sent, along with ensuring the correct database type mapping from Oracle Eloqua is applied to each field.

Detail one.

The primary key for the shared list: C_EmailAddress.

An email address (mapped to the database type C_EmailAddress) is the only requirement for sending audiences to Oracle Eloqua for use as a shared list. Additional attributes may be sent. Some must be mapped to the default attributes ; custom attributes may be defined.

Add destination

Configure Amperity to send audiences directly to Oracle Eloqua.

To add a destination

Step 1.

Open the Destinations tab to configure a destination for Oracle Eloqua. Click the Add Destination button to open the Destination dialog box.

Name, description, choose plugin.

Enter a name for the destination and provide a description. For example: “Oracle Eloqua” and “This sends audiences to Oracle Eloqua”.

From the Plugin drop-down, start typing “ora” to filter the list, and then select Oracle Eloqua.

Step 2.

Credentials allow Amperity to connect to Oracle Eloqua.

The credential type is set automatically. You may use an existing credential or you may add a new one.

Choose an existing credential or add credential.

Select an existing credential from the Credential drop-down.

– or –

Select Create a new credential from the Credential drop-down. This opens the Credential dialog box.

Choose an existing credential or add credential.

Enter the name for the credential, and then add a description.

Oracle Eloqua has the following settings:

  • Username The username for your Oracle Eloqua account.

  • Password The password associated with your username.

  • Company name The name of your company, as used with your Oracle Eloqua account.

When finished, click Save.

Step 3.

Each destination has settings that define how Amperity will deliver data to Oracle Eloqua. These settings are listed under the Settings section of the Destination dialog box.

Settings for Dynamics 365 Marketing.

The following settings are specific to Oracle Eloqua:



Shared List Name

The name of the shared list in Oracle Eloqua. If the shared list does not exist, Amperity will create it.


Amperity does not create custom attributes for a shared list. A shared list that contains custom attributes must be created in Oracle Eloqua along with any custom attributes before Amperity can send data.

Audience Primary Key

This value must be set to C_EmailAddress.

Step 4.

Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them.

Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII.

What is restricted access to PII?

Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.

You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options:

Allow business users access to this destination.


To allow business users to use this destination with campaigns, you must enable the Available to campaigns option within the data template. This allows users to send campaign results from Amperity to Oracle Eloqua.

The other two settings may be configured within the data template instead of the destination.

Step 5.

Review all settings, and then click Save.

Save the destination.


You must configure a data template for this destination before you can send data to Oracle Eloqua.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

To add a data template

Step 1.

From the Destinations tab, open the menu for a destination that is configured for Oracle Eloqua, and then select Add data template.

This opens the Add Data Template dialog box.

Step 1

Enter the name of the data template and a description. For example: “Oracle Eloqua” and “Send audiences to Oracle Eloqua.”.

Step 2.

Verify business user access to queries and orchestrations and access to segments and campaigns.

A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data.

Step 2.

If business user access was not configured as part of the destination, you may configure access from the data template.

Step 3.

Verify all configuration settings.

Verify settings for the data template.


When the shared list name and primary key are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns.

Step 4.

Review all settings, and then click Save.

Save the data template.

After you have saved the data template, and depending on how you configured it, business users can send query results and/or send campaigns to Oracle Eloqua.