Skip to content

Commit 8137632

Browse files
committed
Edits
1 parent 1c4e90d commit 8137632

File tree

1 file changed

+4
-4
lines changed
  • src/connections/destinations/catalog/actions-the-trade-desk-crm

1 file changed

+4
-4
lines changed

src/connections/destinations/catalog/actions-the-trade-desk-crm/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,10 +33,10 @@ Before you begin, generate a [long-lived token](https://partner.thetradedesk.com
3333
6. Once authenticated, enter your Authentication Token and Advertiser ID from your [The Trade Desk's CRM Data Platform API](https://api.thetradedesk.com/v3/portal/data/doc/DataIntegrateCRMData){:target="_blank"} account. Enable the destination by toggling **Enable Destination** and click **Save Changes**.
3434
7. Navigate to the **Mappings** tab, click **New Mapping**, and choose **Sync Audience to CRM Data Segment**.
3535
8. In the **Select mappings** section, input the PII Type and maintain other defaults. Click **Save** and toggle to enable the mapping.
36-
_**Create only one mapping for every instance.**
37-
- If any of the emails stored in your Engage Audience are already in a hashed format, please specify the PII type as `Hashed Email.` Failure to do so will result in Trade Desk categorizing the hashed records as invalid during the ingestion process.
38-
9. Return to **Engage > Audiences** and select the Audience from Step 1.
39-
10. Click **Add Destinations** and choose The Trade Desk CRM destination you just created. In the settings that appear in the side panel, enable the **Send Track** option and **do not** alter the Audience Entered/Audience Exited event names. Fill out the Audience Settings, specifically the region field, with the geographical region of the CRM data segment based on the origin of the PII (US, EU, or APAC). Click **Save Settings**.
36+
- **Create only one mapping for every instance.**
37+
- If any of the emails stored in your Engage audience are already in a hashed format, please specify the PII type as `Hashed Email.` Failure to do so results in The Trade Desk categorizing the hashed records as invalid during the ingestion process.
38+
9. Return to **Engage > Audiences** and select the audience from Step 1.
39+
10. Click **Add Destinations** and choose The Trade Desk CRM destination you just created. In the settings that appear in the side panel, enable the **Send Track** option and **do not** alter the Audience Entered/Audience Exited event names. Fill out the audience settings, specifically the region field, with the geographical region of the CRM data segment based on the origin of the PII (US, EU, or APAC). Click **Save Settings**.
4040

4141
Setup is now complete, and the audience starts syncing to The Trade Desk.
4242

0 commit comments

Comments
 (0)