All guides, by feature
Save your agency’s Trade Desk credentials
Open The Trade Desk card in Integrations, paste your TTD API token and Partner ID, and save. Orbit keeps one set for your whole agency.
Before you start
- You need
- A Trade Desk API token and your Partner ID.
- Where in Orbit
- Sidebar › Data › Integrations
Steps
Tick a step’s number when it’s done. We’ll remember where you were.
In the sidebar, open Integrations. Under AI Tools & MCP Servers, open The Trade Desk.
Under , paste your TTD API Token and enter your Partner ID. Default Advertiser ID (optional) can stay blank.
Choose the Environment, Production or Sandbox. Leave Read-only mode on unless agents should be able to make changes in The Trade Desk.
Press Save Credentials. Later, the button reads Update Credentials.
When it worked
Orbit confirms “Credentials saved”, and both the page and the Integrations card show Connected.
If something goes wrong
Orbit showsTTD API token is required for first-time setup
Paste your TTD API token. Once one is saved, you can leave the field blank to keep it.
Orbit showsPartner ID is required
Enter your Trade Desk Partner ID, then press Save Credentials again.
Orbit showstoken looks too short
Paste the whole token. Tokens under 8 characters are rejected.
It says Connected, but Claude’s Trade Desk tools fail.
Connected only means a token is saved; Orbit doesn’t test it with The Trade Desk. Paste a current token and press Update Credentials.
How it works
Explainer: The Trade Desk credentials and modes
Your agency saves one set of Trade Desk credentials in Orbit. Claude uses them through Orbit’s Trade Desk server, and Command Center checks them before a push to The Trade Desk.
| Field | What it does |
|---|---|
| TTD API Token | Your Trade Desk API token. Stored encrypted and never shown again. When updating, leave it blank to keep the current one. |
| Partner ID | Required. Your Trade Desk partner ID. |
| Default Advertiser ID (optional) | An advertiser to use by default. |
| Environment | Production or Sandbox. |
| Read-only mode on | “Writes blocked. Agents can read TTD data only.” This is the default. |
| Read-only mode off | “Writes allowed. Agents may create campaigns, ad groups, etc.” |
| Optional · DMP workflows credential | A separate credential that only the DMP toolset needs. |
- Connected means a token is saved. Orbit doesn’t check it with The Trade Desk.
- There’s one set per agency. Saving again replaces it for everyone.
- Once saved, the page shows the Partner, Environment, Mode and when they were Last updated.
- Command Center’s push checks include TTD credentials configured and TTD-MCP key issued.
Explainer: Two ways to connect Claude to The Trade Desk
Claude.ai connects through a custom connector that you approve with your Orbit login. Claude Code and other tools use an API key you create in Orbit.
| Claude.ai connector | API key | |
|---|---|---|
| Best for | Claude.ai. Orbit recommends it. | Claude Code and other tools that read an .mcp.json file. |
| How you connect | Add a custom connector in Claude.ai and approve it. | Create a key in Orbit and paste it into .mcp.json. |
| Listed under | Connected Clients (Claude.ai) | MCP API Keys (Claude Code / advanced) |
| When revoked | Stops at once. The person re-authorizes from Claude.ai’s connector settings. | Requests start failing within about 60 seconds. |
| What Claude can do | Set by Read-only mode. | Set by Read-only mode. |
- Each API key is shown once, when you create it. If you lose it, revoke it and create another.
- Keys last until they’re revoked. The table lists each one’s Prefix, Created date and when it was Last used.
- The approval screen in Claude.ai says what Claude may do: “Read and modify TTD data”, or “Read TTD data (agency is in read-only mode)”.
- Owners and Admins see and can revoke every Claude.ai connection at your agency. Everyone else sees only their own.