You can write Treasure Data job results directly to your Eloqua contact records and custom object. You use this integration and TD query jobs to add contacts to Eloqua Contact lists or add data to custom data objects (CDO).
This data connector is in Beta. For more information, contact support@treasuredata.com.Learn more about:
| Table of Contents | ||
|---|---|---|
|
Prerequisites
Basic knowledge of Treasure Data, including the TD Toolbelt.
An Eloqua account with API access enabled.
Requirements and Limitations
Your query requires that each type of resource has:
...
If your query contains any field name that does not exist in the custom object fields name, then an error is returned, and the job fails.
Obtain the Custom Data Object Name from Oracle Eloqua Console
| Numbered Headings | ||||
|---|---|---|---|---|
| ||||
Login into Oracle Eloqua Console.https://login.eloqua.com/ |
...
Enter the same company, user name, and password |
...
you entered when specifying the CSF authentication keys in Oracle JDeveloper and Oracle Enterprise Manager Fusion Middleware Control.Navigate to Audience
Select Custom Objects. |
...
Optionally, navigate to Custom Object Record Reporting and select the desired report:
|
...
|
...
|
...
|
...
Make note of the custom object name and the field names.
|
Use the TD Console to Create Your Connection
Create a New Connection
In Treasure Data, you must create must create and configure the data connection prior to before running your query. As part of the data connection, you you provide authentication to access the integration.
Open TD Console.
Navigate to Integrations Hub > Catalog.
Search for and select Eloqua.
Type the credentials to authenticate.
Type a name for your connection.
Select Done.
Define your Query
Your query requires that each type of resource has specific resource type to have specific columns and exact column names (case sensitive) and data types.
...
If your query contains any field name that does not exist in the custom object fields name, then an error is returned, and the job fails.
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
Integration Parameters for Eloqua
Contact and Custom Object Data Parameters | Value | Description | ||
|---|---|---|---|---|
| Destination | Contact | The Eloqua object to export data (contact list or custom object) | ||
| Custom Object Data | The Eloqua object to export data (contact list or custom object) | |||
| Identifier Field Name | - Contact's email address [c_emailaddress] | The field name is used to identify the contact entity. If you chose a Contact's email address, you must have the c_emailaddress field in your query with the Contact's external ID as c_externalid field, and the Contact's ID is a c_id field. | ||
One of the field names from your custom object data query. For example, if your query is:
then the value should be one col_a, col_b, or col_b. | The field name is used to identify the custom object row. | |||
| Add prefix to the identifier | Check if you want to modify the identifier value by adding a prefix value to the identifier column. This option is supported for an identifier column that has a data type of string type. | |||
| Prefix | string value | prefix value will be added to identify column value | ||
| List/Object name to import | Custom object names can be case insensitive. | The contact list name or object name for the exported data. The custom object name that we need to export data into. | ||
| Update Rule | - Always update - Update if the new value is not blank - Update if the existing value is blank - Use the rule defined at the field level | The rule is used when doing updates on existing data. For more information about this parameter, see the Oracle Eloqua. | ||
| Skip invalid records | If you checked when Eloqua synced data and you receive a data rows error, the export job is still a success. Otherwise, the job failed. | |||
| Map custom object to contact | If you checked, the job tries to map a custom object to a contact. | |||
| Perform case sensitive search when mapping custom object to contact | Perform a case-sensitive search when mapping a custom object to a contact. | |||
| CDO source field | Column name of the field | Input the column name of the field to be mapped, as used in the export schema. Required when Map custom object to contact is enabled. | ||
| Contact map field | Column name of the field | Input the contact field for mapping. Required when Map custom object to contact is enabled. |
Example Query
Your query requires that each type of resource has specific resource type to have specific columns and exact column names (case sensitive) and data types.
...
If your query contains any field name that does not exist in the custom object fields name, then an error is returned, and the job fails.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
SELECT col_a, col_b, col_b FROM your_table; |
For For example, the following query to export contact data does not match any real users and is for demonstration purposes only.
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
SELECT c_emailaddress, c_firstname, c_lastname FROM contact; |
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
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.
| Numbered Headings | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
Optionally Configure Export Results in Workflow
Within Treasure Workflow, you can use this data connector to export data.
Learn more at Using Workflows to Export Data with the TD Toolbelt.
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
Example Workflow for Exporting Contacts
The identifier_field_name accepts the following values:
...
| Code Block |
|---|
_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
skipInvalidRecords: true
|
Example Workflow for Exporting Custom Object
The custom_object_identifier_field is one of the fields named in the export_contact.sql query.
...
| Code Block |
|---|
_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: custom_object
custom_object_identifier_field: {xxxxx}
list_name: {custom_object_name}
update_rule: always
skip_invalid_records: true
skipInvalidRecordsmap_custom_object_to_contact: true,
perform_case_sensitive_search: false,
cdo_source_field: Email_Address,
contact_map_field: C_EmailAddress |