Case study · Mopo · Hamburg
278K readers.
75% accept the ad.
One line of code.
Hamburger Morgenpost embedded BotTalk's audio-advertising platform into its CMS — and turned a declining print-ad line into a growing audio one.
- 278K daily reach
- Single-line CMS embed
- 3 TTS providers
- $6–30 CPM
The numbers
What shipped — and what it did.
- 10% of readers became listeners
- 75% accepted the in-audio ad
- $6–30 CPM range
- 40–60% audio-ad fill rate
Mopo — Hamburger Morgenpost — is one of the leading newspapers in Northern Germany, a 75-year-old daily with a reach of more than 278,000 readers across print and digital.
Headquartered in Hamburg, Mopo has spent the past decade running the same arbitrage every legacy publisher knows: print ad revenue is sliding; digital-native competitors are taking the screen; and the reader experience cannot bend to make room for more banners.
By the time BotTalk arrived, the question was no longer whether audio would help — it was whether a new format could ship without rebuilding the CMS.
- Founded
- 1949
- Headquarters
- Hamburg
- Daily reach
- 278,000+
- Channels
- Print · Digital · Audio
What they were fighting
Three fronts. One revenue line.
-
01 · Print ad decline
Print ad revenue was sliding.
The same chart every legacy publisher knows: readers migrating to digital faster than the digital ad line could replace what print was losing. Audio is one of the few new inventory formats that hasn't been priced flat.
-
02 · Digital-native pressure
Digital-natives owned the screen.
The competition for attention on the device is brutal — and the competition for the ad slot is even worse. A new format that doesn't live on the screen at all changes the competitive set entirely.
-
03 · Reader experience
Ads couldn't get in the way of the read.
Every additional banner is a vote against the article. Mopo needed monetisation that ran in parallel to the read — not on top of it. Audio ads inside narrated articles do exactly that.
The verdict
Print ads fell. Audio ads grew.
The line turned around.
One integration, one CMS embed, and four steps of conversion between a daily reader and a delivered audio ad. The funnel holds at every step.
What they walked away with
Three wins. One operating layer.
-
01
A new ad inventory. Behind every article.
Parallel to the read.
Audio ads ship inside the narrated version of every article. The banner column doesn't move; the inventory grows. Mopo gets a new monetisation slot the digital-natives don't.
- 10% reader → listener
- 75% in-audio ad accept
-
02
One line of code. Three TTS providers.
No vendor lock-in.
The integration was a single-line script embedded into Mopo's CMS. Behind that line: routing across ElevenLabs, Microsoft Azure Neural, and OpenAI — swap any time, never go dark.
- 1 CMS embed
- 3 voice providers · live routing
-
03
Print fell. Audio grew. The line turned.
Revenue, recovered.
Monthly performance reports landed in Felix's inbox; the numbers held. Mopo built a digital revenue line that scales with article output — not with banner inventory.
- $6–30 CPM
- 40–60% fill rate
In their own words
The easy integration of the audio advertising platform was a turning point for us. It seamlessly integrated into our existing systems and addressed our biggest problems with declining print ad revenues.
The rollout
One integration. Four moves.
-
Step 01
Proof of concept.
Pilot embed against one section of mopo.de. Audio shipped against real articles, real readers, real ad slots. Numbers cleared the bar inside the pilot window.
-
Step 02
Single-line CMS embed.
A single line of JavaScript dropped into Mopo's CMS template activated audio across every article. API adjustments for optimisation followed; no rebuild required.
-
Step 03
Three voice providers, routed.
ElevenLabs · Microsoft Azure Neural · OpenAI. The control layer routes by need and swaps on the fly — quality stays editorial, costs stay predictable.
-
Step 04
Audio-ad inventory live.
Audio ads serve inside narrated articles across mopo.de. Felix receives monthly performance and revenue reports. The new line runs in parallel to print, not against it.
- Single-line CMS embed
- 3 TTS providers · live routing
- 75% in-audio ad accept
- Monthly revenue reports
- Hamburg-built · GDPR-compliant
Run this play in your newsroom
Talk to Andrey.
No deck. No pitch. Your CMS, your ad stack, your numbers. Thirty minutes. One call.