Integrate The Trade Desk with Adobe Experience Platform and collect The Trade Desk ID
When you integrate The Trade Desk (TTD) with Adobe Experience Platform (AEP), there is uncertainty in collecting and mapping the Trade Desk ID through Web SDK. A clear approach helps you capture the identifier correctly and ensures that the integration uses the correct identity namespace. To resolve the issue, enable the proper ID sync and ingest the identifier through the supported mapping process.
Description description
Environment
- Product: Adobe Experience Platform (AEP)
- Constraint: Web SDK in use
Issue/Symptoms
- Uncertainty exists regarding the collection of the Trade Desk ID on a Web SDK site.
- Difficulty arises when identifying the correct Adobe Experience Platform identity namespace for the Trade Desk ID.
- Guidance is required on capturing the identifier through Adobe’s ID sync process.
- Clarification is needed on additional activation steps for validating Trade Desk sync behavior.
Resolution resolution
The Web SDK does not provide a direct API to retrieve the Trade Desk ID. Use one of the supported approaches below.
Approach 1: Use Adobe’s built‑in ID sync with The Trade Desk
The Trade Desk is already integrated into the Experience Cloud ID (ECID) and Unified Identity Service (UIS) ecosystem through the TradeDesk namespace (DPID 903). This namespace manages cookie‑based mapping between ECID/Demdex IDs and TTD IDs.
Note: Contact Adobe Support to ensure that partner ID 903 is enabled for your organization.
Approach 2: Ingest an existing client‑side TTD ID into AEP
If you already captured a TTD ID in the browser, you can send it to AEP as a standard identity using a dedicated identity namespace.
Enabling TTD ID Sync in Web SDK
Follow these steps to activate the Trade Desk sync through your datastream.
Step 1: Enable 3rd‑party ID sync
- In AEP, navigate to Data Collection
>Datastreams>Your Web SDK Datastream>Advanced options>3rd Party ID Sync. - Use the same container ID you previously used with ECID or Audience Manager. For most implementations, this value is
0.
Step 2: What does the Web SDK do automatically
After you enable 3rd‑party sync, Web SDK:
- Calls the ECID/Visitor ID Service through Adobe Edge.
- Retrieves all configured partner sync pixels, including Trade Desk (
DPID 903). - Executes the partner sync in the browser.
Validating the Integration
To verify that the Trade Desk sync is working, open your browser’s Developer Tools and check the Network tab for requests containing ibs?dpid=903. If these calls appear, the Trade Desk sync pixel is firing correctly.
Notes:
- Review the official Adobe Experience Platform documentation for The Trade Desk connection.
- Support does not provide implementation guidance beyond documented configuration options. For solution‑level recommendations, consult your Adobe account team.