The Trade Desk Integration for Car Dealers

The largest independent demand side platform, what a connection to it would move, and why the queue decides whether it gets built.

The Trade Desk is the largest independent demand side platform, which in plain terms means it is a buying console that bids on advertising inventory it does not own. That independence is the whole product. Google sells you Google inventory first, Amazon sells you Amazon inventory first, and The Trade Desk has no inventory of its own to prefer, so the buy is assembled from open exchanges, premium publishers, connected TV apps, streaming audio and retail media networks in one place.

For a dealership, it is the platform behind a large share of what agencies sell as programmatic. If your store already buys display or connected TV through a regional agency, there is a reasonable chance the media is transacting here under somebody else's seat, with your name nowhere near the login.

The piece worth knowing by name is Unified ID 2.0, an identity framework built on hashed email addresses rather than third party cookies. It is the strongest answer the open internet has produced to cookie deprecation, and it is why buyers who need reach outside the walled gardens keep this platform in the plan.

The argument is reach without a landlord. A single audience definition can be delivered across display, connected TV, streaming audio and retail media, with frequency managed across all of it, which is something no individual network can do because each of them can only see its own delivery. For a store running a conquest push in a defined trade area, that unified frequency control is worth real money, because the alternative is paying three platforms to show the same household the same spot.

The honest objection is that this is not a dealership product. It is an agency product. Access is a contracted seat with commercial minimums, the interface assumes a trained buyer, and the fees sit on top of media in a way that a store with a modest monthly budget will feel immediately. Most single rooftop dealerships that reach for The Trade Desk end up buying it through a reseller, and at that point the store is paying for a layer of expertise it may already be paying an agency for.

The second objection is duplication. If your agency already runs The Trade Desk for you, a second seat inside a CRM does not make the media cheaper, it makes the reporting harder to reconcile. That is worth saying out loud before anybody asks us to build it.

Available on request, which on this directory is not a euphemism. The published test for that status is simply this: not started, and demand decides the order. No adapter file exists in the ad gateway for this platform, so there is no partial implementation to describe and no checklist to quote.

Access class is CERTIFIED, which is the vendor's gate rather than ours, and here it is the more interesting half of the answer. API access to this platform follows a commercial relationship: a contract, a certification, or a spend commitment agreed before a key is issued. That is a business step, not an engineering one, and no amount of work on our side removes it.

The practical consequence is that a request for this platform is really two requests. One asks us to write an adapter, which is scoped work of a known shape. The other asks whether a dealership or a group has, or can obtain, the commercial access that makes the adapter useful. A store that already holds a seat through a group changes that answer completely, which is why the request form asks.

Written as design, not description. None of it exists.

That last row is the one to read twice on this page in particular, because the platform's best known feature is an identity framework built from hashed email addresses and we do not produce one.

The reason a platform can sit at not started without that meaning never is that adding one is a defined shape of work rather than an open ended project.

Inside LeadLocate there is one library defining what any advertising network must be able to do: hand us an authorization URL, exchange the code for a token, list the accounts you own, deploy a campaign, pause or resume it, return spend and results, and prove on demand that the connection still works. Seven operations, one adapter file per network. A network that has not been started has not had its file written, and that is the entire difference between this page and the pages carrying a stronger word.

Everything around that file already exists and is not rebuilt per platform. Credentials are encrypted before storage with AES-256-GCM. Every action against a network lands in an append only audit log carrying the company, the network, the user and the detail. Campaign objects record which credentials created them and re-resolve those credentials afterwards, so disconnecting an account later does not orphan the work built under it. The platform with the shortest remaining distance to that contract is Meta, which is the one already through it.

Two ways to advertise through LeadLocate, and you choose.

The first is the webXintel Ads Network. It is included, our team builds and runs the campaigns from the selections you make in Leads Manager, and it arrives as one line rather than a stack of platform invoices. Nothing to contract for and no vendor certification to clear.

The second is your own account, which is what a page like this one is about. Connect the advertising account your store already holds and campaigns route through it instead, on your billing, in your name, with your history intact. For a certified platform that second path has a precondition we cannot supply: you or your group must hold the seat. If you do not and do not intend to, the managed path is the honest recommendation rather than a queue position.

One limit stated plainly, because it is true of the whole gateway: pushing, pausing and reading numbers from a network is done by our team today, not from your dashboard. That constraint is deliberate while the connection layer is young, and it is on the list to open up.

In order, and the first two steps are not engineering. Establish the commercial relationship with the vendor, since a certified platform issues credentials against a contract. Obtain API credentials under that relationship. Then, on our side, write the adapter, implement the credential exchange, implement account listing, implement campaign creation, implement status changes, implement reporting and implement verification.

Anyone who tells a dealership that connecting a certified platform is a weekend of work is describing only the last seven items and ignoring the first two, which usually take longer. We would rather set that expectation before a request than explain it afterwards.

On measurement, the honest expectation is patient. Open internet display and connected TV bought here influence a shopper in the days before a visit rather than in the hour after an impression, so a store judging a flight against next day form fills will conclude the channel does not work when what actually happened is that it was read too early. Lead capture is a clickout, meaning the shopper arrives on your website and your site decides whether anything is captured at all. If you want a channel that reads inside a day, the advertising overview points at the ones that do.

This is the section that makes a directory of unbuilt integrations worth publishing.

We do not export a hashed audience or onboard your customer list to any identity framework. Unified ID 2.0 works from hashed email addresses, and there is no export anywhere in our product that produces such a file. This is the single most likely thing to be implied on a page about this platform, and it is not true here.

We do not run a server side conversions API or upload offline conversions. No conversion events are posted from our stack to this platform in any direction.

We do not install or manage a tracking tag on your website. Attribution for a clickout buy depends entirely on tagging we neither place nor maintain.

We do not emit a vehicle catalog, so dynamic vehicle level creative driven by your inventory is not something we deliver here or anywhere else in the gateway.

No campaign has ever been deployed to this platform from the CRM, and no adapter exists that could deploy one. Nothing about this page should read as a connection in progress, because there is not one.

Ask, with the store attached. Requests are recorded against the platform they name and counted, and the tally decides build order, because a dealership ready to spend on a channel is a better input to that decision than any internal roadmap meeting.

Tell us one extra thing on this platform, because it changes the answer more than anything else: whether you or your group already holds a seat, or buys through an agency that does. A request from a store with existing access is a different project from a request that would need us to solve the commercial gate too, and we would rather sort those two into different piles than treat them as one number.

Meanwhile the managed path runs today and none of this blocks it. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with The Trade Desk today?

No. There is no adapter file in the ad gateway for this platform, so nothing partial exists to describe. It sits at available on request, which means not started, with demand deciding the order.

Can I use my own Trade Desk account?

Not through the CRM, because there is nothing to connect it to yet. Holding a seat already does matter for the queue though, since it removes the commercial step that usually takes longer than the engineering.

What happens if I request The Trade Desk?

It is recorded against this platform specifically and counted. The tally decides build order, and you will hear back from a person with a range or a reason rather than silence.

What does CERTIFIED mean here?

It describes the vendor's gate, not ours. API access follows a contract, a certification or a spend commitment agreed before a key is issued. That step exists whether or not we ever write the adapter.

Could you push my customer list in to build an audience?

No. We do not export a hashed audience file or onboard a customer list to any identity framework, including Unified ID 2.0. That capability does not exist in the product for any network.

My agency already buys here. Would connecting change what I pay for media?

No. An adapter changes where campaigns are created and how the record is kept, not what inventory costs. If your agency already holds the seat, the reconciliation problem is usually the thing worth solving first.

Requests are counted against the platform they name and the count decides what gets built next. Tell us whether you already hold a seat, and what you would run through it first.