This integration is currently in Beta, and we’re actively gathering feedback to improve its functionality and stability.
The Adobe Target connector allow marketers upload customer profiles data directly from TD platform to Adobe Target
- Basic knowledge of Treasure Data, including the TD Toolbelt.
- Basic knowledge of Adobe Target.
- Adobe Client Code and Adobe Profile API Access Token in case of Adobe Profile API Authentication enable
If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.
Please find the complete list of static IP addresses, organized by region, at the following link:
https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/
- Updates generally occur in under one hour, but might take as long as 24 hours to be reflected.
- Login into
experience.adobe.comthen choose Target
- From Target home choose Adminstration -> Implementation -> Copy Client Code
- From Implementation page scroll down to Profile API section. Click on Require Authentication to enable if needed. After that click on Generate Authentication Token and copy and save the token for connector configuration.
Before running your query, you must create and configure the data connection on the TD Console. As part of the data connection, you provide authentication to access the integration. Complete the following steps.
- Open TD Console.
- Navigate to Integrations Hub > Catalog.
- Search for and select Adobe Target. Hover over the icon and selectCreate Authentication.
- Ensure that the Credentials tab is selected, and then enter credential information for the integration. Choose one of the following
5. Select Continue. 6. Type a name for your connection. Select Done.
Authentication Fields
| Parameter | Description |
|---|---|
| Client Code | This is a unique identifier provided by Adobe Target, used for Adobe API authentication. Retrieved from Target admin settings |
| Adobe Profile API Authentication Token | Optional. Only required when Adobe Profile API authentication is enabled |
The TD Console supports multiple ways to export data. Please follow these steps to export data from the Data Workbench.
- Navigate to Data Workbench > Queries.
- Select New Query, and define your query.
- Select Export Results to configure the data exporting.
- Select an existing Adobe Target authentication or create a new one described previously
- Select Done.
| Field | Description |
|---|---|
| Bulk Update API Version | API Version to be used. - v1: support for bulk profile update only. (mbox.id is supported by only v1) - v2 (default): create profile if not found. |
| Guaranteed Upload | Adobe Target connector upload profile data file by file. If we checked the system will waiting for last uploaded file process successfully from Adobe Server Side before upload the next one. |
| Skip invalid records? | If checked, the job will skip the invalid record and continue to handle the next record. Otherwise, the job will stop. |
To successfully upload/modify user profile data to Adobe Target, you must construct an export query that adheres to specific data specifications.
| Specification | Description |
|---|---|
| Required Fields | At least one of the following identifier fields must be present in your export query: - pc_id (Target-generated visitorID) - third_party_id (ID specified by the client application, which is passed to Target through an mbox call as mbox3rdPartyId) pc_id and third_party_id fields must be in String data type. |
| Custom Fields | Any fields not listed in the required fields will be automatically mapped to the profile param. These are displayed in Target as profile.paramName. |
You can also use CLI (Toolbelt) to export results to Adobe Target.
You need to specify the information for export to your Adobe Target server using the --result option of the td query command. For more information about the td query command, refer to this article.
The format of the option is JSON, and the general structure is as follows.
type: 'adobe_target'
client_code: xxxx
profile_api_token: xxxxx
api_version: v1
guaranteed_upload: false
skip_invalid_records: true$ td query --result '{"type":"adobe_target","client_code":"xxx","profile_api_token":"xxx", "api_version": "v1","guaranteed_upload":false,"skip_invalid_records":true}' -d sample_datasets "select ........ from ........" -T prestoThe following table identifies the configuration keys with descriptions.
| Config Key | Type | Required | Description |
|---|---|---|---|
| type | string | yes | value must be adobe_target |
| client_code | string | yes | Adobe Target client code |
profile_api_token | string | yes if Adobe profile api turn on | Adobe Profile API token |
| api_version | string | no | Select from v1, v2. Default is v2 |
guaranteed_upload | boolean | no | Default value is false. If set to true then next upload profile data will wait until current upload process done on Adobe Target Side |
skip_invalid_records | boolean | no | If set to true (default), this will skip invalid records and continue uploading valid ones. If set to false, this will terminate the job when an invalid record is encountered. |
For those whose would like to retrieve uploaded pcID via API, please add edge domain to profile fetch URL for exact location. Adobe Target implements geographically distributed serving architecture to optimize response time regardless of users' location. pcId profiles are routed to nearest edge. Check the batch upload status for edge domain where the data is routed to.
See Adobe Target's document for more information https://experienceleague.adobe.com/en/docs/target-dev/developer/implementation/privacy/allowlist-edges