Engagement & retention
First-party data
Data a publisher collects directly from its own readers, names, emails, behaviour, subscriptions, comments, stored on the publisher's systems, controlled by the publisher.
First-party data is the data a publisher gathers directly from its own readers, through subscriptions, comments, newsletters, account creation, on-site behaviour, and stores in its own systems. Opposed to third-party data (bought from data brokers, tracked across the web via cookies), first-party data is the only data a publisher fully owns and controls.
Why this became the strategic conversation
Two simultaneous shifts made first-party data the most important asset a publisher can build :
- The death of the third-party cookie. Safari, Firefox and (eventually) Chrome are blocking or limiting third-party tracking. Advertisers who used to target via cookies now need first-party data from publishers.
- GDPR + DSA. The cost of relying on external trackers went up. The cost of running your own reader graph went down.
The publishers who win the next decade will be those with the biggest owned, engaged, identified audience graphs.
How a comment system feeds first-party data
A modern comment / debate system is one of the most efficient first-party data collectors in a publisher’s stack :
- A reader who comments is identified (account in your database).
- A reader who comments is engaged (high time-on-site, recurrent visits).
- A reader who comments leaves behind rich behavioural data : topics they care about, arguments they vote for, journalists they respond to.
Milenio reports that 10-11% of new daily registrations come directly from the comment widget. The widget is the fourth biggest source of new registrations in the entire newsroom, ahead of most content sections.
Why “first-party” depends on your vendor
This is where the comment-vendor choice matters. If the reader registers on Disqus (the vendor’s account, not yours), the data is not first-party for you. You can read it, but Disqus owns the relationship.
If the reader registers via Logora SSO into your own database, the account is yours. The participation data (votes, arguments, points) is your processor’s product, but the account graph belongs to you and stays in your CRM, your CDP, your subscription system.
Related concepts
See the Logora vs Disqus comparison for the data ownership angle.