Subscriber Analytics Playbook: Metrics That Mattered for Goalhanger’s Growth

Hook: Fix the blind spots killing subscriber growth

Paid audio publishers have two common problems in 2026: scattered telemetry across apps, CMS and player SDKs, and dashboards that only tell half the story. That gap hides early warning signs — slipping engagement, rising trial drop-off, and subtle cohort churn — until revenue moves. This playbook maps the metrics, event schema, dashboards and workflows you need to measure acquisition, engagement, churn and LTV reliably, using Goalhanger’s 250,000+ paying-subscriber milestone as a practical anchor.

Why this matters in 2026 (and why Goalhanger’s milestone is instructive)

Late-2025 and early-2026 trends make subscriber analytics a revenue-critical capability:

• Privacy-first measurement: With cookieless targeting and consent-first telemetry now standard, server-side events and first-party analytics are required for accurate long-term subscriber measurement.
• Subscription scale: Publishers like Goalhanger report hundreds of thousands of paying users — Goalhanger reached ~250,000 paying subscribers (Press Gazette, Jan 2026) with an average revenue per subscriber of ~£60/yr. At that scale small percentage changes in churn or conversion produce multi-million-pound swings.
• Cross-platform complexity: Users interact via web players, mobile apps, smart speakers and Discord. You need unified identity and deterministic linking to build funnels and cohorts.

"Goalhanger now has more than 250,000 paying subscribers across its network… The average subscriber pays £60 per year… annual subscriber income of around £15m per year." — Press Gazette (Jan 2026)

Core metrics every paid-audio team must track

Below are the non-negotiables. Use them as the foundation for dashboards, alerts and experiments.

Acquisition metrics

• New subscriptions (by source): count of paid subs grouped by channel (organic, display, social, referral, podcast ad, email, partner).
• Conversion rate: sessions → trial → paid. Track step conversion and time-to-conversion.
• Customer acquisition cost (CAC): total channel spend / new paid subs (30/60/90-day windows).
• Paid conversion velocity: median days from first touch to paid subscription.

Engagement metrics

• Daily / Weekly / Monthly Active Subscribers (DAU/WAU/MAU) — platform-agnostic, user-level deduplicated count.
• Avg playback minutes per active subscriber — use this to benchmark ‘value delivered’.
• Episode depth: percent of episodes listened to >50% and >90%.
• Content breadth: average distinct shows/episodes consumed by subscriber per 30 days.
• Engaged subscriber rate: percent of paying subscribers meeting an engagement threshold (e.g., ≥30 mins/week).

Churn & retention metrics

• Monthly churn rate: cancellations / starting-subscribers for the period.
• Rolling churn (90-day): better for smoothing seasonal noise.
• Net revenue retention: revenue at period end vs beginning, accounting for upgrades/downgrades/cancellations.
• Survival function / cohort retention: retention curve for cohorts by signup month or source.

LTV & revenue metrics

• ARPU (per period): total subscriber revenue / active subscribers.
• Cohort LTV: discounted cumulative revenue per cohort over 12/24 months.
• Payback period: CAC / monthly gross margin per subscriber.

Funnel health metrics

• Top-of-funnel (TOFU): downloads, visits, ad impressions.
• Mid-funnel (MOFU): email signups, trial starts, previews consumed.
• Bottom-of-funnel (BOFU): subscription starts, payment completed, trial-to-paid.

Event tracking plan: stitch your signals into one source of truth

Start with a clear event taxonomy and event payload standard. Keep naming stable and document every property. The following event design balances developer ergonomics and analytics needs.

Key events and minimal properties

Implement these events across client SDKs and server-side sources. Each must include the identity and context fields listed.

{
  "event": "subscription_completed",
  "user_id": "user_12345",
  "anonymous_id": "anon_abc",
  "timestamp": "2026-01-10T12:34:56Z",
  "platform": "iOS",
  "product_tier": "premium_monthly",
  "price": 5.99,
  "currency": "GBP",
  "promo_code": "NEWYEAR",
  "referrer": "newsletter_id_78",
  "payment_gateway": "stripe",
  "trial_length_days": 7
}

• subscription_started — properties: product_tier, price, promo_code, utm_source, timestamp.
• subscription_completed — payment_gateway, revenue, currency, user_id, invoice_id.
• trial_started — trial_length_days, source, user_agent.
• trial_converted — days_to_convert, product_tier, revenue.
• playback_started — episode_id, show_id, duration_ms, position_ms, player_version.
• playback_completed — percent_played, completed_at, device_type.
• account_cancelled — cancel_reason, intent (self-serve / support), refund_issued.
• engagement_signal — event types like liked_episode, shared_episode, comment_posted.

Identity & linking rules

1. Record both user_id (authenticated) and anonymous_id (cookie/device) on every client event.
2. Reconcile server-side billing events (webhooks) to client events using invoice_id and email hash.
3. Prioritize deterministic joins (email or account id) over probabilistic linking.

Implementation checklist for engineers

• Instrument player SDKs (web/iOS/Android/SmartSpeaker) to emit playback events with position updates.
• Send billing events from backend webhooks directly to the analytics pipeline (avoid client-only billing events).
• Route events through a streaming collector (Kafka / Kinesis) into your data warehouse (BigQuery / Snowflake) for deterministic joins.
• Maintain an events registry (OpenAPI/JSON Schema) and auto-generate TypeScript/Python clients to keep payloads consistent.

Dashboards to build first — and what they should show

Design dashboards for different stakeholders: growth, product, ops, finance. Each should have a clear owner and SLA for data freshness.

1. Acquisition & Channel Performance

Purpose: evaluate CAC, channel ROI and conversion velocity.

• KPIs: new paid subs, CAC (7/30/90d), conversion rate by campaign, payback days.
• Charts: time-series of new subs by channel, funnel conversion ratios, cohort ROAS heatmap.

2. Subscription Funnel & Conversion Health

Purpose: spot bottlenecks from discovery → payment.

• KPIs: trial_start → trial_convert rate, payment_failure_rate, checkout abandonment.
• Charts: step-conversion waterfall, median time between steps, A/B test overlays.

3. Engagement & Content Value

Purpose: map content consumption to retention.

• KPIs: avg playback minutes, episode completion%, engaged subscriber ratio.
• Charts: heatmap of listens per episode, cohort retention vs avg playback minutes.

4. Retention, Churn & LTV

Purpose: forecast revenue and evaluate subscriber health.

• KPIs: monthly churn, 3/6/12-month cohort LTV, net revenue retention.
• Charts: survival curves per cohort, LTV curve, churn reason distribution.

5. Revenue & Financial Reconciliation

Purpose: map analytics revenue to financial reporting.

• KPIs: recognized revenue, refunds, MRR/ARR.
• Charts: MRR waterfall, revenue by tier, refund trends.

6. Real-time Alerts & Anomaly Detection

Purpose: detect regressions (e.g., spike in payment failures, sudden churn).

• KPIs: payment_failure_rate threshold, DAU drop >10% day-over-day, funnel conversion drop.
• Alerts: Slack + incident playbook integration when thresholds breach.

Concrete SQL & query examples

Example: monthly churn rate using event and subscription data in a warehouse. This assumes a subscriptions table with status and start/end dates.

-- Monthly churn rate for 2026-01
SELECT
  DATE_TRUNC('month', cancel_at) AS month,
  COUNT(DISTINCT user_id) AS cancelled,
  (SELECT COUNT(DISTINCT user_id) FROM subscriptions WHERE DATE_TRUNC('month', start_at) = DATE '2026-01-01') AS started,
  ROUND(COUNT(DISTINCT user_id)::numeric / NULLIF((SELECT COUNT(DISTINCT user_id) FROM subscriptions WHERE DATE_TRUNC('month', start_at) = DATE '2026-01-01'),0)::numeric, 4) AS churn_rate
FROM subscriptions
WHERE status = 'cancelled'
  AND DATE_TRUNC('month', cancel_at) = DATE '2026-01-01'
GROUP BY 1;

Example: 30-day cohort retention (simplified):

WITH first_sub AS (
  SELECT user_id, DATE_TRUNC('day', MIN(start_at)) AS cohort_day
  FROM subscriptions
  GROUP BY user_id
)
SELECT
  cohort_day,
  DATE_DIFF('day', cohort_day, DATE_TRUNC('day', events.timestamp)) AS days_since_signup,
  COUNT(DISTINCT events.user_id) AS active_users
FROM first_sub
JOIN events ON events.user_id = first_sub.user_id
WHERE events.event IN ('playback_started','playback_completed')
  AND DATE_DIFF('day', cohort_day, events.timestamp) BETWEEN 0 AND 30
GROUP BY 1,2
ORDER BY 1,2;

From measurement to action: playbooks that move the needle

Data without action is noise. Here are high-impact plays for paid audio publishers.

1. Reduce churn by targeting at-risk subscribers

1. Build a churn model using features: avg playback minutes/week, last playback date, episodes per week, number of friends referred, support tickets.
2. Score subscribers daily and create a retention workflow: automated in-app messages, personalized episode recommendations, promotional offers (discount vs content).
3. Measure lift: A/B test the outreach, track 30/90-day retention lift vs control.

2. Improve trial-to-paid conversion

1. Instrument trial cohort funnels: trial_start → week1_activity → trial_end.
2. Experiment with trial length and onboarding content. Example: test 7-day vs 14-day trials segmented by source.
3. Automate nudges tied to engagement (e.g., if playback_minutes >= 45 in first 3 days, send targeted offer at day 6).

3. Use content-level analytics to inform editorial and product

1. Tag content by series, topic, host and length.
2. Run correlation analysis between episode completion rates and retention by cohort to prioritize formats that retain subscribers longer.

Data governance, privacy and scaling (operational playbook)

As you scale, put guardrails in place to protect accuracy and compliance.

• Consent & PI handling: store consent flags with each event; avoid collecting PII in client events — hash emails server-side when necessary.
• Schema enforcement: run nightly schema validation jobs; reject or quarantine malformed events.
• Monitoring: set coverage checks — percent of subscription events with invoice_id present, percent of playback events with user_id after login.
• Cost control: aggregate noisy streams (position updates) and send sampled updates to analytics while keeping full fidelity in raw event storage for 30 days.
• Scaling: adopt streaming ingestion + ELT to a cloud warehouse. Use partitioned tables and materialized views for common KPIs.

Goalhanger case study: applying the playbook (numbers & impact)

Use Goalhanger’s public figures to demonstrate impact. With 250k paying subs, average revenue ~£60/yr, annual revenue ≈ £15M. Small percentage improvements matter:

• If monthly churn is 3% and you reduce it to 2.5%, annualized subscriber retention improves: a 0.5% point improvement on 250k subs retains ~15k additional subscribers across the year (est.). At £60/yr that’s +£900k incremental revenue annually.
• If trial-to-paid conversion increases from 10% to 12% on 100k trials, that’s +2k paid subs → ~£120k of recurring ARPU in year one.

Steps Goalhanger-style teams can take in 90 days:

1. Unify events into a single warehouse with deterministic identity linking (day 0–30).
2. Ship five dashboards (Acquisition, Funnel, Engagement, Retention, Revenue) and configure two key alerts (payment_failure_rate, DAU drop) (day 30–60).
3. Run two A/B experiments: 7-day vs 14-day trial and two onboarding sequences targeted at cohorts with low first-week engagement (day 60–90).

Advanced strategies and 2026 predictions

Look ahead and invest where the market is moving.

• First-party identity fabrics: expect more publishers to build identity layers that unify subscriptions, email, CRM and device IDs — this will become table stakes for accurate cross-platform attribution.
• Server-side personalization: with privacy constraints, personalization will shift server-side using aggregated behavioral signals rather than third-party cookies.
• Generative insights: in 2026, production analytics will include auto-generated explanations for KPI drops (anomaly explanations), saving analysts hours of manual root cause hunting.
• Monetization mix tracking: track non-sub revenue (live events, merch, ticket early-access, Discord benefits) as extension metrics inside subscriber LTV.

Actionable takeaways (start these this week)

• Implement the event schema — instrument the 10 core events and store them server-side and client-side with user_id + anonymous_id.
• Build the five core dashboards and assign owners with weekly review cadence.
• Run a retention experiment — target the top 10% of at-risk users with personalized re-engagement and measure 30/90-day lift.
• Automate alerts for payment failures and sudden DAU drops with runbooks for ops and product.
• Adopt cohort LTV as your planning metric — move away from one-off ARPU snapshots.

Final checklist for engineering & analytics teams

1. Event registry published (OpenAPI/JSON Schema).
2. Server-side billing ingestion and invoice link to user events.
3. Identity resolution implemented (email hash + account_id joining).
4. Five dashboards live, with data freshness SLA (e.g., hourly).
5. Anomaly detection & alerts configured.

Closing: turn metrics into predictable growth

In 2026, high-performing audio publishers treat subscriber analytics as the product control plane: an engineered system that collects, validates and surfaces signals that directly drive experiments and financial outcomes. Goalhanger’s scale shows the payoff — when you know which cohorts retain, which content hooks users, and which checkout flows leak, you can convert small improvements into major revenue gains.

Ready to move from scattered logs to a repeatable subscriber analytics engine? Start by instrumenting the 10 core events in this playbook and creating the five dashboards. If you want a jumpstart, download our sample events registry, SQL templates and dashboard wireframes, or book a technical audit to map this playbook onto your stack.

Related Reading

• Lighting That Photographs: Technical Tips to Make Your Listing Photos Pop
• Film Studies Debate Kit: Is the New Filoni ‘Star Wars’ Slate a Risk?
• From Parlays to Portfolios: What Sports Betting Models Teach Us About Probabilistic Trading
• Compact Countertop Kitchens for Urban Pop‑Ups: Tools, Logistics and Safety (2026 Field Guide)
• Workshop: How Coaches Can Use Live-Streaming Features to Grow Engagement