Using Remote Audio

Last updated: July 16, 2026

Overview

Remote Audio enhances RedCircle's host-read workflows for remote shows. It replaces manual reporting with a single tracking pixel called Pulsar as the source of truth for billing and delivery.

There are two Remote Audio campaign types:

Remote: Dynamic Ad Insertion (DAI)

Ads dynamically inserted across all episodes

Remote: Faked-In

Ads dynamically inserted into a specific episode, for a defined period of time

Both are configured under a show's Host-Read Ads → Settings page, in the Remote Audio section, where each type has its own toggle (DAI Flights / Faked-In Flights).

What's changing

  • No more manual reporting. For campaigns using the Pulsar pixel, impressions are tracked automatically. Podcasters no longer submit manual reports at the end of a campaign.

  • Podcasters still own flighting. RedCircle does not control scheduling, targeting, or placement for Remote Audio campaigns. Podcasters set start/end dates and geo-targeting themselves, in their own ad server/hosting platform (Megaphone, Simplecast, etc.), matching what RAP shows.

  • Proactive delivery monitoring. If Pulsar doesn't detect traffic by a campaign's start date, or delivery goes quiet mid-flight, RedCircle automatically flags it, emailing the podcaster.

Setup: what a podcaster needs to do

  1. Grab the pixel. Find the unique Pulsar pixel URL in the campaign in RAP.

  2. Add it to your ad server. Implement it as the tracking pixel in the host platform.

  3. Confirm placement. Check the box in RAP once the pixel is live.

  4. Schedule the campaign. Set start/end dates (and geo-targeting, if applicable) directly in your own ad server. RAP will display the settings to match.

FAQ

What’s the difference between Remote DAI and Remote Faked-in?
Remote DAI campaigns run dynamically across all episodes for as long as the campaign is active.  Remote faked-in campaigns are dynamically inserted into one or a few episodes for a defined period of time. 

Do I still need to send a manual report at the end of the campaign?
No, for campaigns using the Pulsar pixel, manual reporting is no longer required since impressions are tracked automatically.

Where do I find the Pulsar pixel?
It's available within the campaign details in RAP.

Do I still need to schedule the campaign on my own hosting platform or ad server?
Yes. You're still responsible for setting up the campaign in your own system and matching the requirements shown in RAP. RedCircle doesn't control flighting, targeting, or placement for Remote Audio campaigns.

What if I'm not sure where to place the pixel?
Reach out to your RedCircle contact, we can point you in the right direction. Platform-specific setup guides for common hosting platforms and ad servers are in progress.

How are impressions tracked via Pulsar?
Pixels are tracked once per episode. We recommend avoiding inserting the ad multiple times during an episode. If the ad is inserted multiple times within the same episode, Pulsar will only count one unique impression. 

What happens if RedCircle doesn't see traffic from my pixel?
If Pulsar doesn't detect delivery by the campaign's scheduled start date, or delivery stops mid-flight, you'll get an automated email flagging it so you can check your setup. Our team is notified internally at the same time.

What happens if my campaign is paused?
If the campaign needs to be paused due to advertiser feedback/input, an email will be automatically sent to you with pause instructions. Impressions that occur in the “paused” period will not count towards billable impressions. 

How are remote audio ad reads reviewed?
Ad reads are transcribed and checked for compliance/quality through our AI Mic Check, the same as other automated host-read campaigns.

Is every show/network moving to Remote Audio right away? Not immediately. RedCircle is rolling this out network-by-network and show-by-show rather than all at once, so you may continue on the existing manual workflow for a while even if Remote Audio is generally available.