Send audiences to Oracle Eloqua

You can use segments and campaigns to manage shared lists in Oracle Eloqua.

Note

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

Note

Ask your DataGrid Operator or your Amperity representative for help configuring Oracle Eloqua as a destination to which you can send campaigns for customer activation.

Build a segment

Use the Segment Editor to build any audience using a series of dropdowns and picklists.

As you define the attribute profile for an audience be sure to refresh segment insights to see how many customers match your audience and to see how much value they bring to your business.

When the segment is ready, activate it, and then use it use it in a campaign to send to your preferred destinations for customer activation.

Which attributes should you use?

You can use any attribute that is in your customer 360 database to define your audience.

When the list of customers who belong to this audience is sent to Oracle Eloqua as part of a campaign you will be required to choose specific attributes to send.

Oracle Eloqua supports the following attributes: audiences.

Add to a campaign

Use the campaign editor to configure Amperity to send data to Oracle Eloqua. Add a segment, define exclusions and sub-audiences, and then define the audiences that will be sent to Oracle Eloqua.

To add Oracle Eloqua to a campaign

	Open the Campaign Editor. This is available from the Campaigns page. Click the Create campaign button in the top right corner of the page.
	Assign Oracle Eloqua as a destination for at least one treatment group. Note You may need to edit the attributes for the sub-audience to ensure Amperity is sending the right data to Oracle Eloqua.
	Click Edit attributes to review the attributes that Amperity will send to Oracle Eloqua. Oracle Eloqua requires an email address. You may configure Amperity to send additional fields. Amperity pre-selects the list of attributes that may be sent to Oracle Eloqua. The Edit attributes page for Oracle Eloqua is similar to: Note The Merged Customers table is the default table from which data is sent to Oracle Eloqua, even though segments are often built from the Customer 360 table. This is by design. The Merged Customers table is the underlying table for customer profile data and is the source for all customer profile data that exists within the Customer 360 table.

Configure default attributes

Each unique destination that is configured to send data to Oracle Eloqua may be configured to have a set of default attributes that will sent to Oracle Eloqua every time this destination is associated with a treatment group in an active campaign.

Default attributes may be configured for a destination by clicking the Default attributes link next to the Create campaign button on the Campaigns page.

The source table is set to Merged Customers for most attributes. Your brand may configure each attribute to be pulled from the source table that best represents how your brand wants to use the attribute in Oracle Eloqua.

Oracle Eloqua has the following requirements for attributes.

Source attribute	Destination attribute
email	C_EmailAddress