Run Digital Turbine from Your Dealership CRM

On device placements through carrier and manufacturer relationships, and a candid account of the gap for a rooftop.

Digital Turbine sits in an unusual place in the advertising chain. Rather than buying space inside somebody else's application or website, it holds relationships with mobile carriers and handset manufacturers, and it delivers placements through software that ships on the phone itself. Recommendation screens during device setup, application discovery surfaces the carrier controls, and notification placements are the characteristic inventory.

The company also operates an exchange and a mediation business acquired over the years, so a buyer can reach ordinary in application inventory through it as well. But the on device layer is the part nobody else has, and it is why the platform is discussed separately from every other mobile network in this catalogue.

What that means for a dealership is a moment no browser based channel can reach: a person holding a new phone, or opening a carrier surface, before any advertising cookie or application session exists. That is genuinely distinctive reach. Whether it is reach a store can use is a different question, and the next section answers it without softening the edges.

The case is uniqueness of moment and freshness of device. Placements that arrive through the carrier layer land in front of somebody who is not scrolling past an advertisement, and the surfaces have very little competition from other local advertisers. A market where every rooftop is bidding on the same search terms and the same social audiences has an obvious appeal in inventory nobody local is buying.

The first honest objection is that the platform's signature mechanic does not apply to a car store. The on device machinery exists to get applications installed with as little friction as possible, and a dealership has nothing to install. Strip that away and what is left is ordinary mobile advertising bought through an unusual door, at which point you are paying for distinctiveness you cannot use.

The second objection is how the inventory is sold and at what scale. Carrier and manufacturer arrangements are national, negotiated against national budgets, and the buyers are the sort of advertisers who can absorb a market wide flight. A single rooftop wanting a twenty mile radius is not the shape of demand this business was designed around, and a group may need to be quite large before the conversation is a comfortable one on both sides.

The third is tone, and it deserves a sentence rather than a footnote. Placements that arrive on a device the user did not ask to see advertising on carry an annoyance risk that a local business absorbs differently from a global brand. A national company can wear a small amount of irritation across a hundred million impressions. A dealership lives on a reputation inside one town. Weigh that honestly before buying, and compare it against the more conventional options in programmatic display for dealers.

Not started, and the published test for that status is a claim you can check rather than a word you have to trust: no adapter file exists in the ad gateway for this platform. No authorization URL, no credential block, no wire-up checklist, and nothing partially implemented behind a status badge.

The difference from a registered platform is worth restating because it changes what a request buys. A registered network already has an adapter and an ordered checklist, so the open question is scheduling. Here the adapter itself is the first piece of work, which makes the request tally the entire mechanism.

Access class is PARTNER, and that gate belongs to the vendor. Credentials require an application the vendor reviews, and a business whose inventory depends on contracts with carriers and device manufacturers reviews advertiser access with those contracts in mind. Expect that review to weigh the size and the shape of the buyer, not just the paperwork. It sits in front of the engineering whatever our queue looks like, and saying so is more useful to a dealer than a vague promise of availability.

A design for a connection that does not exist, written as a design so nothing reads as a description of live behaviour.

The install row is the one specific to this platform. The measurement that makes the on device layer valuable to its usual buyers is an application install attributed on the handset, and that is a measurement a dealership has no version of. Anything a store did here would be judged on delivery and on traffic arriving at a page you control.

Something unbuilt can be described this precisely because the frame it would drop into already exists 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 means writing that one file against those seven, which is why a request here asks for a scoped job rather than for a discovery phase.

Credentials are encrypted with AES-256-GCM before they are stored. Every action taken against any network is written to an append only audit log carrying the company, the network, the user and the detail, timestamped in UTC deliberately, because the table is shared across dealerships and a company local timestamp cannot be reconciled afterwards. Campaign objects record which credentials created them and re-resolve those same credentials later, so disconnecting an account does not orphan the campaigns built beneath it.

None of that is rewritten per platform, which is why a catalogue this size is publishable at all, and why the honest answer on the entries nobody has built is a queue position rather than a shrug.

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

The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, and billed as a single line rather than a set of platform statements. No application to file and no credential for you to hold.

The second is your own account. Connect the advertiser account your group already holds and campaigns route through it, on your billing, in your name, with your negotiated terms intact. For this platform neither path exists today, because no adapter has been written and the vendor gate has not been approached.

One limit applies across the whole gateway and belongs on the page rather than in a later conversation: 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 rather than something already delivered.

Four steps, two of which are ours. A request from a store or a group that would fund the channel at a weight this inventory recognises. A queue position earned against every other request in the catalogue. An adapter written against the seven operations, with a credential block and a verification path. And a vendor reviewed application for advertiser access, on the vendor's timeline and subject to the vendor's commercial appetite.

That fourth step is the one to think hardest about here, because unlike most partner gates it is not only a compliance review. The vendor is deciding whether a buyer of your size is worth onboarding into inventory it negotiated with carriers. A single point may simply not be, and being told that early is better than being strung along.

On measurement, delivery numbers would arrive quickly and mean little on their own. The useful read for a dealership is traffic landing on your own pages and what happens to it there, which is measured in your own analytics and in the CRM rather than in the platform. Attribution from an on device impression to a signed deal weeks later is weak by nature and no vendor can honestly claim otherwise. Nobody can promise that link, and treating a delivery report as proof of sales is the mistake this channel invites.

Nothing is connected, so the gaps get named plainly.

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

We do not build mobile applications and we ship no software on any handset. The mechanic that defines this platform, getting an application onto a device with minimal friction, has no dealership equivalent in our product, and we will not describe it as though it does.

We do not post conversion events, install events or offline conversions anywhere. No server side conversions API and no pixel installation or management, which means a campaign here is judged on delivery rather than optimised toward an outcome.

We do not emit a vehicle catalog or an inventory feed to this or any advertising platform, so vehicle level dynamic units are not available even with a connection built.

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

We hold no carrier or manufacturer relationship of any kind. Nothing in our stack has a route to a device outside an ordinary browser or an ordinary advertising placement, and no amount of adapter work would change that.

Ask by name and attach the rooftop or the group. Requests are recorded against the platform they name and the tally decides build order, because a dealer with a budget ready to move outranks any internal ranking exercise.

Two details make a request here much stronger. Say how many rooftops and how many markets you operate, because the vendor gate on this platform weighs the size of the buyer and a group request is a materially different conversation from a single point. And say what you would actually run, since the distinctive on device inventory suits a brand message far better than a weekend price offer.

Until any of that happens the managed path runs today and depends on none of it. Platform pricing is on the pricing page and does not vary with which networks you enable.

Does LeadLocate integrate with Digital Turbine today?

No. The status is not started, and the test for it is that no adapter file exists in the ad gateway for this platform. There is no credential, no checklist and no partial code, and the request count is what decides whether that changes.

Can I use my own Digital Turbine ad account?

Not through the CRM. Nothing has been written on our side, and access is partner gated, so credentials come through an application the vendor reviews with its carrier agreements in mind. An existing relationship removes the vendor half of the answer and leaves the engineering half.

What happens if I request Digital Turbine?

It is recorded against this platform by name and counted, and the count feeds build order across the catalogue. A person replies with a range or a reason. Group requests carry more weight here than single rooftop requests, because the vendor gate weighs buyer size.

Does the on device advantage help a car dealership?

Less than the pitch suggests. The mechanic was built to install applications with almost no friction, and a store has nothing to install. Remove that and you are buying ordinary mobile advertising through an unusual door, which is a thinner proposition than it first sounds.

Is a single rooftop big enough to buy this?

Often not, and it is fairer to say so up front. The inventory comes from national carrier and manufacturer agreements sold against national budgets. A multi point group has a far better case, and a single store may find the vendor simply is not interested in onboarding it.

Are on device placements a reputational risk for a local business?

They can be. Advertising that arrives on a device the owner did not open for advertising carries an irritation cost, and a national brand absorbs that across a huge audience in a way a store inside one town cannot. Weigh it before you buy rather than afterwards.

Requests are recorded against the platform they name and the tally sets build order. Send your markets, your rooftop count, and the message you would actually run.