Audacy Integration for Dealerships

Sports talk, all news and the local station cluster, and what connecting that to a CRM would honestly change.

Audacy is one of the country's large radio groups, built from station clusters in most of the major metros. What distinguishes it for an advertiser is format. Its strongest properties tend to be sports talk, all news and the local play by play rights that come with them, which is a very particular kind of listener and a very particular kind of hour.

Alongside the broadcast signal there is an app carrying the same stations as streaming audio, and a podcast operation built partly from studios the group acquired. So the sellable schedule can span a spot inside a game broadcast, an insertion into the same station's stream, and a read on a show that never touches a transmitter.

For a dealership, the reason this group comes up in conversation is almost always sports. Being the store that reads the score update is a position stores have wanted for as long as radio has existed, and it is sold that way. Whether that position is worth its price is a separate question, and the next section takes it seriously.

The genuine case is environment. A sports or news listener is engaged with live content rather than skipping past it, the audience is heavily local by definition, and association with a team or a morning news block transfers a kind of civic familiarity to a store that no performance channel produces. Dealership advertising has historically worked in exactly these formats, and that is not nostalgia, it is a reflection of who is in the car during the hours the inventory is sold.

The honest objection is that this is where dealerships most often buy prestige and call it marketing. Live game inventory is priced at a premium, it sells out around a season, and the spot that runs between the third and fourth quarter costs a multiple of the identical spot at ten in the morning. Some stores buy it because it works. Others buy it because the owner listens to that station, and that is a real budget going to a real place for a reason nobody writes down.

The second objection is stability. Radio group ownership, format lineups and sports rights all move around, and a schedule bought against one lineup can deliver against a different one by the end of a flight. Ask what happens to your rate and your daypart if the format changes mid flight, because the answer is in the contract and it is rarely in the proposal.

Available on request. The test published beside that status is that the work is not started and demand decides the order, and there is nothing here that stretches it. No adapter file exists in the ad gateway for this group. No credential block, no authorization URL, no checklist.

Access class is PARTNER, the vendor's gate rather than ours. A credential requires an application the group reviews before it is issued. On a radio company that gate reflects how the business is actually organised: revenue arrives through market sellers negotiating schedules, and programmatic access to the streaming inventory runs through audio marketplaces rather than through an advertiser API of the kind this gateway is built to speak to.

That distinction is the whole build question here. Reaching a station's streaming inventory is a marketplace problem with a known shape. Reaching its broadcast avails is a contract problem with a person on the other end. A page that promised both under one word would be selling you a plan as though it were a product, which is precisely what this directory exists not to do.

A design, not a description. None of this runs.

The row worth reading twice is the second one, for what it does not contain. No shopper arrives from a radio schedule, because a spot collects nothing. The value of a connection would be that spend and delivery land beside your other advertising inside the CRM, which is a modest claim and a true one.

Networks are not bolted on here as individual projects, which is why a page about something unbuilt can still describe the work precisely. A single provider agnostic library inside the CRM sets out what any advertising platform must be able to do: produce 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 is still alive.

Seven operations. One adapter file per network. Twenty networks are registered against that contract and one is implemented, and the other nineteen answer every lifecycle call with a refusal that names themselves, so a stray call fails loudly rather than looking like a vendor outage. This group is not among the twenty, which is a smaller claim than registered and an accurate one.

The shared 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 lands in an append only audit log carrying the company, the network, the user and the detail, timestamped in UTC deliberately, because these tables are shared across dealerships and a local time stamp cannot be reconciled later. Campaign objects remember which credentials created them and re resolve those credentials afterwards, so disconnecting an account does not strand the work built under it.

Two routes, and a dealership picks. The first is the webXintel Ads Network: included, run by our team from the selections you make in Leads Manager, invoiced as one line instead of 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, the account your store already holds is the one campaigns route through, on your billing, in your name, with your spend history intact. Disconnect and delivery returns to the managed path without you doing anything.

Neither route reaches this group today. Worth saying plainly: on radio you do not need us in order to advertise. A phone call to the market seller buys the schedule. What an integration adds is that the schedule stops living in a separate email thread, and starts sitting in the same system as the follow up work.

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 that move at different speeds. Theirs is an application and a review before any credential exists. Ours is an adapter file against the seven operation contract, a credential block, and each operation wired and verified against a live account. Our half is predictable engineering. Their half is a queue we do not control and would not pretend to schedule.

On measurement, hold this to what audio can actually support. Radio is a reach and frequency channel. The right way to judge a flight is to fix the question before it starts: how much of the trade area heard the spot, how often, across how many weeks, and did the countable channels move over that window. Sports schedules add a wrinkle, since delivery clusters around a game calendar rather than spreading evenly, so a four week average can hide the fact that the whole flight landed on three nights.

Do not expect same day lead counts from an audio buy, and be careful with any seller who offers them. Set the frequency target first, run the flight long enough for it to mean anything, and read direct traffic, inbound calls and walk in count across the period rather than the morning after.

These are the specific gaps that apply here.

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

We do not set up or reconcile call tracking numbers against a station schedule. That is the standard answer a radio seller gives when a dealership asks what the spots did, and nothing in our stack provisions one or ties a call back to a daypart.

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

We do not emit a vehicle catalog. No unit level feed goes to any advertising platform from here, so the creative is audio about the store, never a specific stock number.

We do not upload hashed audiences. Your customer list never becomes a targeting segment on any network.

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

Ask, and name the market and the format you actually want, because a request that says sports talk in one metro is a far more useful signal than a request that names a company operating in dozens. Requests are recorded against the platform they name and the tally is the input to build order.

A person replies with a range or a reason. On this one, expect a question about what you would pay for game adjacent inventory versus ordinary rotator time, because the gap between those two numbers is usually where a dealership radio budget quietly goes.

The managed path runs today and waits on none of this. Pricing for the platform sits on the pricing page and does not move based on which networks you turn on. If the underlying question is whether digital audio behaves differently from broadcast, the streaming audio page answers it.

Does LeadLocate integrate with Audacy today?

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

Can I use my own Audacy ad account?

Not through the CRM, since nothing exists to reach it. Radio is bought by negotiating with the market seller, which a store can do unaided. An integration would put the schedule and spend beside your other channels rather than give you access you already have.

What happens if I request Audacy?

It is recorded against this group specifically and counted, and that tally feeds build order. Expect a reply that asks which market and which format, because a national request tells us far less than a metro and a daypart.

Is sports inventory worth the premium for a dealership?

Sometimes, and sometimes it is a preference dressed as a plan. Live game spots cost a multiple of the same spot at mid morning. If you buy it, buy it for the frequency it delivers against a defined audience, not because the station sounds like your store.

What happens to my schedule if a station changes format?

That is a contract question and worth asking before signing. Group ownership, formats and sports rights move, and a flight bought against one lineup can deliver against another. The proposal rarely covers it and the agreement usually does.

How would I know whether the flight worked?

By deciding in advance what reach and frequency would count as a pass, then reading direct traffic, inbound calls and walk ins across the whole flight. Sports schedules cluster around a game calendar, so judge the period rather than any single day.

Requests are counted against the platform they name and the tally decides build order. Send your store, the metro you buy, and what you would spend on game adjacent time.