Audience leakage

Loss of reader engagement and first-party data to third-party platforms (Facebook, X, Disqus) when the publisher hosts conversation off-domain. Reversed by bringing the conversation back to the publisher's own site.

Audience leakage is what happens when a publisher’s most engaged readers end up commenting, debating and discussing the article somewhere else, typically Facebook, X, or a third-party comment vendor with its own account model. The publisher produced the article; another platform captured the engagement.

The cost compounds three ways :

  1. First-party data that should be growing your subscriber graph grows the platform’s instead.
  2. Recurring traffic flows to the platform, reader returns to Facebook to check replies, not to your site.
  3. Editorial signal (what the audience is arguing about) is invisible to the newsroom.

The Milenio reversal

When Milenio replaced Facebook Comments with on-domain Logora SSO, daily comment volume grew +150% in the first year and +100% in the second. The comment widget became the fourth biggest source of new daily registrations at Milenio, ahead of most content sections. The audience didn’t disappear when Facebook left ; it returned to a destination Milenio controls.

See first-party data for the data-ownership angle and the Milenio case for the full reversal numbers.

⌘K / Ctrl+K to open