Nexxen Integration for Dealerships

Video reach and audience tooling bought together, and a straight answer about the state of the connection.

Nexxen operates on both sides of the video advertising market. It runs a demand side platform that buyers use to place connected television and online video campaigns, and it also runs supply side technology that publishers use to sell their inventory. Around both sits a data and audience toolkit that is stronger than most independent video platforms offer.

For a dealer group the relevant product is television style video delivered to streaming households in a defined trade area, planned against audience segments rather than programme schedules. A thirty second spot reaches a household watching a streaming service, and the buy is defined by geography, household attributes and frequency rather than by a network and a daypart.

The reason this is a group conversation more than a single rooftop one is the shape of the cost. Video production, minimum flight sizes and the analytical work of using the audience tooling all favour a buyer with several stores and a marketing person who owns the plan. A single store with no video asset gets very little of what makes this platform interesting, which is the same structural point our page on connected TV advertising for dealers makes at length.

The case is reach and conquest. Streaming video puts a store in front of households that no search campaign will ever surface, because those households are not searching yet, and it does it with the one creative format that still carries a brand: motion, sound and a face. For conquest work against a competing point across town, a geography plus household audience buy is a legitimate instrument, and the audience tooling here is a real differentiator over buying video as a line item inside a general purpose platform.

The first honest objection is measurement patience. Results on this kind of buy are not reliably attributable inside twenty four hours, and anybody who tells you otherwise is describing a dashboard rather than a customer. The channel is bought for reach against a defined audience, and it has to be judged over a flight rather than over a morning.

The second objection is structural, and worth asking the vendor about directly. A company that operates both a buying platform and supply side technology has an interest in where your money lands. That is not a scandal, it is the shape of the industry, but a buyer should ask what share of delivered impressions came through the vendor's own supply and get the answer in writing.

The third is simpler. Without a produced video asset, none of this is available to you at any price, and creative production is not something we supply.

Not started. The published test for that status is blunt: no adapter file exists in the ad gateway for this platform. There is no authorization URL, no credential block, no checklist and no partially written code. It is a name in the catalogue with a status attached, which is the honest description of eighty entries in this directory.

That is a different position from a registered platform. A registered one has a scoped adapter and a written wire-up sequence, so the work is countable and the remaining question is queue position. Here the first task would be writing the adapter itself, which is why the request queue is the whole mechanism rather than a formality.

Access class is PARTNER, and that gate belongs to the vendor rather than to us. Credentials for the buying platform come through an application the vendor reviews, so a store cannot simply register a developer account and be trading the same week. That step would sit in front of the engineering regardless of how many dealers asked, and it is precisely the kind of dependency this directory names instead of hiding.

Written as a design for a connection that does not exist, so that the shape is clear rather than implied.

There is no form inside a streaming video ad, so nothing about this channel captures a lead directly. Response arrives later, on a landing page or by phone, which is why the reporting row above counts views and reach rather than submissions.

The reason an unbuilt platform can be described this precisely is that the gateway it would join already exists and has a fixed shape.

One library inside LeadLocate defines what any advertising platform must be able to do: hand us an authorization URL, exchange the credential for a usable token, list the accounts that credential reaches, 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. Adding a platform means writing that one file against those seven operations, not redesigning anything, and it cannot destabilise the network already implemented.

Credentials are encrypted with AES-256-GCM before storage. Every action taken against any network is written to an append only audit log carrying the company, the network, the user and the detail, stamped in UTC deliberately, because the table is shared across dealerships and a company local timestamp is one nobody can reconcile later. Campaign objects record which credentials created them and re-resolve those same credentials afterwards, so disconnecting an account never strands the work built underneath it. That is what a request buys: a place in a queue for a defined piece of work, not an open ended research project.

Two ways to advertise through LeadLocate, and the store picks.

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 bills as one line rather than a stack of platform statements. Nothing to apply for and no credential to hold.

The second is your own account, where the account your group already holds carries the campaigns, on your billing, in your name, with your terms intact. For this platform that route does not exist yet in either direction: there is no adapter, and access is partner gated, so the vendor would also have to approve the relationship.

One boundary that applies everywhere in the gateway: deploying, activating, pausing and reading spend is done by our team today rather than by a control on your dashboard. That is a deliberate constraint while the connection layer is young.

Four things in order, and only two of them are ours. A request from a store that would fund it. A queue position earned against every other request in the catalogue. An adapter file written against the seven operations, with a credential block and a verification path. And a vendor reviewed application for buying credentials, which runs on the vendor's timeline rather than ours.

That last one is worth weighing before you ask. On a partner gated platform, a store that already holds an account relationship changes the calculation dramatically, because the part we cannot influence is already done. Say so in the request if it applies to you.

On measurement, plan the flight before you plan the report. Reach, completed views and frequency are readable across a flight. A same day response curve is not, because a household that saw a spot on Tuesday evening may walk onto the lot on Saturday with no traceable path between the two. Sell yourself on reach and conquest here, and keep the lead counting to the channels that capture an opt in directly, several of which are already connected or registered in this directory.

There is no connection, so the temptation on a page like this is to describe capability as though the absence were a detail. It is not.

We have never made a call to this platform. No adapter, no credential, no test, no deployment. Nothing about the seven operations has been implemented for it.

We do not emit a vehicle catalog or an inventory feed to this or any advertising platform, so dynamic vehicle creative in video units is not something we deliver.

We do not run a server side conversions API of any kind, and we do not install or manage pixels. On a video channel that matters more than usual, because view through measurement depends entirely on signals we do not send.

We do not export a hashed customer list for audience matching or suppression, which is exactly the input that would make this platform's audience tooling worth paying for. If audience activation from your own database is the reason you are interested, the honest answer is that we are not the route to it.

We do not produce video creative, and no adapter would change that.

Say the name, attach your group and rooftop count, and describe the reach problem rather than the platform. Requests are recorded against the platform they name and the tally is what decides build order, because a dealer ready to fund a channel is a better prioritisation signal than a preference expressed internally.

Two details make a request in this category count for more. Tell us whether you already hold an account relationship with the vendor, since that removes the gate we cannot clear. And tell us whether you have video creative in hand, because a platform whose entire value is motion and sound is not worth building for a store with nothing to run on it.

Meanwhile the managed path is live and depends on none of this. Platform pricing sits on the pricing page and does not change with which networks you turn on.

Does LeadLocate integrate with Nexxen today?

No. Not started is the published status, and its test is that no adapter file exists in the ad gateway for this platform. There is no credential, no checklist and no partially written code, and demand is what decides whether that changes.

Can I use my own Nexxen account?

Not through the CRM, for two separate reasons. The connection has not been written, and access is partner gated, so credentials come through an application the vendor reviews. Holding the account relationship already would remove the second reason but not the first.

What happens if I request Nexxen?

It is recorded against this platform by name and counted. That count is the input to build order across the whole catalogue, and a person answers you with a range or a reason rather than silence. Requests that come with a budget and a rooftop count carry more weight.

How quickly could I tell whether a video buy worked?

Not in a day. This kind of buy is judged across a flight on reach, completed views and frequency, because a household that watched a spot may act days later with no traceable path. Plan the measurement window before the campaign, not after it.

What does partner access mean for a single rooftop store?

It means the vendor reviews an application before issuing credentials, and a small independent may not be the buyer it wants. That gate is theirs rather than ours, and it exists whether or not our side is built. The managed path avoids it entirely.

Can you target my own customer list on this platform?

No. Audience matching from your database would require exporting a hashed customer file, and we do not build or send one to any advertising platform. That is a firm limit rather than a queue item, and it applies to every entry in this directory.

Requests are recorded against the platform they name and the tally decides build order. Tell us your group, your trade area and whether you have a spot ready to run.