Run Rokt from Your Dealership CRM

Reaching people in somebody else's confirmation screen, and the honest standing of that idea inside the ad gateway.

Rokt does not buy feed placements or banners. It operates in the confirmation moment of other companies' transactions: the screen a person sees immediately after booking a flight, buying insurance, ordering furniture or completing any of thousands of other purchases. In that space it presents relevant offers from other advertisers.

The interesting part for a dealership is not the format, it is the signal. A confirmation screen carries context nothing else does, because the platform knows what the person just did. Someone who just paid a moving company has a strong reason to be thinking about vehicles. So does someone who just closed on a home, just booked a long relocation, or just bought a policy on a car they are about to replace. Those are life events, and life events move vehicles far more reliably than a browsing session does.

The advertiser experience is closer to a media partnership than to a self serve account. Placements are negotiated, creative is constrained by the surface it appears in, and the response to an offer is a clickout that lands the person somewhere on your side. Nothing is submitted inside the unit itself, which puts the whole burden of conversion on the page you send them to.

The case is timing on a life event. Most advertising in this directory works by finding a signal of interest and hoping it becomes intent. This platform reaches people at the moment a documented event has just occurred, and several of those events genuinely predict a vehicle purchase within months. Relocation is the clearest. A household that just moved is a household re-evaluating what it drives, how far it commutes and whether a second vehicle is now necessary, and almost nothing else in paid media reaches that household at that hour.

The honest objection is that the moment cuts both ways. A person on a confirmation screen just finished spending money and is trying to close a tab. Attention is real but it is short, defensive and pointed at the transaction they came for, not at yours. Interrupting it with something as large and slow as a vehicle purchase is a hard ask, and the offers that perform in that space are typically small, instantly comprehensible and cheap to accept. A dealership does not have one of those.

The second objection is control. You are appearing inside somebody else's checkout, and which checkout is not entirely yours to choose. That is a brand context question a store should ask before signing, and it is a different question from the ones asked of an ordinary display buy. If the answer matters to your franchise, get it in writing. Read expectations against what to expect from car sales leads before setting a target, because a lead from a confirmation screen is a colder object than a lead from a search result.

Available on request, which on this directory is a status with a published test rather than a polite deferral. The test is that no adapter file exists in the LeadLocate ad gateway for the platform, and that is the case here. There is no partial implementation, no stub returning encouraging numbers, and no code in the CRM that has ever spoken to their systems.

Access class is PARTNER, and that axis describes the vendor's gate rather than ours. Credentials require an application the vendor reviews before issuing them. On a platform where placements are negotiated rather than bought from a dashboard, that review is not a formality either. It is where a prospective advertiser is assessed for fit against the surfaces available.

The two facts are worth keeping apart because they fail differently. If the adapter were written tomorrow, the review would still stand between a dealership and a live connection, and it runs on somebody else's timeline. An approved application, equally, is worth nothing without an adapter to use it. What that means for a store today is simple: if you want reach now, the managed path handles it and does not touch this page. If you specifically want Rokt wired into the CRM, that is a request, and the last section explains exactly what a request does.

Stated as a design rather than a description, because none of it runs and none of it is scoped. The same four row shape appears on every page in this directory, so a platform we have built and one we have not can be read line for line.

Notice what is absent from the first row. Nothing about the person on the confirmation screen comes from you, and nothing about your customers goes toward them. The targeting value here belongs to the transaction context, which is the platform's asset rather than anything we would supply.

If this platform were built, it would not be a special case. Every network answers the same contract.

A single library inside LeadLocate defines what any advertising platform must be able to do: hand us an authorization URL, exchange the returned 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. That is why adding a platform is scoped work rather than an open ended project, and why turning one on does not disturb the ones already running.

Credentials are encrypted before storage using AES-256-GCM. 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 on purpose, because these tables are shared across dealerships and a timezone relative timestamp is one nobody can reconcile afterwards. Campaign objects record which credentials created them and re-resolve those same credentials later, so a credential withdrawn later does not strand the work built under it.

Twenty networks are registered against that contract and one of them is implemented. Rokt is not among the twenty at all, which is what available on request means here rather than a softer way of saying soon. Every entry in this directory carries a status with a stated test beside it, including the entries that say no.

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 application to file, and no dependency at all 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 Rokt it does not exist. Any relationship your store or your agency holds with them stays where it is and operates independently of LeadLocate.

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, not from your dashboard. That is a deliberate constraint while the connection layer is young, and opening it up is queued work rather than a promise.

Three things in order, and only one of them is engineering.

First the vendor application, which is reviewed on their timeline and is where fit against available surfaces gets decided. Second the adapter: the seven operations written against their endpoints, a credential block added to the gateway configuration, and a verification call that proves a connection rather than assuming one. Third the part most stores underestimate, which is the destination. Because the response is a clickout, the page a person lands on after accepting an offer does all of the converting, and building that page well is a bigger determinant of results than anything in the media buy.

On measurement, acceptance data would read quickly. Transaction volume on the publisher side is continuous, so impressions and responses accumulate within hours rather than days. What those responses are worth is a much slower question. Somebody who accepted an offer in the middle of moving house is not filling in a credit application that evening, and judging this channel on same week appointments will make it look worthless while it is quietly working. Decide the window before the first dollar, not after the first report. None of this is a promise about volume or about what any of it closes at, and nobody can promise those.

The gaps below are true whether or not an adapter is ever written, and two of them shape what this platform could ever be for a dealership.

We do not emit a vehicle catalog or an inventory feed to any advertising platform. Any creative rendering specific units with price and mileage needs a product feed and no code in our stack generates one. Inventory Link ingests your feed and merchandises your units on your own properties, which is a different job entirely. On this surface the practical effect is that an offer would be a store level offer rather than a vehicle level one.

We do not install or manage pixels. Measuring what a confirmation screen response did on your website depends on a tag living there, and placing it, maintaining it and keeping consent handling correct are not services we provide.

We do not run a server side conversions API and we do not upload offline conversions. On a channel where the payoff is months out, feeding a signed deal back as a conversion is exactly what would prove it, and that is precisely what we have no code to do.

We do not export a hashed audience. Nothing built from your customer records leaves the CRM, here or anywhere else in this directory.

There are no native lead forms to retrieve. The response is a clickout, so nothing arrives by webhook and the real time lead path built for one network does not extend here.

No campaign has ever been deployed to Rokt from LeadLocate, because no code exists that could deploy one.

Say so, and say it with your store attached. Requests are recorded against the platform they name, and the tally is the input to build order, because a dealership ready to spend on a channel is a better signal than any internal roadmap meeting.

A request here is stronger when it names the moment you are chasing. A store in a market with heavy inbound relocation is describing a genuine fit, and that is an argument we can carry into a vendor conversation. A store that simply wants more leads is describing something this surface is a poor instrument for, and hearing that now costs you nothing.

If the honest answer turns out to be that the one network already connected reaches the same households more cheaply, you will hear that as well, because selling a build you do not need is a bad trade for both of us. Meanwhile the managed path is live and waits on none of this, and pricing sits on the pricing page without changing based on which networks you turn on.

Does LeadLocate integrate with Rokt today?

No. The published test for available on request is that no adapter file exists in the ad gateway for the platform, and that is the case here. Nothing in the CRM has ever called their systems and no campaign has ever been deployed to them from our side.

Can I use my own Rokt ad account?

Not through the CRM. Bringing your own advertising account is the half of the product this directory documents platform by platform, and for Rokt that half is empty. Whatever relationship you hold with them runs entirely outside LeadLocate.

What happens if I request Rokt?

It is recorded against Rokt specifically, not against retargeting in general, and counted. That tally is the input to build order, and you will hear back from a person with a range or a reason rather than silence.

Is a confirmation screen a sensible place to advertise a vehicle?

It depends entirely on which confirmation. Relocation and insurance moments carry real predictive weight for a vehicle purchase. Most other transactions do not, and the format rewards small instantly acceptable offers, which a dealership does not have.

Can I choose which sites my offer appears in?

That is a question for the vendor rather than for us, and it is the right question to ask before signing. Appearing inside somebody else's checkout is a brand context decision, and if it matters to your franchise you should get the answer in writing.

Why does the PARTNER label matter if the adapter does not exist anyway?

Because the two gates fail independently. The vendor reviews an application before issuing credentials, which is their timeline. The missing adapter is ours. Clearing either one alone still leaves a store without a connection.

Requests are counted against the platform they name. Tell us which life event your market actually produces and what you would offer, and you will get a range or a reason from a person.