Audiohook Integration for Dealerships

Audio bought like performance media, with the measurement claim examined rather than repeated.

Audiohook is a demand side platform for audio. Rather than selling a station or a show, it buys across streaming music, radio streams and podcasts programmatically, and it is built around the thing audio has historically been worst at: proving something happened afterwards. Targeting, delivery reporting and conversion measurement sit in the same tool.

The pitch to an advertiser is that audio can be run the way search and social are run. Set a geography, a budget and a target, launch, then read a report that connects exposure to a site visit or a form submission rather than to an estimated audience. For a category that spent decades saying trust us, that is a genuine shift in posture.

For a dealership the appeal is obvious. Audio reaches people in the car, which is the one place a vehicle is already on somebody's mind, and a store that has avoided the medium because it could never justify the spend to an owner now has a report to point at. Whether that report says what it appears to say is the subject of the next section.

The case is discipline. Buying audio through a performance oriented platform forces a store to define a geography, a frequency and an outcome before spending, which is more rigour than most radio schedules ever receive. Counted impressions replace panel estimates, delivery is visible by day, and the budget can stop on a Tuesday if it is not working. None of that is available when audio is bought as a quarterly schedule from a rate card.

The honest objection is that an attributed audio conversion is a model, not an observation. Nobody clicks an audio ad. Attribution in this category works by comparing people who were probably exposed against people who probably were not, usually through device level location or identity signals, and then crediting the difference. The comparison group is chosen by the platform, the exposure is inferred, and the resulting lift figure is produced by the party selling the media. That is not fraud, it is methodology, and it should be read the way you would read a supplier's own quality report.

The second objection is incrementality. Audio supply overlaps heavily with the audiences you are already reaching through display and social, so a lift attributed to a spot may be a shopper who was already surrounded by your advertising. Ask what the control group was, how exposure was determined, and whether the measurement window is longer than the buying cycle it is meant to explain.

Available on request. The published test for that status is that the work is not started and demand decides the order, and this entry sits squarely there. No adapter file exists in the ad gateway for this platform, no credential block, no authorization URL, no wire up checklist.

Access class is PARTNER, the vendor's gate rather than ours. Credentials require an application the vendor reviews before issuing them, which on a demand side platform usually means a commercial agreement rather than a developer signup, since supply access and measurement data are things a vendor is contractually careful with.

Worth being precise about one thing, because it is where a page like this would normally overreach. Even with a built adapter, the measurement story on this platform would remain the vendor's. We would carry campaigns and read spend and delivery. We would not be the party computing lift, and we would not stand behind a lift figure produced elsewhere. A CRM that quietly relabels a supplier's model as its own reporting has made the number harder to question, not easier.

A design rather than a description, because none of it exists.

Notice what the second row leaves out. Attribution and lift are not in it. Those are computed by the platform from signals we neither collect nor control, and importing a number we cannot reproduce would give it a credibility it has not earned. Spend and delivery are facts. Lift is an argument, and arguments belong beside their author.

Adding a network here is a shaped task rather than an open ended project, which is what allows a page about unbuilt work to be specific. 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 the same way by every network. Twenty are registered against that contract and one is implemented. The other nineteen return a refusal that names themselves, so a stray call fails loudly and readably rather than looking like an outage at the vendor. This platform is not among the twenty, which is a smaller and more accurate claim than registered.

The shared infrastructure below 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 deliberately, because these tables are shared across dealerships and a local time stamp cannot be reconciled later. Campaign objects record which credentials created them and re resolve those credentials afterwards, so a disconnected account never strands the work built beneath it.

Two routes, and the dealership decides. 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. It is live today and nothing here gates it.

The second is your own account. Where a network is built, campaigns route through the advertising account your store already holds, on your billing, in your name, with your spend history intact. Disconnect and delivery returns to the managed path.

Neither route reaches this platform today. If it were built, the self connect route would be the more interesting of the two here, because a store that already has a relationship with an audio demand side platform usually wants the reporting alongside its other channels rather than a second intermediary between it and the vendor. That is the honest value of an integration on a platform a dealership can already buy from: consolidation of the view, not access to the media.

The gateway wide limit, stated 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 it is on the list to open up.

Two tracks. The vendor track is an application and a commercial review before credentials exist. Our track is an adapter file against the seven operation contract, a credential block, and each operation wired and verified against a live account. Ours is predictable work. Theirs is a queue we do not control and will not put a date on.

On measurement, the discipline here is unusual for audio and should still be applied carefully. Delivery reads in a day or two. Any lift or conversion figure needs a window long enough to cover how people actually shop for a vehicle, which is weeks rather than days, and it needs the control group described before the flight rather than after the result. A store that agrees the method in advance can trust the answer more than a store handed a number at the end.

Do not expect same day lead counts from an audio schedule, whoever sells it and however performance oriented the interface looks. Audio remains a reach and frequency channel that happens to be measured better here than elsewhere, and better measurement of a slow channel does not make it a fast one.

The gaps that apply specifically to this platform, and the first two matter more here than anywhere else in the audio family.

We do not install or manage a pixel. Audio attribution on this kind of platform depends on a tag on your website, and placing, maintaining and verifying that tag is between you and the vendor. If nobody checks it, the measurement quietly stops meaning anything and the report still renders.

We do not compute or import attribution and lift. Those numbers belong to the platform that produced them. We would carry spend and delivery, which are facts, and we would not relabel a supplier's model as our reporting.

We do not retrieve leads from this platform. Lead form retrieval exists for one network and this is not it, and an audio spot collects no opt in in any case.

We run no server side conversions endpoint and no offline conversion upload. A dealership that wants closed sales matched back to audio exposure is asking for something we do not do.

We do not emit a vehicle catalog, so creative is audio about the store rather than a specific unit, and we do not upload hashed audiences, so no customer list becomes a targeting segment.

No campaign has ever been deployed to this platform from the CRM, because nothing exists that could deploy one.

Ask, and say whether you are already running with them, because a store with an existing account is asking for consolidation while a store starting fresh is asking for a media decision. Those get different answers and both are legitimate. Requests are recorded against the platform they name and the tally decides build order.

Expect a question back about measurement method rather than budget. On this platform the number that will be waved at you in three months is the one worth agreeing the rules for today, and a vendor that answers that question crisply is telling you something good about itself.

The managed path runs today and waits on none of this. Pricing for the platform is on the pricing page and does not change based on which networks you turn on. For the channel itself rather than the vendor, the streaming audio page is the better read.

Does LeadLocate integrate with Audiohook 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 exists for this platform in the ad gateway.

Can I use my own Audiohook account?

Not through the CRM, because nothing exists to reach it. You can hold an account with the vendor directly. What an integration would add is consolidation, meaning spend and delivery beside your other channels rather than in a separate login.

What happens if I request Audiohook?

It is recorded against this platform specifically and counted, and the tally feeds build order. Say whether you already run with them, because a consolidation request and a first time media request are different problems with different answers.

How much should I trust an audio lift number?

Read it as a model rather than an observation. Nobody clicks an audio ad, so lift is inferred by comparing probable exposure against a control group the platform selects. Agree the method and the window before the flight, not after the report.

Does audio attribution need something on my website?

Usually yes, a tag that records site activity for the comparison. We do not place or maintain that tag, so it stays between you and the vendor. An unchecked tag is the most common way a measurement report keeps rendering after it stopped being true.

Would you match audio exposure to sales I closed?

No. That would require an offline conversion upload or a server side conversions endpoint, and we operate neither. Anyone offering to close that loop for you should be asked exactly which file leaves your building and where it goes.

Requests are counted against the platform they name and the tally decides build order. Tell us whether you already run audio with them and what a pass would look like.