# Limits & errors

What The Trade Desk connection does not do, its limits, and the common errors when connecting or sending conversions.

## Limits

| Limit | Value |
|-------|-------|
| Tracking tags per profile | One |
| Events per request to The Trade Desk | Up to 1,000 |
| Match keys | TDID, UID2 or a UID2 token |

## What you cannot do

- Send a test event: The Trade Desk has no test mode, so Zernio sends nothing for one
- Match on email or phone: turn them into UID2s with your own UID2 integration
- Restate or retract a conversion: The Trade Desk keeps its count
- Read campaigns or spend, or post, schedule or use the Inbox API on a Trade Desk account
- Use more than one tracking tag on a profile: connect each one on its own profile

## Common errors

| Error | Cause | Fix |
|-------|-------|-----|
| `400` naming `advertiserId` or `trackerId` on connect | The id is not a short code such as `abc1234` | Copy the id again from The Trade Desk. |
| `403` on connect | The Ads add-on is off | Turn on the Ads add-on. |
| `409` with `profile_platform_conflict` | The profile already has another tracking tag connected | Disconnect it first, or use another profile. |
| A failure naming "matches a conversion only by its own ids" on an event | No `tdid`, `uid2` or `uid2Token`, or `adUserData` denied | See [Conversions](/platforms/the-trade-desk/conversions#if-it-fails). |
| `The Trade Desk has no test mode` on an event | The request has a `testCode` | Send it without `testCode`. |
| Conversions missing on the tag, no error | A wrong Advertiser ID or tag id: The Trade Desk does not check them | Check both ids and [connect again](/platforms/the-trade-desk/connect). |

## Related

- [Connect](/platforms/the-trade-desk/connect)
- [Conversions](/platforms/the-trade-desk/conversions)
- [Rate limits](/guides/rate-limits)