Zeta DSP Integration for Car Dealers

Identity based targeting, a contract gated API, and a plain account of what the CRM does and does not do with either.

Zeta is a demand side platform built around an identity graph rather than around inventory access. The buying capability is ordinary enough, display and video and streaming placements across the usual exchanges. What the company sells is the layer above that: a large body of first party identity data, keyed heavily on email, which lets a campaign target people the graph believes are in market rather than pages the algorithm believes are relevant.

For a dealership there are two practical uses. The first is prospecting against modelled in market automotive audiences, which is what every platform in this family promises and what an identity graph is genuinely better positioned to do. The second is reactivation, which is more interesting. A store with a long service history and a lapsed customer list has an asset, and an identity based platform is the kind of tool that can put a message in front of those households across channels. That second use is the one this page has to be careful about, and the reason why is further down.

The argument is precision at the household level. Most programmatic targeting in automotive is a probability dressed as a segment, assembled from browsing behaviour that may or may not belong to a car shopper. A platform anchored on a durable identifier can carry a definition of a person across devices and channels, which means less waste at the same budget and a more honest frequency figure. For a store working a defined trade area with a defined equity position to mine, that is a real advantage over open exchange buying.

The honest objection is that you are buying somebody else's match rate and you cannot audit it. Every identity graph reports impressive coverage, and no advertiser has ever been given the raw means to verify how much of that coverage was a genuine match against the people they wanted. When a campaign underperforms it is nearly impossible to tell whether the creative failed or the match did.

The second objection is commercial rather than technical. The access class here is not casual, and platforms sold with a contract and a spend commitment are rarely a good first channel for a single rooftop. If you have not yet exhausted the channels covered on car dealership advertising, this is not where to start.

Available on request, and the test for that word is published so you can check it: no adapter file exists in the LeadLocate ad gateway for the platform. None does. Zeta is not among the twenty networks registered against the gateway contract, so there is no partial implementation to describe and no configuration block waiting on a key.

Access class is CERTIFIED, which is the strictest of the three and always describes the vendor's gate rather than ours. It means a contract, a certification or a minimum spend is required before API access is granted. That is a commercial conversation with a commercial threshold, and it happens on the vendor's terms whatever we build.

Keeping the two on separate axes matters most on a page like this one. A reader could reasonably assume that a network we have not built and a network the vendor keeps behind a contract are the same problem. They are not. One is engineering we control and schedule. The other is a negotiation with a spend floor attached, and no amount of code on our side removes it. Publishing both is the only way a dealership can tell which conversation it is actually having.

A design, not a description, since nothing runs. The four row shape is the same on every page in this directory so a built platform and an unbuilt one read alike.

Read the outbound row again. Audiences would be selected from the platform's own catalogue by name. Nothing about your own customers would travel outward, which on an identity platform is the single most important sentence on this page.

The reason this page can be precise about a platform we have not built is that building one is a known shape rather than a guess.

One library inside LeadLocate defines the contract every advertising network answers: an authorization URL, a token exchange, an account listing, a campaign deploy, a status change, a spend and results report, and a verification call. Seven operations, one file per network, no special cases. Twenty networks are registered against that contract and exactly one is implemented, a ratio published rather than hidden, because a directory that only listed the connections would be a wall of logos like everybody else's.

The surrounding machinery already exists and is shared by whatever comes next. Credentials are encrypted with AES-256-GCM before storage. Every action lands in an append only audit log carrying the company, the network, the user, the detail and a UTC timestamp. Campaign objects re-resolve the credentials that created them, so an account disconnected later does not orphan the campaigns built under it. That is why a request for a platform like this one is schedulable work rather than a research project, and why the integrations directory can publish a queue at all.

Two paths, and the difference matters more than the branding.

The managed path is the webXintel Ads Network. It is included with the platform, our team builds and manages the campaigns from what you select in Leads Manager, and the reporting returns inside the CRM alongside the activity it produced. Nothing on this page gates it and nothing on this page delays it.

The self connect path is where a named network belongs. You connect the advertising account your store already owns, campaigns route through it, and the spend history, the billing relationship and the account itself stay yours. Most vendors do not offer that option because it costs them the markup on your media. For Zeta DSP the option is not available, because there is no adapter to route through and, above that, a vendor contract that a login screen cannot substitute for.

Across both paths one limit holds today: our team performs the push, the pause and the spend read, not you from a dashboard inside the CRM. It is a constraint of a young connection layer rather than a product decision, and opening it up is queued work.

The commercial step comes first and it is the long pole. Certified access means a contract, a certification or a minimum spend before the API opens, so the question of whether a single rooftop can reach the threshold has to be answered before any engineering is worth scheduling. A dealer group with several stores is a different conversation from one lot, and it is worth being blunt about that rather than taking a request and going quiet.

The engineering afterwards is the ordinary seven operations, a credential block in the gateway configuration and a verification call. It is not the hard part and it never has been.

On measurement, an identity led campaign in a dealership trade area delivers readable impression data quickly, generally inside a couple of days. Whether it produced showroom activity is a slower and softer question, and on a reactivation campaign in particular the honest window is measured in weeks because service and repurchase cycles are slow. None of this is a promise about volume or about what any of it closes at. Nobody can promise that.

This is the section that matters most on an identity platform, because identity platforms are exactly where a vendor is tempted to imply more than it does.

We do not export a hashed audience of any kind. No Custom Audience, no customer match file, no email list uploaded to a graph for onboarding. Your customer records and your service history stay inside the CRM. If a reactivation campaign is the reason you are reading this page, that sentence is the answer to the question you actually have.

We do not emit a vehicle catalog or inventory feed to any advertising platform, so dynamic creative rendering your actual units is not something we produce.

We do not install or manage pixels, which on a demand side platform is how retargeting pools and site conversions are ordinarily built.

We do not run a server side conversions API and we do not upload offline conversions, so tying a delivered impression to a signed deal is not part of this.

No campaign has ever been deployed to Zeta from LeadLocate. Anyone describing a working connection is describing an intention.

Ask for it by name and attach the store, because requests are recorded against the platform they name and the tally is what decides build order. A dealership ready to spend on a channel is a better signal than any internal roadmap discussion, and it is the only signal this queue runs on.

On this platform specifically, say how many rooftops you are asking for. A certified vendor gate with a spend threshold answers differently for a group than for one lot, and knowing which you are changes whether the honest reply is a queue position or a recommendation to spend the same money somewhere with a lower floor. If the answer is the second one, you will hear it, and the rest of the directory is there precisely so you can see the alternatives with their statuses attached.

The managed path is live and waits on none of this. Platform pricing is on the pricing page and does not change with the networks you turn on.

Does LeadLocate integrate with Zeta DSP today?

No. The published test for available on request is that no adapter file exists in the ad gateway, and none does. On top of that, the vendor requires a contract or certification before API access, which is a separate gate we do not control.

Can I use my own Zeta DSP ad account?

Not through the CRM. There is no adapter to route campaigns through, so an account you hold with the vendor operates entirely on its own. Nothing in LeadLocate reads it, writes to it or reports on it.

What happens if I request Zeta DSP?

It is recorded against Zeta specifically and counted, and the count feeds build order. Because the vendor gate here carries a commercial threshold, the reply will also tell you plainly whether your store size makes the platform realistic.

Can you upload my customer list to build a match audience?

No. We do not export a hashed audience of any kind, to this platform or any other. Your customer list and service history stay inside the CRM, and no part of building an adapter would change that.

What does CERTIFIED mean here, exactly?

It is the vendor's gate, not ours. A contract, a certification or a minimum spend is required before API access is granted. It would still apply on the day an adapter shipped, which is why this directory tracks it on a separate axis from our own build status.

Is identity based targeting better than the alternatives for a car store?

Sometimes, and it is unverifiable from the outside. A graph can carry a person across devices, which reduces waste. You are also trusting a match rate you cannot audit, so treat the precision claim as a reason to test carefully rather than a reason to move the whole budget.

A certified vendor gate answers differently for a group than for one lot. Send the store count and the trade area, and the reply will be a queue position or a straight recommendation to spend the money elsewhere.