Paywall Analytics Events: What to Track Before You Optimize Pricing
Track the right paywall analytics events for impressions, CTA taps, purchases, variants, revenue per visitor, and subscription conversion.
Summary
A focused paywall instrumentation guide for teams that want cleaner conversion data without over-tracking.
Separate paywall impressions from CTA taps and purchases.
Always include source, plan, placement, and variant fields.
Measure revenue per visitor alongside conversion rate.
The four events every paywall needs
A paywall funnel needs Paywall.viewed, Paywall.ctaTapped, Purchase.started, and Purchase.completed. Without all four, it is hard to know whether a weak result is caused by poor targeting, weak copy, store purchase friction, or failed purchase verification.
Teams often jump straight from impressions to revenue. That hides the middle of the funnel. A high impression count with low CTA taps suggests messaging or offer problems. A high CTA count with low Purchase.completed suggests checkout or product configuration problems.
- Paywall.viewed: the user saw a paywall.
- Paywall.ctaTapped: the user showed buying intent.
- Purchase.started: the store flow started.
- Purchase.completed: a verified purchase succeeded.
Payload fields that make variants comparable
Every paywall event should carry the same experiment and variant names. The payload can also include source, placement, productId, plan, and offerType. Keep values controlled and short so they group cleanly in dashboards.
Do not include raw user identifiers, emails, or free-form survey answers in paywall events. Paywall analytics should explain which offer worked, not who the person is.
Conversion rate is not enough
A variant with a lower conversion rate can still win if it sends more users to annual plans or higher-value products. Track revenue per visitor and purchase amount, not only conversion percentage.
For subscription apps, connect provider webhooks later to capture renewals, refunds, trials, cancellations, and billing retry events that occur while the app is closed. Use one source per transaction unless separate provider and client records are intentional.
FAQ
Common questions
What is the most important paywall event?
Paywall.viewed is the entry point, but Paywall.ctaTapped and Purchase.completed are needed to understand intent and conversion.
Should paywall events include price?
They can include a normalized plan or productId. Use revenue amount on verified purchase events when available, and avoid sending personal billing details.