Merge pull request #5534 from segmentio/rajul/ttd-docs-update

The Trade Desk CRM DOCS Update

Author: rchinn1

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

@@ -33,10 +33,10 @@ Before you begin, generate a [long-lived token](https://partner.thetradedesk.com
 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**.
 7. Navigate to the **Mappings** tab, click **New Mapping**, and choose **Sync Audience to CRM Data Segment**.
 8. In the **Select mappings** section, input the PII Type and maintain other defaults. Click **Save** and toggle to enable the mapping.
-   - If you see a field labeled "Segment Name," please input the same name as the audience you have connected the destination to. Ensure that there is no existing segment in TTD with the identical name.  Additionally, fill out the "Region" field with the geographical region of the CRM data segment, based on the origin of the PII.
-   - _**Create only one mapping for every instance.**_
-9. Return to **Engage > Audiences** and select the Audience from Step 1.
-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. If you missed providing the Segment Name and Region in step 8, please complete the Audience Settings, specifically the region field, with the geographical region of the CRM data segment based on the origin of the PII. Please note that the Public Beta only supports `US`. Click **Save Settings**.
+   - **Create only one mapping for every instance.**
+   - 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. 
+9. Return to **Engage > Audiences** and select the audience from Step 1.
+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**.
 
 Setup is now complete, and the audience starts syncing to The Trade Desk.
 
@@ -68,4 +68,5 @@ The CRM endpoint maps email addresses into UID2s. If it's a valid email address,
 
 #### What PII format should I send?
 
-The Trade Desk recommends transmitting personally identifiable information (PII) in its original, non-hashed format. TTD's preference is to handle the hashing of the data on their end.
+The Trade Desk recommends transmitting personally identifiable information (PII) in its original, non-hashed format. TTD's preference is to handle the hashing of the data on their end (PII type as `Email`). However, if your data already contains any hashed emails, please designate the PII type as `Hashed Email.`
+