Merge pull request #6104 from segmentio/DOC-828

Updates to The Trade Desk CRM Destination docs [DOC-828]

Author: stayseesong

src/_data/catalog/slugs.yml

@@ -212,4 +212,6 @@ destinations:
   - original: "google-analytics-4-cloud"
     override: "actions-google-analytics-4"
   - original: "app-fit"
-    override: "actions-app-fit"
+    override: "actions-app-fit"
+  - original: "the-trade-desk-crm"
+    override: "actions-the-trade-desk-crm"

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

@@ -12,8 +12,7 @@ redirect_from: "/connections/destinations/catalog/the-trade-desk-crm/"
 
 This integration lets users link Engage audiences to The Trade Desk and transmit Personally Identifiable Information (PII), including email addresses and hashed emails. Users have the flexibility to configure their delivery preferences within Segment.
 
-> info ""
-> The Trade Desk destination can only be connected to Twilio Engage sources.
+The Trade Desk destination can only be connected to Twilio Engage sources.
 
 ## Getting started
 
@@ -31,30 +30,26 @@ Before you begin, generate a [long-lived token](https://partner.thetradedesk.com
 3. Search for **The Trade Desk CRM** and select the destination.
 4. Click on **Configure The Trade Desk CRM**.
 5. On the **Select Source** screen, your Engage space should already be selected as the source. Click on **Confirm Source**.
-6. After authenticating, 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.
+6. Generate a [long-lived token](https://partner.thetradedesk.com/v3/portal/api/doc/Authentication#ui-method-create){:target="_blank"} on [The Trade Desk's Developer Portal](https://auth.thetradedesk.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3Dttd-dev-portal%26redirect_uri%3Dhttps%253A%252F%252Fpartner.thetradedesk.com%252Fv3%252Fsignin-oidc%26response_type%3Dcode%26scope%3Dopenid%2520profile%2520email%2520ttdui_refresh%2520offline_access%2520applications%26code_challenge%3DG5xIiN4NLQYS_L9kqCGZyWg678USH1pV6D2Iqu1e1Q8%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D638441362885322803.NWFjOTk2NTMtMzkyOS00NmJmLWE3N2YtODZlYzZjNGQxZWQ1M2E3OGI1ZmUtOThmNC00MDA5LWFiNzQtZmZiZGI2OTUzMzMy%26state%3DCfDJ8BBsgv10-z9IvE3EffVp_QCSKM7pxVdw3rv-shU-_OG4utdVslWzvw8nfZ0D8TKi75uKGCMPp2hiM-IBxjjwToGR-ryK13SXlVMOGMxXj_FUEV8nQfnRR1oQN6YZED0-48NhERsQr96xbaz6a_pVR_z5OZWgQ6RR9MBMUkHYF5tFp651wtbno-7ES1-zsje7hCqzFMTAVV_qAoNur-f8MGkMdw7oSAOQmoYOW4zV2w6SIMLSIOkUvariDC9EAAVPYTjonQdieo2V0rYscC-aVG6U8ASV3yqJc6RmnGRUEVnKHPt-ZZcvy9PHA2-Et04QlGwz6b-buRbNXd3v1E6zuMC5F7dxcT3otr5TQ4yMuC1JA5VRxT4c1tFON2lY4jtxKuyQIQs5N3a59eFc1wGdUSo%26x-client-SKU%3DID_NETSTANDARD2_0%26x-client-ver%3D6.10.0.0){:target="_blank"}. 
+7. After authenticating, 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**.
+8. Navigate to the **Mappings** tab, click **New Mapping**, and choose **Sync Audience to CRM Data Segment**.
+9. In the **Select mappings** section, input the PII Type and maintain other defaults. Click **Save** and toggle to enable the mapping.
    - **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**.
+10. Return to **Engage > Audiences** and select the audience from Step 1.
+11. 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.
 
 To sync additional Audiences from your Engage space, create a separate instance of The Trade Desk CRM Destination.
 
 {% include components/actions-fields.html settings="true"%}
 
-## Public Beta Instructions
-
-* The Segment team needs to enable the feature for your Engage spaces.
-* After you agree to join the public beta, Segment enables all Engage spaces that are part of your Segment workspace.
-* New Engage spaces you create won't be automatically enrolled. Contact your Account Team/CSM to get these spaces enrolled.
 
 ## Limitations
 
 * An audience must have at least 1500 unique members; otherwise, the destination fails, and the data won't sync.
-* Audience sync occurs once per day.
+* Audience attempts to sync once per day.
 * Audience sync is a full sync.
 
 ## FAQs