Rethinking How We Evaluate The New York Times Subscription Performance

Amir Malek8 Mar 2024

Problem

The New York Times sells its All Access bundle through the mobile and desktop sites and the News, Games and Cooking apps. After the move to a bundle-first strategy, the Growth Data team could not tell which product or path produced a subscription. The path depends on how the user reached the site, which pages they saw, whether they were logged in and more. Building one aggregate table per question gave fragmented metrics tied to the current user experience.

Example from the article: Paywalls in Cooking recipes, news articles and Games had slightly different tracking specifications, so a "did the user meet a paywall" dimension would have needed a query for every distinct impression event.

Solution in brief

Build one canonical data model that links each subscription to onsite and offsite metadata, with neutral multi-touch attribution and no weights. Take subscriptions from financial reporting data so totals match company-wide numbers. Define shared dimensions with stakeholders, unify the event tracking behind them, and join front-end events to subscriber records.

Questions this case answers
  • How to attribute a conversion to touchpoints of a multi-surface user journey with one reusable data model instead of per-question aggregate tables
  • How to enrich audited back-office conversion records with behavioral context that lives only in front-end events
  • How to tell where subscriptions come from when a bundle can be bought in many apps and sites?
  • How to choose an attribution model that serves many teams and survives product changes?

Tools and methods

  • Neutral multi-touch attribution — links a subscription to all touchpoints without weights; credit rules come later
  • Unified (canonical) data model — one transform feeds all aggregated metrics tables
  • Financial subscriber reporting data — source of truth for subscription records
  • Standardized dimensions — product, channel, platform, paywall encounter, agreed with stakeholders
  • Unified paywall tracking specification — one impression event format for every paywall
Continue reading — it's free

Google or a one-time email code. No password.