You can write Treasure Data job results directly to your Eloqua contact records and custom object. You use this integration and Using this integration, you can use TD query jobs to add
- Add contacts to your Eloqua
...
- contacts lists
- Add accounts to Eloqua account groups
- Add data to Eloqua custom data objects (CDO)
...
Learn more about:
Table of Contents | ||
---|---|---|
|
...
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:
...
Obtaining the Custom
...
You must define the column mapping in the query.
Custom object fields, such as col_a, col_b, col_c, can be case insensitive.
If the custom object field contains a space, replace it with an underscore.
If your query contains any field name that does not exist in the custom object fields name, an error is returned, and the job fails.
...
Data Object Name from Oracle Eloqua Console
Numbered Headings | ||||
---|---|---|---|---|
| ||||
Login into Oracle Eloqua Console.In your web browser, go to https://login.eloqua.com/com.Log in to the Oracle Eloqua Console using the same Company Name, Username, and Password you usedEnter the same company, user name, and password you enteredwhen specifying the CSF authentication keys in Oracle JDeveloper and Oracle Enterprise Manager Fusion Middleware Control.Navigate to AudienceSelect After logging in, select Audience >Custom Objects.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
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.
Numbered Headings | ||||
---|---|---|---|---|
| ||||
Create a New AuthenticationOpen TD Console.Navigate to Integrations Hub > Catalog.Search forEloqua in the Catalog; hover your mouse over the icon and select |
...
Create Authentication.Type the credentials to authenticate |
...
:
Select Continue.Enter |
...
a name for your |
...
authentication, and select Done. |
...
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
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Integration Parameters for Eloqua
Contact and
...
Parameters | Value | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Destination | Contact | The Eloqua object to export data (contact list or custom object or account) | ||||||||||
Custom Object Data | The Eloqua object to export data (contact list or custom object or account) | |||||||||||
Account | The Eloqua object to export data (contact list or custom object or account) | |||||||||||
Add a 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 with a data type of string type | |||||||||||
Prefix | string value | This option is supported for an identifier column with a data type of string. The prefix value will be added to identify the column value. | ||||||||||
List/Object name to import | Custom object names can be case-insensitive. Group account name that can be case insensitive (optional) | The contact list name or object name for the exported data. The custom object name that you want to export data into. Group account name for the exported data | ||||||||||
Identifier Field Name | For destination Contact - Contact's email | address [address ( | ]) | ID [ID ( | ]) | ID [ID ( | ]) | The field name is used to identify the contact entity. If you chose a Contact's email address, you must have the | , and the Contact's ID | is as a | ||
For destination Custom Object Data or Account It is one | One of the field names from your custom object or account data query. For example, if your query is:
| b
then the value should be | one
| , or | , or | b
| The field name is used to identify the custom object or account 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. | Update Rule | -
| -
| -
| -
| The rule is used when doing updates on existing data. For more information about this parameter, see the Oracle Eloqua Developer Help Center. | |||||
Skip invalid records | If | youchecked | when Eloqua synced data and you receive a data rows error, the export job is still a success, Eloqua will return success even if it encounters data row errors. Otherwise, the job | failedwill fail if there are invalid records. | ||||||||
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. | ||||||||||
Auto Delete Duration | integer | The length of time (in seconds) before the import definition will be automatically deleted, 0 or greater than 3600 |
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.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
SELECT col_a, col_b, col_b FROM your_table; |
For example, the following query to export contact data does not match any real users and is for demonstration purposes only.a contact, you could use queries similar to these:
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
SELECT c_emailaddress, c_firstname, c_lastname FROM contact; |
...
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 skipInvalidRecordsskip_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_contactcustom_object.sql query.
The update_rule accepts the following values:
- always
- ifNewIsNotNull
- ifExistingIsNull
- useFieldRule
Obtain the You can get custom_object_name from the Oracle Eloqua Console.
Code Block |
---|
_export: td: database: eloqua_db +eloqua_custom_object_export_task: td>: export_contactcustom_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 skipInvalidRecordsskip_invalid_records: true mapCustomObjectToContact map_custom_object_to_contact: true, performCaseSensitiveSearchperform_case_sensitive_search: false, cdoSourceFieldcdo_source_field: Email_Address, contactMapFieldcontact_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.
Code Block |
---|
_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 |