> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/trade-desk/onboarding.md).
# Onboarding
In order to add the Trade Desk channel, you'll need to obtain the following pieces of information:
* Advertiser ID - this ID is used to send events to your account
* Event Mapping - this is a list of event IDs defined by Trade Desk that you can map to EdgeTag's events
You'll need to contact your Trade Desk representative to obtain this information.
### Adding the Trade Desk Channel
After providing a name for the channel, enter the advertiser ID supplied by the Trade Desk representative into the **Advertiser ID** field.\
\
Next, we need to enter the Pixel ID that Trade Desk provided.
To configure event mapping, enter each event ID into the **Tracking Tag ID** field and match it with the Browser Event to which you would like to map the event. You can use any of the standard events EdgeTag provides, or you can enter your own.
{% hint style="warning" %}
Events should be created under the Universal Pixels tab in Trade Desk
{% endhint %}
After you're done, click the **Save & Deploy** button. Once the tag has been deployed, events should automatically start flowing into Trade Desk.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.edgetag.io/channels/trade-desk/onboarding.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.