All guides, by feature
Connect Claude.ai to The Trade Desk
Add Orbit’s Trade Desk server as a custom connector in Claude.ai, then approve it with your Orbit login. No API key is needed.
Before you start
- You need
- Your agency’s Trade Desk credentials saved in Orbit. Without them the connector authorizes, but its tools fail.
- Where in Orbit
- Sidebar › Data › Integrations
Steps
Tick a step’s number when it’s done. We’ll remember where you were.
Open Integrations, choose The Trade Desk, and press Connect with Claude.
Under Claude.ai (recommended), press Copy name and Copy URL to copy the connector’s name, TTD via Orbit, and its Remote MCP server URL.
In Claude.ai, open Settings → Connectors → Add custom connector, paste the name and URL, and press Add.
In the tab that opens, sign in to Orbit if asked, check the permissions, and press Approve.
When it worked
Your connection is listed under [[Connected Clients (Claude.ai)]] on The Trade Desk page, marked “you”.
If something goes wrong
Orbit showsHeads up — your agency hasn't configured The Trade Desk yet.
Save your agency’s credentials on The Trade Desk page in Orbit. The connector authorizes anyway, but its tools fail until they’re saved.
Orbit showsYour account is not associated with an agency. Ask your administrator to invite you to an agency before connecting this integration.
Sign in with the Orbit login you use at your agency, or ask an Owner or Admin to invite you from Team.
Claude can read The Trade Desk but can’t change anything.
Your agency has Read-only mode on, and the approval screen says “Read TTD data (agency is in read-only mode)”. Switching it off lets agents create and change campaigns.
How it works
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.
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.