Using this integration, you can use TD query jobs to

• Add contacts to your Eloqua contacts lists
• Add accounts to Eloqua account groups
• Add data to Eloqua custom data objects (CDO)

Learn more about:

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

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

In Treasure Data, you must create and configure the data connection 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 to Integrations Hub > Catalog.

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

4. Type the credentials to authenticate:

Parameter	Description
Authentication Method	Basic (Default)
Site Name	URL for the Oracle Eloqua site
Username	The username of your Oracle Eloqua account
Password	The password for your account

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 that each type of resource has 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 column names (case sensitive) and data types. 

• Custom object or account fields, such as col_a, col_b, and col_c, can be case insensitive.
• If the custom object or account field name on the Eloqua server 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 fields name, an error is returned, and the job fails. 

SELECT col_a, col_b, col_b 
FROM your_table;

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

SELECT c_emailaddress, c_firstname, c_lastname 
FROM contact;

SELECT identifier_type, identifier
FROM table my_table

Optionally Schedule the Query Export Jobs

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

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

Optionally Configure Export Results in Workflow

Within Treasure Workflow, you can specify the use of a data connector to export data.

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
    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
    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