Adomni Integration for Dealerships

Digital billboards, forecourt screens and rideshare toppers bought without a rate card, and where that sits with the CRM.

Outdoor advertising used to be sold by a rep with a territory and a printed rate card, in flights measured in four week blocks. Adomni is one of the platforms built to remove that conversation. It is a self serve buying layer sitting on top of a very large pool of screens: roadside digital billboards, screens at fuel pumps and inside convenience stores, screens in gyms and bars, and toppers riding on the roofs of rideshare cars.

For a dealership the useful part is the minimum. A store can pick a radius around the lot, load a still image or a short animation, put a modest figure behind it and be on screens within a few miles of the showroom in a matter of days rather than after a quarterly commitment. That changes outdoor from a franchise group decision into something a single rooftop can test.

The rideshare piece is the one people ask about, because a topper is a screen that moves. It carries your message through the neighbourhoods the driver happens to work, which is a different shape of coverage from a fixed board on a commuter route, and it is worth understanding as a distinct product rather than as billboards with wheels.

The case is presence in a trade area. Car buying is a local decision made by people who drive past the same intersections every day, and a screen on the route to work builds the kind of familiarity that makes a store feel like an obvious place to look. Nothing in digital advertising replaces being visibly present in the ten mile circle where your buyers already live, and outdoor is the cheapest way to occupy that space at scale.

The honest objection is that a screen cannot be answered. There is no click, no form and no opt in, so a dealership buying outdoor is buying awareness and hoping it converts through a channel it can actually count. If your store is judged on cost per lead this month, outdoor will lose that comparison every time, because it does not produce a lead at all.

The second objection is specific to how these impressions are counted. A digital screen reports plays, not people. The audience figure attached to a play is a model built from traffic counts and mobile movement data, not a headcount, and two vendors can model the same screen differently. That is not fraud, it is how the category works, and a dealership should read outdoor delivery numbers as an estimate of opportunity rather than as a measurement of attention. If you want a channel that puts a name in your inbox, social lead ads do that and outdoor does not.

Available on request. The published test for that status is that the work is not started and demand decides the order, and nothing here stretches it. There is no adapter file for this platform in the ad gateway, no credential block, no authorization URL and no wire up checklist waiting behind a feature flag.

The access class is PARTNER, which is the vendor's gate rather than ours. Credentials require an application the vendor reviews before issuing them. That distinction matters on a platform like this one, because the advertiser side is deliberately open to anyone with a card while the developer side is not. Being easy to buy from and being easy to build against are different doors, and only the second one is what this page is about.

So a build here has two dependencies and we control one. We would schedule the engineering, which the request tally drives. The vendor would approve a credential on its own timeline. Any page that offered you a date would be inventing the second half of that sentence, and the directory exists so that nobody has to guess which half is which.

Written as a design rather than a description, because none of it runs.

Read the second row for what is missing rather than what is there. No opt in comes back from a screen buy, because a screen does not collect one. What a connection would add is spend and delivery landing beside your other channels inside the CRM, so a comparison across everything you buy is one screen instead of four logins.

The reason a page about an unbuilt platform can be this specific is that networks are not added here as bespoke projects. One provider agnostic library inside the CRM defines what any advertising platform must be able to do: hand us an authorization URL, exchange the code for a token, list the accounts a credential can reach, 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, answered identically by every one of them. Twenty networks are registered against that contract today and exactly one is implemented. The nineteen that are not return a refusal naming themselves, so a stray call fails readably rather than looking like an outage at the vendor. Adomni is not among the twenty at all, which is a smaller and more honest claim than registered.

Underneath the adapters sits infrastructure that already exists and would not be rebuilt for a new network. Credentials are encrypted before storage using AES-256-GCM. Every action against a network is written to an append only audit log carrying the company, the network, the user and the detail, stamped in UTC deliberately, because those 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 credentials later, so disconnecting an account does not orphan the work built under it.

Two routes, and the dealership picks. The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, and delivered as a single line rather than a stack of platform invoices. It is live today and nothing on this page gates it.

The second is your own account. Where a network is built, you connect the account your store already holds, campaigns route through it, and the billing, the naming and the spend history stay yours. Disconnect whenever you like and delivery falls back to the managed route.

Neither route reaches Adomni today. It is worth saying that a dealership does not need us in order to buy outdoor here, because the product was designed to be bought without an intermediary. What an integration would add is not access, it is the spend sitting in the same ledger as everything else, and the outdoor flight appearing on the same calendar as the campaigns that do produce a name.

The limit that applies across the whole gateway, repeated on every page in this directory: pushing, pausing and reading numbers from a network is done by our team, not from your dashboard. That is a deliberate constraint while the connection layer is young, and it is on the list to open up.

Two tracks, and only one of them is on our calendar. The vendor track is an application and a review before any credential exists. Our track is an adapter file written against the seven operation contract, a credential block, then each operation implemented and verified against a live account. Ours is predictable work with a known shape. Theirs is somebody else's queue.

On measurement, carry the caveat that governs every screen based channel. Outdoor results are not reliably attributable inside a day. Delivery reads immediately, because plays are counted as they happen, but the effect on your showroom does not separate itself from everything else you are running that week. The correct way to judge a screen buy is to fix the question in advance: how many screens inside the trade area, how many plays a day, at what cost per thousand estimated impressions, and did direct traffic and inbound calls move over the following month.

That is a statement about how a channel produces information, not a forecast of lead volume or closing rate. Nobody can forecast those for outdoor, and a vendor who offers to is telling you something about themselves rather than about screens. The same discipline is set out in what to expect from car sales leads.

The gaps below are the ones that apply on this platform specifically.

We do not retrieve leads from this platform. Lead form retrieval in our stack is implemented for exactly one network and this is not it. A screen does not collect an opt in in any case, so a campaign here would report into the CRM as a reach buy and would not feed your lead intake.

We do not emit a vehicle catalog. Some screen networks accept a feed so that creative can rotate individual units or prices. No code anywhere in our stack generates a catalog for any advertising platform, so creative here would be your store and your offer rather than your stock.

We do not install or manage a pixel, and we do not run a server side conversions endpoint or an offline conversion upload. Those are the mechanisms an outdoor vendor would use to argue that a screen produced a visit, and we operate none of them.

We do not upload hashed audiences. No customer list from your store becomes a targeting segment anywhere, on this platform or any other.

No campaign has ever been deployed to Adomni from the CRM, because there is no code that could do it. Anyone describing this as an existing integration is describing a wish.

Ask, with your store attached, and say which screen types you actually want. Roadside boards, forecourt screens and rideshare toppers behave differently enough that the answer changes with the format, and a request that names one is more useful than a request that names the vendor.

Requests are recorded against the platform they name and the tally is the input to build order, because a store ready to spend on a channel is a better signal than any roadmap meeting. You will hear back from a person with a range or a reason rather than silence.

In the meantime the managed route runs today and does not wait on any of this. If what you want is coverage across a trade area rather than one vendor's console, read car dealership advertising first. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with Adomni today?

No. The status is available on request, whose published test is that the work is not started and demand decides the order. There is no adapter file, credential block or wire up checklist for this platform anywhere in the ad gateway.

Can I use my own Adomni account?

Not through the CRM, because nothing exists to reach it. You can open an account directly with the vendor, since the product is built to be bought without an intermediary. An integration would add the spend landing beside your other channels, not the ability to advertise.

What happens if I request Adomni?

It is recorded against this platform specifically and counted, and that tally is the input to build order. A person replies with a range or a reason. On this one the reply will ask which screen formats you want before anything else.

Would a billboard campaign produce leads in my CRM?

No. A screen collects nothing, so there is no opt in to deliver. A connection here would carry plays, estimated impressions and spend into the CRM for comparison against your other channels, which is a smaller and more accurate claim than most outdoor vendors make.

Why is the audience number on a screen an estimate?

Because a digital screen reports plays rather than people. The audience attached to each play is modelled from traffic counts and mobile movement data, and different vendors model the same screen differently. Read it as opportunity, not as attention.

Are rideshare toppers worth buying for a dealership?

They are a different product from a fixed board. A topper travels wherever the driver works, so coverage is broad and unpredictable rather than concentrated on one route. That suits general awareness across a metro and suits a message tied to one intersection much less well.

Requests are counted against the platform they name and the tally decides build order. Send your store, your radius and which formats matter, and expect a real answer.