Acast Integration for Dealerships

Podcast advertising bought without an agency, and the geography problem a single rooftop hits first.

Acast is one of the larger independent podcast companies, sitting between shows and advertisers. It hosts and distributes podcasts, represents many of them for advertising, and sells access to that catalogue through both a self serve route for smaller budgets and a managed route for bigger ones. Independent matters here, because the catalogue is not one broadcaster's own programming.

Two ad formats do most of the work. A host read is the presenter talking about your store in their own voice, usually recorded into the episode and carried by whatever credibility the host has built. An inserted spot is produced audio dropped into an episode dynamically, which can be swapped, geographically targeted and turned off, and which sounds exactly like what it is.

For a dealership the interesting one is the host read, because trust transfers. A presenter saying they bought their truck from a named store on the edge of town does something no display impression does. It is also the format with the most friction, and the section below is honest about it.

The case is endorsement and attention. Podcast listening is deliberate rather than incidental, the audience is often in a car or on a commute, and a host read arrives as a recommendation rather than an advertisement. Local services in particular do unusually well from that, because the objection a shopper has about an unfamiliar dealership is trust, and borrowed trust is the one thing paid media rarely supplies.

The honest objection is geography. A dealership sells to people within a driving radius, and podcast audiences are national by default. Targeting is show level and area level rather than precise, and the location signal available in podcast delivery is coarse compared with what a search or social buy can do. A store buying a national show pays for a large audience that will never visit, and a store insisting on tight geography finds the reachable audience inside its radius is small.

The second objection is operational. Host reads take lead time, they require script approval, and once recorded into an episode they are effectively permanent, because the episode stays in the feed. If the offer changes or the unit sells, the read keeps running. Inserted spots avoid that and lose the endorsement effect. There is no version of this channel that gives you both, and the podcast page works through the trade in more detail.

Available on request. The published test for that status is that the work is not started and demand decides the order, and that is exactly where this sits. 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 they are issued. As with several entries in this family, the advertiser door and the developer door are not the same door: buying a campaign is open to a small business, while programmatic access that lets another system create and read campaigns is a reviewed application.

One shape note about what an integration would even cover. The inserted spot side of this business looks like the campaign objects the gateway already understands. The host read side does not, because it involves a script, a person, a recording schedule and an approval, none of which is an API call. Any page claiming a podcast integration should be asked which half it means, and this one means the first.

Design rather than description. None of it exists.

The second row carries a caveat the industry rarely puts in writing. A podcast impression is generally counted when an episode is downloaded, which is not the same as somebody hearing the spot. It is the accepted currency of the medium and it is a proxy. Treat a delivery report here as evidence that the file went out, not that the message landed.

Networks join this system against a fixed contract, which is why an unbuilt entry can still be described in detail. A single provider agnostic library inside the CRM sets out what any advertising platform must be able to do: hand back 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, identical everywhere. Twenty networks are registered against that contract today and exactly one is implemented. The remaining nineteen answer every call with a refusal naming themselves, so a stray call fails readably rather than looking like an outage at the vendor. This platform is not among the twenty, which is a narrower claim than registered and a true one.

The infrastructure beneath the adapters already exists and would not be rebuilt for a new network. Credentials are encrypted before storage using AES-256-GCM. Every action taken 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 these tables are shared across dealerships and a local time stamp cannot be reconciled afterwards. Campaign objects record which credentials created them and re resolve those credentials later, so disconnecting an account never orphans the work built under it.

Two routes and the store 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 stack of platform bills. It is live today and none of this page 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 history intact. Disconnect and delivery falls back to the managed path.

Neither reaches this platform today, and on podcasts specifically a dealership does not need software in order to advertise. The self serve route is open and a store can buy a schedule this week. What an integration would add is that podcast spend stops living in its own login and starts sitting beside the rest of the advertising a store buys, which is where the honest comparison between a slow trust channel and a fast response channel becomes possible.

One limit applies across the whole gateway 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. The vendor track is an application and a review before credentials exist. Our track is an adapter file against the seven operation contract, a credential block, then each operation wired and verified against a live account, scoped to inserted spots because the host read workflow is people rather than endpoints. Ours is predictable work, theirs is not on our calendar.

On measurement, podcasts are the slowest reading channel in this family and should be bought accordingly. Delivery figures appear as episodes are downloaded, which lags publication, and a show released weekly accumulates its audience over days. Judging a podcast flight after a week is measuring the release schedule rather than the advertising.

Do not expect same day lead counts here. The reasonable test is a reach and frequency question fixed in advance: how many listeners inside the area you care about will hear the spot, how often, across how many episodes, and did your countable channels move over the following weeks. If a store needs response this weekend, podcasts are the wrong instrument and any seller who says otherwise is selling.

The gaps that bite on this platform in particular.

We do not retrieve leads from this platform. Lead form retrieval is implemented for exactly one network and this is not it. A podcast spot collects no opt in, so a connection here would report a reach buy into the CRM rather than feed it shoppers.

We do not produce, script or arrange host reads. That is a creative and scheduling relationship between a store, the vendor and a presenter. No adapter automates a person reading a script, and describing it as an integration feature would be nonsense.

We do not run a promotional code or vanity URL attribution scheme. Those are how podcast response is usually traced, and setting one up and reconciling it is not something we do today.

We do not install or manage a pixel, we run no server side conversions endpoint, and we do not upload offline conversions.

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

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

Ask, and name the radius you sell into rather than the shows you like, because geography is what decides whether podcast advertising is affordable for a single rooftop or simply expensive. Requests are recorded against the platform they name and the tally decides build order.

Expect a question back about whether you want endorsement or reach. Those buy differently, cost differently and are measured differently, and a store that has picked one before the conversation starts gets a much better answer than a store that has not.

The managed path runs today regardless, and it does not wait on an adapter. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

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

Can I use my own Acast account?

Not through the CRM, since nothing exists to reach it. You can buy directly, because the self serve route is open to a small business. An integration would put podcast spend beside your other channels rather than grant access you already have.

What happens if I request Acast?

It is recorded against this platform specifically and counted, and the tally is the input to build order. Expect a reply asking whether you want host reads or inserted spots, because only the second resembles the adapters in this gateway.

Can podcast advertising be targeted to my trade area?

Only loosely. Targeting is show level and area level, and the location signal in podcast delivery is coarse. A national show wastes most of its audience on a local store, and a tight radius leaves a small reachable audience. That trade off is the channel.

What happens to a host read when my offer expires?

It usually keeps running, because the read is recorded into an episode that stays in the feed. Write host read copy about the store rather than about a price, and keep dated offers in the inserted spot format where they can be swapped out.

Is a podcast impression the same as somebody hearing the ad?

No. Impressions in this medium are generally counted on download, which is the accepted currency and still a proxy. Read a delivery report as evidence the file went out, and judge the flight on reach and frequency agreed in advance.

Requests are counted against the platform they name and the tally decides build order. Send your radius and which of the two you want, and expect a straight answer about cost.