Podcast ad blocking: what Podtastic means for sponsors

Podcast ad blocking now has a paid product behind it. Podnews reported on September 22, 2026 that an app called Podtastic strips ads out of podcast episodes on the listener's device, charges $9.99 a month for it, and hands up to 30% of that subscription to Apple and Google as standard app store commission. The creators whose ads get removed receive none of it.

What the app does and why hosts cannot block it

The app processes audio on the listener's own device. Podnews reports that it spoofs the user-agent of Apple's Safari, which defeats the user-agent filtering that podcast hosting companies use to block unwanted clients. Since the request originates from a real device with a plausible browser signature, there is nothing on the server side that reliably separates it from an ordinary listener.

Podnews says it reported the app to Apple on July 22 and that Apple's legal team required Podnews to deal directly with the developer, Ben Bowler, who describes himself as an "Adventurer and Startup Founder." Podnews had previously covered a similar app from the same developer that closed in May 2026. Neither Apple nor Google has acted on the report, and both keep collecting the commission.

Podnews describes the arrangement as unethical while noting it may be legal in the United States, because the stripping happens on the device, not on a server. That distinction is what has protected on-device ad blocking in the browser world for years, and it is the same argument here.

Your download still counts

None of this changes your analytics. The episode file was requested and delivered, so the download is real, qualifying, and countable under the IAB podcast measurement guidelines. The host-read ad inside that file was then removed before a human heard it.

Nothing in the RSS delivery chain can see that. A download counts a request for audio, not a person listening to it, which is the same limit covered in what counts as a podcast download. Prefix analytics measure the same event from one step earlier in the chain.

That gap has always existed. Listeners skip ads manually, drop off mid-episode, or leave the episode queued and never play it. Ad stripping adds a category where the ad is gone from the file entirely and the listener never had the option, which is worth separating from the ordinary skip behaviour described in Spotify's skip ahead podcast ads change.

Sizing the exposure without inventing a number

No published figure exists for how many podcast listeners use an ad-stripping app. Podtastic does not disclose subscriber counts, and Podnews did not publish an estimate. Any percentage you see attached to this story is somebody's guess, so keep it out of your reporting.

Describe the exposure with numbers you already have. Prefix reporting names the clients that request your episodes and leaves a remainder labelled as a browser or as unknown. Record that remainder as a monthly percentage and watch its direction over a quarter. If it climbs while your named-client mix holds steady, put the figure in front of the sponsor rather than leaving them to discover the discrepancy from a weak response rate.

Platform consumption data covers the surfaces that report it. Apple Podcasts and Spotify each publish their own listening figures, and neither depends on your download count, so they give you a second reading on completion inside those apps.

Then there is the outcome record, which Podnews points at directly: creators will see lower renewals and unhappier advertisers. A sponsor running a tracked offer against a solid delivery report and getting weak response will not renew, whatever the cause. Keeping the code redemption or landing page numbers alongside your delivery numbers is the only way to tell the two situations apart.

What to change in the sponsor conversation

Keep your rate where it is. What changes is how precisely you describe what the report proves.

Say delivery, not listening. A delivery report counts the audio requests your host served in a stated window. It does not claim the ad was heard. Writing that sentence into the proposal protects you when a sponsor asks why a campaign underperformed its impression count, and our ad impression guide covers the wording in more detail.

Keep one consistent delivery window across every quote so the numerator and the base never drift. How to measure podcast CPM walks through where those two figures usually come apart.

Push the outcome measurement onto the offer. A unique code, a dedicated landing page, or a survey question at signup gives the sponsor evidence that survives any argument about impression quality. That evidence also happens to be immune to ad stripping, because a listener who never heard the ad was never going to use the code anyway.

Agree the make-good terms before the campaign runs, including the report date and what happens if delivery misses the forecast. A contract that already distinguishes delivered audio from heard audio does not need renegotiating when a story like this one lands.

Where this is heading

Two things follow from the app store detail. Apple and Google are being paid a cut of a product that removes creator revenue, and both have been told about it. That is a policy question for the platforms rather than a technical problem podcasters can fix, and the pressure will come from networks and trade bodies, not individual shows.

The part you control is narrower and more useful. Put a tracked offer on every sponsorship, keep the redemption numbers beside the delivery numbers, and you can answer the question this story raises with your own campaign record instead of an argument about file integrity.

Start with Podder Analytics to see your client mix and delivery window in one consistent report before the next sponsor asks about it.