Cadent Integration for Car Dealers

Convergent television buying, identifier free targeting, and a plain account of what the CRM can and cannot do with it.

Cadent sits in the part of the market that television buyers call convergent. Its purpose is to buy across broadcast and cable inventory and across streaming inventory from the same plan, so a schedule can be built once and delivered wherever the household happens to be watching. That is a different proposition from a pure streaming platform, and it exists because most markets still contain a large audience that watches television the old way alongside a growing one that does not.

The second characteristic worth knowing is the targeting approach. Rather than leaning on a durable personal identifier, the platform models audiences with machine learning against contextual and behavioural signals, which is the direction the whole television market has been pushed by identifier loss. For a dealership the practical effect is that you describe the audience you want in market terms and the system finds delivery, rather than you assembling a list. The channel case for streaming specifically already lives on connected TV advertising for dealers.

The case is coverage of one market rather than one screen. A store still running broadcast spots has an audience it is reaching and an audience it is missing, and buying those two separately means paying twice for the household that sees both and never knowing the real frequency on anyone. A convergent plan is the only structure that answers the frequency question honestly, and for a dealership that already spends on television it is a cost control argument before it is a reach argument.

The honest objection is that television is not a lead channel and treating it as one will end badly. It produces no click, no form and no contact record. It moves brand preference and it moves walk in traffic over months, and a store that buys it expecting next week's opt in count to jump has bought the wrong thing. Results here are not reliably attributable in a short window, which is a statement about the medium rather than about any vendor.

The second objection is the floor. This is a platform with a commercial gate, and the production quality expected on a television screen is not the production quality a display banner survives with. If your total marketing budget is small, spend it where the feedback loop is fast and read car dealership advertising for the alternatives.

Available on request. The published test is that no adapter file exists in the LeadLocate ad gateway for the platform, and that is exactly the situation. Cadent is not among the twenty networks registered against the gateway contract. Nothing is half written, no credential block is waiting, and no code path in the CRM has ever addressed their API.

Access class is CERTIFIED, the strictest of the three, and it always describes the vendor's gate rather than ours. A contract, a certification or a minimum spend is required before API access is granted. Television has always been sold that way and the programmatic layer over it has inherited the habit, so this is not an unusual position for the category.

The reason those two facts are printed on separate lines is that they behave differently. Our missing adapter is scheduled work we control. The vendor's contract is a negotiation with a spend threshold attached, and no amount of code removes it. A dealership reading a competitor's logo wall cannot tell those apart, which is the entire argument for publishing a status with a stated test beside it instead of an icon.

A design rather than a description, since nothing runs. Every page in this directory uses the same four rows so a connected platform and an unconnected one read the same way.

There is no lead row in the return direction and there never could be. A television plan hands back delivery, not people. Any activity your store sees arrives because somebody called or walked in, and no reporting integration will ever change that.

Underneath every platform in this directory sits one library, and understanding it is what makes a request answerable rather than aspirational.

The library defines seven operations that any advertising network must answer: produce an authorization URL, exchange the returned code for an access token, list the accounts the connected user controls, deploy a campaign, change its status, report spend and results, and verify on demand that the credentials still work. A network is added by writing one adapter file against those seven. Nothing else in the CRM changes and nothing already running is disturbed.

Access tokens are encrypted with AES-256-GCM before storage. Every action taken against a network is written to an append only event log carrying the company, the network, the user and the detail, stamped in UTC deliberately, because those tables are shared across dealerships and a local timestamp is one nobody can reconcile afterwards. Campaign objects record which credentials created them and re-resolve those same credentials later, so an account disconnected next quarter does not strand the work built under it. None of that would need rebuilding for Cadent, and the directory says what is actually missing instead of implying a connection with a logo.

There are two ways to advertise through LeadLocate and you pick.

The first is the webXintel Ads Network. It is included, our team builds and operates 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 set up, no vendor application to file, and no dependency whatever on the state of this page.

The second is your own account, connected to the CRM so campaigns sit on your billing, in your name, with your spend history intact. That is the path this page documents, and for Cadent it does not exist. A relationship you already hold with them stays exactly where it is, and nothing in the CRM reads it or writes to it.

One limit stated plainly, because it holds across the whole gateway even where a network is fully built: pushing, pausing and reading numbers from a network is done by our team today rather than by you from a dashboard. That is a deliberate constraint while the connection layer is young, and opening it up is queued work rather than a promise.

The commercial step comes first and it is the long one. Certified access means a contract, a certification or a minimum spend before the API opens, so the honest first question is whether your store or group can reach that threshold at all. That question is worth answering before any engineering is scheduled, because a queue position on a platform you cannot buy is not a favour.

The engineering after it is the ordinary seven operations, a credential block in the gateway configuration and a verification call. That has never been the hard part on a platform like this.

On measurement, delivery data reads quickly. Whether the schedule moved anything does not, and the platform's own conventions in this category say results are not reliably attributable inside a short window. Expect to judge it on store level trend over a season, on call volume and on walk in traffic, and refuse any presentation that puts an impression total next to a lead count and divides. That number is arithmetic, not evidence. None of this is a promise about volume or about what any of it closes at, and nobody can promise that.

These gaps are true whether or not an adapter is ever written, and on a television platform two of them decide what the channel can honestly be measured on.

We do not upload offline conversions and we do not run a server side conversions API. That is the headline gap here, because offline upload is the standard method anyone uses to connect a television exposure to a delivered vehicle. Without it, the join between a schedule and a signed deal is an inference, and we will not describe it as anything else.

We do not export a hashed audience built from your customer list, which rules out targeting your own owner base through the platform's matching.

We do not emit a vehicle catalog or an inventory feed to any advertising platform, so inventory driven television creative is not something we produce.

We do not install or manage pixels, which is how site side response to a spot would ordinarily be captured.

No campaign has ever been deployed to Cadent from LeadLocate, because nothing in our code can reach them.

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 conversation, and it is the only signal the queue runs on.

Two things make the reply useful on this platform. Say how many rooftops you are asking for, since a certified gate with a spend threshold answers differently for a group than for one lot. And say what you are already spending on broadcast, because the strongest argument for convergent buying is usually that a store is paying twice for the same household and cannot see it. If the honest reply is that your money works harder on a faster channel, you will get that instead of a queue position, and the rest of the directory lets you compare with the statuses attached.

The managed path runs today and waits on none of this. Platform pricing is on the pricing page.

Does LeadLocate integrate with Cadent today?

No. The published test for available on request is that no adapter file exists in the ad gateway, and none does. The vendor also gates API access behind a contract or certification, which is a separate condition we do not control.

Can I use my own Cadent ad account?

Not through the CRM. There is no adapter for campaigns to route through, so any relationship you hold with the vendor runs entirely on its own. Nothing in LeadLocate reads it, changes it or reports on it.

What happens if I request Cadent?

It is recorded against Cadent specifically and counted, and the count feeds build order. Because the vendor gate carries a commercial threshold, the reply will also say plainly whether the platform is realistic at your store count.

Can you tell me how many leads a television schedule produced?

No, and treat any vendor who will with suspicion. Television hands back delivery, not people, results are not reliably attributable in a short window, and we do not upload offline conversions that would let anyone join a schedule to a signed deal.

Does convergent buying mean I can drop my broadcast schedule?

Not necessarily, and that is not the argument. The argument is that buying broadcast and streaming separately hides your real frequency on the households that see both. Whether the mix should change is a media planning question specific to your market.

What does CERTIFIED mean on this page?

It is the vendor's gate rather than ours. A contract, a certification or a minimum spend is required before API access is granted, and that would still be true on the day an adapter shipped. This directory tracks it on a separate axis from our own build status for exactly that reason.

Convergent buying earns its keep when a store is already paying twice for the same household. Tell us the market, the rooftop count and what you spend on television now, and you will get a straight answer.