AdsWizz Integration for Dealerships

Dynamic ad insertion and programmatic audio supply, and why the right way to read this entry is as engineering rather than media.

Most entries in this directory are places to buy advertising. This one is not. AdsWizz is the technology a large share of digital audio runs on: the ad server that decides which spot plays, the dynamic insertion that drops a fresh ad into a podcast episode downloaded a year after it was published, and the marketplace where audio inventory is traded programmatically.

If a dealership has ever heard a streaming spot, there is a reasonable chance the machinery underneath it came from here, without the store, the station or the listener ever seeing the name. It is infrastructure sold to publishers, broadcasters and platforms rather than to advertisers, and the self serve tools an ordinary small business uses to buy audio frequently sit on top of it.

The reason it appears in this directory at all is that a company deciding to build audio buying properly has to decide whether to integrate at the buying tool level or at the infrastructure level. Those produce very different products, and only one of them is still useful in five years.

The candid answer is that a dealership does not spend money here, and would not. No store opens an account with an audio ad server. You are not the customer of this business and you never will be, and a directory that implied otherwise would be padding a list with a logo.

The genuine interest is second order. A platform that integrates at this level can build audio buying rather than resell somebody else's console, which means the geography, the frequency capping, the creative rotation and the reporting are ours to shape rather than whatever a self serve interface happens to expose. For a dealership the practical difference shows up in things like whether a schedule can be capped so the same listener hears the spot three times a week instead of once a day, and whether audio delivery lands in the same report as everything else you buy.

The honest objection, then, is timing. This is the most useful integration on the audio list and the least immediately usable one. It delivers nothing a store can run next week, it is an enterprise conversation rather than a signup, and any dealership whose real question is how do I get on the radio this month should be reading the self serve options in this family instead. Building here is the right long answer to the wrong short question.

Available on request. The published test is that the work is not started and demand decides the order, and that is precisely the state. No adapter file exists in the ad gateway for this platform, no credential block, no authorization URL and no checklist waiting to be scheduled.

Access class is PARTNER, the vendor's gate rather than ours, and on an infrastructure company that gate is heavier than the word suggests. Credentials require an application the vendor reviews, and the review is not a formality when the applicant is asking to plug into supply the vendor is contractually responsible for. Expect a commercial conversation, not a developer portal signup.

The other honest note is scope. An integration here would not be one adapter answering seven operations against a tidy campaign API. It would touch supply access, creative handling and reporting shapes that differ from the display and social networks the gateway was first built around. That is why this entry sits at available on request rather than being quietly promoted: calling it started would misrepresent both the size of the work and the state of it.

A design rather than a description, and a rougher one than most on this directory because the shape of the work is less settled.

The frequency cap row is the one that justifies the whole exercise. Reaching audio supply at this level is what makes it possible to control how often a listener hears the same spot, which is the single variable that decides whether a modest audio budget does anything at all.

Every network in this directory answers the same contract, which is why an unbuilt entry can still be described precisely. One provider agnostic library inside the CRM sets out what an 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. Twenty networks are registered against that contract and one is implemented. The nineteen that are not answer every call with a refusal naming themselves, so a stray call fails loudly rather than looking like an outage somewhere else. This platform is not among the twenty.

The shared machinery underneath already exists and would not be rebuilt. 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 disconnecting an account never strands the work built under it. That contract is also the reason integrating at the infrastructure level is attractive: an adapter written once against audio supply serves every dealership on the platform, rather than each store separately learning a console.

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, invoiced as one line rather than a pile of platform bills. Live today, and unaffected by anything on this page.

The second is your own account, where a network is built. Campaigns route through the advertising account your store already holds, on your billing and in your name, and disconnecting returns delivery to the managed path.

This platform is the one entry in the family where the second route makes little sense even in principle, because a dealership does not hold an account with an audio ad server. If this were built, it would almost certainly serve the managed side of the house rather than a store connecting its own credentials. Saying so is more useful than pretending the two routes apply evenly everywhere, and it is why the directory keeps a status and an access class on separate axes.

The gateway wide limit still applies and is 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, and this is the entry where they are least symmetrical. The vendor track is a commercial application and a review before credentials exist. Our track is larger than a standard adapter, because supply access, creative handling and reporting do not map one for one onto the shapes the gateway learned from social and display networks. That is work we can scope honestly and would not pretend is a week.

On measurement, audio remains a reach and frequency channel however it is bought. Deciding in advance what the flight is meant to achieve is the entire discipline: how much of the trade area hears the spot, how many times, over how many weeks, and whether the countable channels move across that window. Buying at the infrastructure level improves control over frequency. It does not turn audio into a channel that reports leads by lunchtime, and nothing will.

Do not expect same day lead counts from an audio schedule regardless of who sold it. Delivery is readable quickly. Effect is not, and a store that judges an audio flight on the following morning is measuring noise.

The specific gaps here, several of which are structural rather than temporary.

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

We do not operate an ad server or dynamic insertion of our own, and we would not describe an integration with one as making us an audio platform. The technology would remain the vendor's.

We do not install or manage a pixel, we run no server side conversions endpoint, and we do not upload offline conversions. Those are the three ways audio attribution is usually argued, and we operate none of them.

We do not emit a vehicle catalog. No unit level feed leaves our stack for any advertising platform, and dynamic insertion of a specific stock number into an audio spot is not something we do.

We do not upload hashed audiences. No customer list becomes a targeting segment anywhere.

No campaign has ever been deployed to this platform from the CRM, because no code exists that could deploy one. Anyone describing audio infrastructure access as an existing LeadLocate capability is describing an idea.

Request it, and be aware you are voting for engineering rather than for a schedule you can run in a fortnight. Requests are recorded against the platform they name and the tally decides build order, so a vote here pushes audio infrastructure up the list rather than putting a spot on air next month.

If what you actually want is audio running soon, say that instead and name a budget, and the answer will point at a self serve route or at the managed path rather than at this. Being told which door to use is worth more than being added to a queue for the wrong one.

A person replies either way, with a range or a reason. Pricing for the platform is on the pricing page and does not change based on which networks you turn on, and the streaming audio page covers how the medium behaves before any vendor enters the picture.

Does LeadLocate integrate with AdsWizz today?

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

Can I use my own AdsWizz account?

Almost certainly not, because dealerships do not hold accounts with audio ad servers. This is infrastructure sold to publishers and platforms. If it were built here it would serve the managed side rather than a store connecting its own credentials.

What happens if I request AdsWizz?

It is recorded against this platform specifically and counted, and the tally feeds build order. Expect a reply that asks what you are really trying to achieve, since a store wanting audio on air soon is better served by a different door.

Why would a CRM integrate with audio infrastructure at all?

Because building at that level means controlling geography, frequency capping, creative rotation and reporting, instead of inheriting whatever a self serve console exposes. Frequency control in particular is what decides whether a modest audio budget does anything.

Would this get my inventory read out in an audio spot?

No. Dynamic insertion of a specific vehicle would require a unit level feed leaving our stack for an advertising platform, and no such feed exists. Audio creative here is about the store rather than about a stock number.

How quickly would an audio flight show results?

Delivery reads within a day or two. Effect does not. Audio is a reach and frequency medium, so the honest approach is to fix a frequency target in advance and read the countable channels across the whole flight rather than the morning after.

Requests are counted against the platform they name and the tally decides build order. Say whether you want audio infrastructure or audio on air this month, because those are different answers.