iHeartMedia Integration for Dealerships

Terrestrial radio, an app and a very large podcast network sold together, and what a connection to that would and would not do.

iHeartMedia is the largest radio broadcaster in the country, and for advertising purposes it is three businesses sold from one desk. There is terrestrial radio, hundreds of stations with a local sales office in most markets. There is the iHeartRadio app, which turns those same stations into streaming inventory alongside custom stations and playlists. And there is a podcast network that ranks among the largest publishers in the medium by audience.

For a store the practical shape of that is one conversation covering the drive time spot, the streaming insertion and a podcast read, priced as a single schedule. The packaging is the product. It is also why radio has stayed on dealership media plans long after other traditional channels dropped off them, since a general manager who has run spots for a decade already knows the seller by name.

Buying happens through that seller rather than through a console. There is no advertiser dashboard where a store logs in and launches a schedule this afternoon, and that one fact shapes everything else on this page.

The case for radio at a car store is context. It reaches people while they are driving, which is the single situation where a vehicle is already on somebody's mind, and it reaches them at a cost per thousand that video cannot approach. A schedule that runs for months builds the kind of name recognition an independent rooftop cannot buy any other way, and the podcast side adds a host voice that carries more trust than any banner ever will.

The honest objection is measurement. Broadcast audiences are estimated from panels rather than counted, so the number on the proposal is a survey based projection of who was probably listening, not a record of who heard your spot. A store that wants a cost per lead figure from a radio schedule is asking a question the medium cannot answer, and any seller who answers it confidently is modelling, not reporting.

The second objection is commercial rather than technical. This is a negotiated rate card business. Rates move with demand, smaller advertisers can find themselves preempted when a national buyer wants the same avails, and the good inventory in a market is spoken for well before the month it runs. Read how streaming audio works for dealers before assuming the digital half behaves like the broadcast half. It 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 in the ad gateway for this broadcaster, no credential block, no authorization URL and no wire up checklist sitting behind the scenes waiting to be scheduled.

Access class is PARTNER, which is the vendor's gate rather than ours. Credentials require an application the vendor reviews before issuing them. That matters more here than on most entries in this directory, because the company is organised around market sellers rather than around self serve advertisers, and an advertising API is not the front door of the business.

One technical fact is worth stating because it changes what an integration would even mean. The streaming delivery and marketplace technology behind a large share of station audio is Triton Digital, which this broadcaster owns. A programmatic route into station streaming inventory therefore looks like a marketplace connection rather than a direct advertiser API, while the broadcast spots stay a negotiated buy. Those are two different pieces of work, and only one of them is the kind of thing an adapter file solves.

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

Read the second row for what is missing. No opt in comes back from a radio schedule, because a spot does not collect one. What a connection would buy a dealership is spend and delivery landing beside every other channel in the CRM, so the monthly comparison is one screen instead of four phone calls.

A page about an unbuilt platform can still be specific, because networks are not added here as bespoke projects. One provider agnostic library inside the CRM defines what any advertising platform has to 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 and exactly one is implemented. The nineteen that are not return a refusal naming themselves, so a stray call fails readably instead of looking like an outage at the vendor. This broadcaster 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 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 timezone relative stamp is one nobody can reconcile afterwards. Campaign objects record which credentials created them and re resolve those credentials later, so a disconnected 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, arriving as one 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 advertising 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 path.

Neither route reaches this broadcaster today. It is worth adding that on radio specifically a dealership does not need software in order to advertise, since the medium is bought by calling the market seller. What an integration would add is not access. It is having the schedule, the spend and the delivery sit in the same system as the follow up, which is where the comparison against your other advertising becomes possible at all.

The limit that applies across the whole gateway, stated on every page here: 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. The vendor track is an application and a review before any credential exists, and on a company built around market sellers that review is not a formality. Our track is an adapter file against the seven operation contract, a credential block, then each operation wired and verified against a live account. Ours is predictable work. Theirs is not on our calendar.

On measurement, treat audio as what it is. Radio and podcasts are reach and frequency channels, and the honest way to judge one is to decide the question before the schedule runs. How many people in the trade area heard the spot, how many times each, over how many weeks, and did the channels you can count move over that window. That is a slower and duller test than a lead report, and it is the only one the medium supports.

Nobody should expect same day lead counts from an audio buy, and a vendor who offers them is describing a model rather than a measurement. Set the frequency target first, run long enough for it to mean something, and read your direct traffic, your inbound calls and your walk in count over the period rather than the day after.

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

We do not retrieve leads from this platform. Lead form retrieval is implemented for exactly one network and this is not it. An audio schedule does not produce an opt in in any case, so a campaign here would be a reach buy reporting into the CRM rather than a lead source feeding it.

We do not provision or attribute call tracking numbers against a broadcast schedule. That is the mechanism most radio sellers reach for when a dealership asks what the spots did, and no part of our stack sets one up or reconciles it back to a daypart.

We do not install or manage a pixel, and we run no server side conversions endpoint and no offline conversion upload. Those are the three ways an audio vendor would argue a spot produced a visit, and we operate none of them.

We do not emit a vehicle catalog. No unit level feed leaves our stack for any advertising platform, so creative here would be audio about the store rather than individual stock.

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 there is no code that could do it.

Ask, with the store attached and with the markets you care about, because radio is bought market by market and a request that names one is worth more in the queue than a request that names a company. Requests are recorded against the platform they name, and the tally is what decides build order.

You will hear back from a person with a range or a reason. On this one expect a question back about whether you want the broadcast half, the streaming half or the podcast half, since those are three different pieces of work behind the same logo and only one of them looks like an ordinary adapter. If podcasts are what you actually want, the podcast page is the better starting point.

The managed path runs today regardless of any of this. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with iHeartMedia 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 broadcaster in the ad gateway.

Can I use my own iHeartMedia ad account?

Not through the CRM, because nothing exists to reach it. Radio is bought by calling the market seller, and a store can do that without any software. An integration would put the schedule and the spend beside your other channels, not grant access you lack.

What happens if I request iHeartMedia?

It is recorded against this platform specifically and counted, and the tally is the input to build order. Expect a reply asking which half you mean, since broadcast spots, app streaming and podcasts are three different builds behind one name.

Why is the access class PARTNER rather than PUBLIC?

Because credentials require an application the vendor reviews before issuing them. The company is organised around market sellers rather than self serve advertisers, so an advertising API is not the front door of the business and the review is a real step.

Can you tell me how many leads a radio schedule produced?

No, and neither can anyone else honestly. Broadcast audiences are estimated from panels rather than counted, so the sensible test is reach and frequency agreed in advance, read against your direct traffic and walk in count over the flight rather than the day after.

Is the podcast inventory a separate thing from the radio inventory?

Commercially it is sold together and technically it is not the same at all. Podcast spots are inserted into a download, station streaming runs through a marketplace, and broadcast is a negotiated avail. Only the middle one resembles the adapters in this gateway.

Requests are counted against the platform they name and the tally decides build order. Send your store, your markets, and whether you mean broadcast, streaming or podcasts.