Run Unity Ads from Your Dealership CRM

Rewarded and interstitial video inside mobile games, and an honest account of what a rooftop would get from it.

Unity is the engine a very large share of mobile games are built with, and its advertising business sells the placements inside those games. Three formats carry almost all of it. A rewarded video, which the player chooses to watch in exchange for a life, a hint or a currency. An interstitial, which appears at a break between levels. And a banner, which sits at the edge of play.

The rewarded format is the interesting one and it is genuinely different from everything else in this catalogue. The player opts in. They are told a video is coming, they agree, and they watch it to the end because leaving early forfeits the reward. Completion rates in that format are unlike anything a store sees on social or on a website.

The audience is enormous and it is not a niche demographic any more. Mobile gaming spans essentially every adult age band, and the sessions happen during idle time: a waiting room, a lunch break, a sofa in the evening. For a dealership the plain reading is that this is cheap, high completion video reach, at a price per thousand impressions well under what social charges.

The case is cost and completion. If a store wants a thirty second message watched all the way through by a lot of people inside its trade area, this is one of the cheapest ways to buy that outcome, and the inventory is not crowded with other dealerships. Local awareness at a low cost per completed view is a legitimate thing to want, particularly for a new point opening or a brand a market does not know yet.

The honest objection is what a completed view is worth when the viewer paid it as a toll. Somebody watching a car advertisement to get back to a puzzle is not leaning in. They are waiting for a button to appear in the corner. The completion rate is real and the attention behind it is thin, which means the metric that makes this channel look excellent is also the metric most likely to mislead a store into thinking it worked.

The second objection is the handoff. Taking someone out of a game, into a browser, onto a dealership website, and through a form is a long walk for a person who was mid level. Click through rates on this inventory reflect that, and a campaign judged on leads rather than reach will usually disappoint. The format was designed to sell other games, where the destination is one tap away in the same phone.

The third is that a twenty mile radius takes a channel whose entire advantage is scale and removes most of the scale. It is still buyable, but the economics at local geography look nothing like the national figures a proposal will quote. If reach at low cost is the actual goal, compare it honestly against connected television for dealers, where the viewer is at least sitting still and watching on purpose.

Not started, and the test attached to that status is checkable rather than rhetorical: no adapter file exists in the ad gateway for this platform. No authorization URL, no credential block, no wire-up checklist, and no partially written implementation sitting behind a badge.

Access class is PUBLIC, and this page is a good place to explain why the two axes are kept separate. Public means the vendor documents its advertiser interfaces and software development kits openly, so nobody has to be approved before building against them. It does not mean anything is built. Every remaining obstacle on this platform is on our side of the line, which is unusual in this catalogue and worth knowing if you are deciding what to ask for.

That also makes this one of the cheaper entries to move. There is no application to file, no licensing negotiation and no partner review to wait on. What there is, is an adapter file that nobody has written yet, and a queue with eighty other platforms in it. Demand decides the order, which is the whole design of the request status rather than an excuse attached to it.

Set out as a design for something that does not run, so no sentence here is mistaken for current behaviour.

Note what is absent from the return column. There is no form inside a rewarded video, so an opt in only ever happens afterwards on a page you control, using the forms that already live in the CRM. Everything this channel gives back is reach and attention, not names.

A platform nobody has built can be described this exactly, because the structure it would join is already running and already carries a live network.

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 is that file written against those seven, which is why a request asks for a bounded piece of work with a shape rather than for an exploration.

Because access here is public, the checklist for this one would be shorter than most. Register for developer access, fill a credential block, implement the token exchange, implement account listing, implement campaign creation, implement status changes, implement reporting, implement verification. Nothing in that sequence waits on another company's approval, which is not true of the majority of entries in this directory.

Credentials are encrypted with AES-256-GCM before storage. Every action against any network is written to an append only audit log carrying the company, the network, the user and the detail, stamped in UTC because the table is shared across dealerships and a company local timestamp cannot be reconciled later. Campaign objects record which credentials created them and re-resolve those credentials afterwards, so disconnecting an account never strands the work built underneath it.

Two ways to advertise through LeadLocate, and the store decides which.

The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, arriving as one line rather than a stack of platform invoices. Nothing to apply for and no credential for you to hold.

The second is your own account. Connect the advertiser account your store already holds and campaigns route through it, on your billing, in your name, with your history intact. For this platform neither path exists yet, because the adapter has not been written, and that is the only reason.

One limit that holds across the whole gateway, stated here rather than left to be discovered: deploying, activating, pausing and reading spend is done by our team rather than from a control on your dashboard. That is a deliberate constraint while the connection layer is young, and it is on the list to open up.

Three steps rather than the usual four, which is what a public access class buys you. A request from a store that would fund the channel. A queue position earned against the rest of the catalogue. And an adapter file written against the seven operations with a credential block and a verification path. There is no vendor review sitting in front of any of it.

The prerequisite that is not on that list is the creative. This inventory is video, held vertically, watched by somebody who agreed to watch it in exchange for something. A recut television spot is the wrong shape and usually the wrong tone, and a still image cannot run at all. Video production is not something we supply, so a store without an asset is asking for a channel it cannot use yet.

Measurement is fast on the things this channel is good at. Impressions, video starts and completion rates are readable within a day or two of a flight opening, because the volume is very large. What will not arrive quickly is a defensible line from a completed view to a signed deal, since the viewer left the game, forgot, and came back on their own terms later. Judge it on reach delivered against cost, and keep your lead targets on channels built to capture an opt in.

Nothing is connected here, so the gaps are listed rather than skipped over.

We have never made a call to this platform. No adapter file, no credential, no verification, no deployment, and nothing partially written.

We do not ship a software development kit and we do not build mobile applications, so nothing of ours sits inside any game, any store's application, or any phone.

We do not post conversion events anywhere. No server side conversions API, no offline conversion upload, and no pixel installation or management, which means a campaign here would be bought and judged on delivery rather than optimised against outcomes.

We do not emit a vehicle catalog or an inventory feed to this or any advertising platform. Vehicle level dynamic units are not on the table even with the connection built.

We do not export a hashed customer list for audience matching, lookalike building or suppression.

We will not describe rewarded video as a lead source. There is no form in the unit, the viewer is mid game, and a store told otherwise will spend a quarter finding out. That is precisely the kind of claim this directory exists to avoid making.

Ask by name and attach the rooftop. Requests are recorded against the platform they name and the tally decides build order, because a dealer ready to spend on a channel is a stronger signal than any internal ranking meeting.

This one has an unusual argument in its favour, and it is worth making if you intend to ask. There is no vendor gate here at all, so a request only has to beat the other entries in the queue rather than wait on somebody else's approvals process. Say what you would run and at what weight, and say whether the video already exists, because the creative is the real prerequisite and not the code.

Meanwhile the managed path runs today and waits on none of this. Platform pricing sits on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with Unity Ads today?

No. The status is not started, and its test is that no adapter file exists in the ad gateway for this platform. Nothing is partially written. The unusual part here is that the vendor gate is open, so the only obstacle left is our own queue.

Can I use my own Unity Ads account?

Not through the CRM, and the reason is entirely on our side for once. The vendor documents advertiser access openly, so no approval is needed from anybody. The adapter that would route your account through the gateway has not been written.

What happens if I request Unity Ads?

It is recorded against this platform by name and counted, and that count feeds build order across the catalogue. A person answers with a range or a reason. Because there is no vendor review to wait on, a request here converts into a build date more directly than most.

Does public access mean it is nearly connected?

No, and the two axes are separate for exactly this reason. Public describes the vendor's gate, meaning anyone may register for developer access without approval. Status describes our code, and here there is none. An open door is not a finished room.

Will people in a game actually click through to my website?

Rarely, and you should plan on that. The format was built to send players to other games, where the destination is one tap away on the same phone. Leaving a game for a browser and a form is a long walk, and the click rates show it.

Is rewarded video good value for a dealership?

As cheap completed reach, often yes. As a lead channel, no. The player agreed to watch in exchange for a reward, so the completion rate measures the bargain rather than the interest. Buy it for awareness with a clear head about which number means what.

Requests are recorded against the platform they name and the tally sets build order. Send your rooftop, the weight you would run, and whether the video already exists.