Oracle Eloqua Export Integration

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

Using this integration, you can use TD query jobs to

• Add contacts to your Eloqua contact lists
• Add accounts to the Eloqua account groups
• Add data to Eloqua custom data objects (CDO)
• Add contacts to the shared list on Eloqua and add the shared list to the segment.

Prerequisites

• Basic knowledge of Treasure Data, including the TD Toolbelt
• An Eloqua account with API access enabled

Obtaining the Custom Data Object Name from Oracle Eloqua Console

1. Go to https://login.eloqua.com.

2. Log in to the Oracle Eloqua Console using the same Company Name, Username, and Password you used when specifying the CSF authentication keys in Oracle JDeveloper and Oracle Enterprise Manager Fusion Middleware Control.

3. After logging in, select **Audience >**Custom Objects.

4. Make note of the custom object name and the field names.

Optionally, you can navigate to Custom Object Record Reporting and select the desired report:

• Custom Object Data —Use this report to view all the custom object records within the individual custom object. You can print and export the report to Excel and copy, delete, or move the custom object records.
• Custom Object and Contact Data — Use this report to view all the custom object records within the individual custom object with the contact information they are mapped to. The report can be viewed in a specified time frame. The default is the past month, but you can change the time range (e.g., Start Date or End Date) or time span (e.g., Last week or Last month). You can print and export the report to Excel.

Use the TD Console to Create a Connection

You must create and configure the data connection in Treasure Data before running your query. As part of the data connection, you provide authentication to access the integration.

Create a New Authentication

1. Open TD Console.

2. Navigate toIntegrations Hub > Catalog.

3. Search for Eloqua in the Catalog; hover over the icon and select Create Authentication.

4. Type the credentials to authenticate:

5. Select Continue.

6. Enter a name for your authentication, and select Done.

About Eloqua Query Constraints

The following constraints apply to your queries:

• Your query requires each resource type to have specific columns with exact column names (case sensitive) and data types.
• Your query must define the column mapping.
• Custom object or account fields are case-insensitive.
• If the custom object or account field contains a space, you must replace it with an underscore.
• If your query contains any field name that does not exist in the custom object or account field name, an error is returned, and the job fails.

Define your Query

1. Complete the instructions in Creating a Destination Integration.
2. Navigate to Data Workbench > Queries.
3. Select a query for which you would like to export data.
4. Run the query to validate the result set.
5. Select Export Results.
6. Select an existing integration authentication.

7. Define any additional Export Results details. In your export integration content, review the integration parameters. For example, your Export Results screen might be different, or you might not have additional details to fill out:

8. Select Done.
9. Run your query.
10. Validate that your data moved to the destination you specified.

Integration Parameters for Eloqua

SELECT col_a, col_b, col_c FROM your_table;

Example Query

Your query requires each resource type to have specific columns and exact names (case sensitive) and data types.

• Custom objects or account fields, such as col_a, col_b, and col_c, can be case-insensitive.
• If the Eloqua server's custom object or account field name contains a space, replace it with an underscore in your query.
• If your query contains any field name that does not exist in the custom object or account field name, an error is returned, and the job fails.

custom object query

SELECT col_a, col_b, col_bFROM your_table;

For example, to export a contact, you could use queries similar to these:

SELECT c_emailaddress, c_firstname, c_lastnameFROM contact;
SELECT identifier_type, identifierFROM table my_table

(Optional) Schedule Query Export Jobs

You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.

Treasure Data's scheduler feature supports periodic query execution to achieve high availability.

When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.

For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.

Scheduling your Job Using TD Console

1. Navigate to Data Workbench > Queries

2. Create a new query or select an existing query.

3. Next to Schedule, select None.

4. In the drop-down, select one of the following schedule options:

   Drop-down Value	Description
   Custom cron...	Review Custom cron... details.
   @daily (midnight)	Run once a day at midnight (00:00 am) in the specified time zone.
   @hourly (:00)	Run every hour at 00 minutes.
   None	No schedule.

Custom cron... Details

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- day of week (0 - 6) (Sunday=0)
 |    |    |    +---------- month (1 - 12)
 |    |    +--------------- day of month (1 - 31)
 |    +-------------------- hour (0 - 23)
 +------------------------- min (0 - 59)

The following named entries can be used:

• Day of Week: sun, mon, tue, wed, thu, fri, sat.
• Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.

A single space is required between each field. The values for each field can be composed of:

1. (Optional) You can delay the start time of a query by enabling the Delay execution.

Execute the Query

Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.

(Optional) You can delay the start time of a query by enabling the Delay execution.

Activate a Segment in Audience Studio

You can also send segment data to the target platform by creating an activation in the Audience Studio.

1. Navigate to Audience Studio.
2. Select a parent segment.
3. Open the target segment, right-mouse click, and then select Create Activation.
4. In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
5. Customize the activation output in the Output Mapping panel.

• Attribute Columns
  • Select Export All Columns to export all columns without making any changes.
  • Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
• String Builder
  • + Add string to create strings for export. Select from the following values:
    • String: Choose any value; use text to create a custom value.
    • Timestamp: The date and time of the export.
    • Segment Id: The segment ID number.
    • Segment Name: The segment name.
    • Audience Id: The parent segment number.

6. Set a Schedule.

• Select the values to define your schedule and optionally include email notifications.

7. Select Create.

Optionally Configure Export Results in Workflow

You can specify using this data connector to export data within Treasure Workflow.

Learn more at Using Workflows to Export Data with the TD Toolbelt.

Example Workflow for Exporting Contacts

The identifier_field_name accepts the following values:

• C_EmailAddress
• C_ExternalID
• C_ID

The update_rule accepts the following values:

• always
• ifNewIsNotNull
• ifExistingIsNull
• useFieldRule

_export:
  td:
    database: eloqua_db

+eloqua_custom_object_export_task:
  td>: export_contact.sql
  database: ${td.database}
  result_connection: new_created_eloqua_auth
  result_settings:
    type: eloqua
    data_sync_mode: append # replace mode is only support account or contact list
    target: contact
    identifier_field_name: C_EmailAddress
    list_name: td_shared_list2
    update_rule: always
    skip_invalid_records: true
    auto_delete_duration: 3600

Example Workflow for Exporting Custom Object

The custom_object_identifier_field is one of the fields named in the export_custom_object.sql query.

The update_rule accepts the following values:

• always
• ifNewIsNotNull
• ifExistingIsNull
• useFieldRule

You can get custom_object_name from the Oracle Eloqua Console.

_export:
  td:
    database: eloqua_db

+eloqua_custom_object_export_task:
  td>: export_custom_object.sql
  database: ${td.database}
  result_connection: new_created_eloqua_auth
  result_settings:
    type: eloqua
    target: custom_object
    custom_object_identifier_field: {xxxxx}
    list_name: {custom_object_name}
    update_rule: always
    skip_invalid_records: true
    map_custom_object_to_contact: true,
    perform_case_sensitive_search: false,
    cdo_source_field: Email_Address,
    contact_map_field: C_EmailAddress
    auto_delete_duration: 0

Example Workflow for Exporting Account

The account_identifier_field is one of the fields named in the export_account.sql query.

The update_rule accepts the following values:

• always
• ifNewIsNotNull
• ifExistingIsNull
• useFieldRule

You can get the group_account_name from the Oracle Eloqua Console.

_export:
  td:
    database: eloqua_db

+eloqua_account_export_task:
  td>: export_account.sql
  database: ${td.database}
  result_connection: new_created_eloqua_auth
  result_settings:
    type: eloqua
    data_sync_mode: append/replace
    target: account
    account_identifier_field: {xxxxx}
    list_name: {group_account_name}
    custom_identifier: true
    prefix_identifier: prefix_value
    update_rule: always
    skip_invalid_records: true
    auto_delete_duration: 0

Example Workflow for Exporting Contacts Shared List

The identifier_field_name accepts the following values:

• C_EmailAddress
• C_ExternalID
• C_ID

The update_rule accepts the following values:

• always
• ifNewIsNotNull
• ifExistingIsNull
• useFieldRule

_export:
  td:
    database: eloqua_db

+eloqua_custom_object_export_task:
  td>: export_contact.sql
  database: ${td.database}
  result_connection: new_created_eloqua_auth
  result_settings:
    type: eloqua
    data_sync_mode: append
    target: contact_shared_list
    identifier_field_name: C_EmailAddress
    list_name: td_shared_list2 # Required
    segment_name: td_segment_name #Required
    update_rule: always
    skip_invalid_records: true
    auto_delete_duration: 3600

(Optional) Export Integration Using the CLI

You can also use CLI(Toolbelt) to export results to Eloqua

You need to specify the information for export to your server as --result option of td query command. About td query command, you can see this article.

Example for Usage

td query -d your_data_base_here \
-w "SELECT c_emailaddress AS C_EmailAddress, c_firstname AS C_First_Name, c_lastname AS C_Last_Name, c_company  AS Company from eloqua_contact_output" \
-T presto \
--result '{ "type": "eloqua","auth_method": "basic", "site_name": "your site name", "username": "username","password": "password","data_sync_mode": "replace","target": "contact", "list_name": "your list name","identifier_field_name": "C_EmailAddress"}'

References

• API Overview:  https://docs.oracle.com/en/cloud/saas/marketing/eloqua-rest-api/APIRequests.html
• Bulk 2.0: https://docs.oracle.com/en/cloud/saas/marketing/eloqua-rest-api/Getting_Started_Bulk.html