Blip Billboards Integration for Dealerships

Outdoor priced per play, with nothing to sign, and what a low entry price actually buys a single rooftop.

Most outdoor is sold in four week flights with a signature at the front and a media rep in the middle. Blip removes both. It is a self serve marketplace for digital billboards where the unit of purchase is the individual play, the campaign can be switched off in an afternoon, and there is no contract binding the advertiser to a second month.

Practically, a store picks boards on a map, decides how much to spend per play and how much to spend per day, uploads a still image and goes live. The auction decides how often the board shows your creative against everything else in the loop. Spend more per play and you appear more often on the boards you chose.

For a dealership that has never bought outdoor, this is the least frightening version of it that exists. There is no production of printed vinyl, no long lead time, and no obligation that outlasts a weekend sales event. That is a genuinely different commercial shape from the rest of the outdoor category, and it is the entire reason a single rooftop would look at it before looking at a traditional board vendor.

The case is the on ramp. A store can find out what a board on the main road into town does for showroom traffic without committing a quarter of its advertising budget to the experiment, and it can time the flight to the event rather than to a media calendar. A tent sale on the last weekend of the month can have boards behind it and stop when the tent comes down.

The honest objection is repetition, and it is the one this pricing model makes easiest to get wrong. Outdoor works by being seen by the same person on the same commute over and over until the store becomes familiar. Paying per play makes it very easy to buy a small number of plays spread thinly across a lot of boards, which produces a bill and almost no familiarity. Twenty appearances scattered across a metro teaches a market nothing. The same money concentrated on two boards on one commuter route at least has a chance to be remembered.

The second objection is the format itself. A driver gives a board perhaps a second of attention at speed. That rules out payments, disclaimers, three vehicles and a phone number, and it leaves room for a store name, one idea and a place. Dealership creative fails outdoor far more often than dealership targeting does. If you want a channel where a longer message and a response are both possible, programmatic display is a better place for that budget.

Available on request, which is the weakest of the three status words in this directory and the accurate one here. The published test is that the work is not started and demand decides the order. No adapter file exists for this platform in the ad gateway, there is no credential block for it, and there is no authorization URL or wire up checklist sitting behind a flag waiting to be switched on.

The access class is PARTNER. That is the vendor's gate rather than ours, and it means credentials require an application the vendor reviews before issuing them. There is a mild irony worth naming, because a dealer comparing options will notice it: this is one of the easiest platforms in the entire catalogue for an advertiser to buy from and it is not correspondingly open on the developer side. Those are two different doors and only the second is what a status word on this page describes.

A build therefore has two dependencies and we control one of them. The engineering is scheduled by the request tally. The credential is approved on somebody else's calendar. A promised date would be a guess about the half that is not ours.

Stated as a design, because none of this exists.

The row worth reading twice is the second one, for what is absent from it. A board returns delivery, not people. There is no opt in in that list because a billboard cannot collect one, and a connection here would make outdoor spend comparable inside the CRM rather than turn it into a lead source.

A page about an unbuilt platform can be specific because networks are not added here one bespoke project at a time. There is a single provider agnostic library inside the CRM that 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, and every network answers the same seven. Twenty are registered against that contract today and exactly one of them is implemented. The other nineteen return a refusal that names the network, so a stray call anywhere in the CRM fails loudly and readably instead of resembling an outage at the vendor. Blip is not among those twenty, which is a smaller claim than registered and the reason this page says request rather than roadmap.

The infrastructure below the adapters already exists and would not be rebuilt for a new network. Credentials are encrypted before storage with 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 on purpose because those tables are shared across dealerships and a timezone relative timestamp cannot be reconciled later. Campaign objects record which credentials created them and re resolve those credentials afterwards, so a disconnected account does not strand the work built under it.

Two routes, and the dealership chooses. 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 one line instead of a stack of platform invoices. That route is live today and nothing on this page holds it up.

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 remain yours. Disconnect and delivery returns to the managed route without you doing anything.

Neither route reaches Blip today. On this platform in particular it is worth saying plainly that a dealership can go and buy boards this afternoon without us, because the product exists to be bought that way. An integration would not grant access. It would put the outdoor flight on the same calendar and in the same spend comparison as the campaigns that do produce a name, which is a smaller benefit honestly described.

One limit applies across the whole gateway and is repeated on every page here: pushing, pausing and reading numbers from a network is done by our team rather than from your dashboard. It is a deliberate constraint while the connection layer is young, and opening it up is on the list.

Two tracks, one of them ours. The vendor track is an application and a review before any credential is issued. Our track is an adapter file written against the seven operation contract, a credential block added and enabled, then each operation implemented and verified against a live account. That work is predictable and shaped like work we have done before.

On measurement, hold the same caveat that governs every screen channel. Outdoor is not reliably attributable inside a day. Plays report immediately, which is not the same thing as knowing what they did. The way to judge a per play buy is to decide the question before the flight starts. How many boards, on which routes, how many plays each per day, at what cost per thousand estimated impressions, and did direct traffic, inbound calls and walk ins move over the following weeks.

Note what that framing does. It converts outdoor from a channel that fails a cost per lead comparison into one that can be judged on the terms it actually operates on. It is also a statement about how the channel produces information rather than a forecast of volume or closing rate, and nobody can forecast those for a billboard.

The gaps that matter on this platform, named individually.

We do not retrieve leads from this platform. Lead form retrieval exists in our stack for one network only, and this is not that network. A board collects nothing regardless, so a campaign here would report as a reach buy and would never feed lead intake.

We do not emit a vehicle catalog. Boards that rotate live price or unit level creative do so from a feed, and there is no code anywhere in our stack that generates a feed for any advertising platform. Creative here is your store and one offer, not your stock list.

We do not install or manage a pixel, we do not run a server side conversions endpoint, and we do not upload offline conversions. Those three are how an outdoor vendor would try to prove a board drove a visit, and we operate none of them.

We do not upload hashed audiences. Nothing from your customer list becomes a targeting segment on this platform or anywhere else.

No campaign has ever been deployed to Blip from the CRM. There is no code that could do it, and describing this as a working integration would be exactly the claim this directory exists to prevent.

Ask, with your store attached, and say which roads matter. On a per play platform the useful request names the two or three boards a buyer would actually want to own rather than the vendor in the abstract, because concentration is the whole argument for buying here at all.

Requests are recorded against the platform they name and the count decides build order, since a dealership ready to spend on a channel is a better signal than any internal roadmap discussion. Somebody replies with a range or a reason instead of silence.

The managed route runs today regardless. If the underlying goal is presence across the trade area rather than one particular console, car dealership advertising covers how the pieces fit together, and pricing for the platform sits on the pricing page without changing based on which networks you turn on.

Does LeadLocate integrate with Blip Billboards today?

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

Can I use my own Blip Billboards account?

Not through the CRM, because there is no code that reaches it. You can buy boards directly from the vendor today, since the platform was designed for exactly that. An integration would put the spend and delivery beside your other channels, not grant access you already have.

What happens if I request Blip Billboards?

It is recorded against this platform by name and counted, and the tally feeds build order. A person answers with a range or a reason. Expect a question back about which roads you want covered, because that decides whether the budget is spent well.

How many plays does a dealership actually need?

More than most first time buyers expect, and concentrated rather than spread. Outdoor works through repetition against the same commuters, so a small number of plays scattered across many boards produces a bill and very little recall. Two boards seen often beat twenty seen once.

Do billboard campaigns show up as leads?

No. A board has no form and no click, so there is nothing to collect. A connection here would carry plays, spend and share of loop into the CRM so outdoor can be compared with the channels that do produce names.

Is there a minimum spend?

The platform is built around not having a meaningful one, which is its main attraction. The practical floor is different from the contractual floor: it is whatever buys enough plays on enough of the right boards to be remembered, and that number is set by your market rather than by the vendor.

Requests are counted against the platform they name and the count decides build order. Send your store and the two boards you would buy first.