Shape
A series by cohort date; recent cohorts are still maturing
Chart · Paywalls
Paywall encounter rate is the share of each period's new customers who saw a paywall on the day they were first seen, and the share who had seen one by day 1, 3, 7 and 14. It counts customers with a paywall impression event, divided by new customers in the cohort.
Formula
Paywall encounter at day N = new customers with a paywall impression by day N / new customers
Shape
A series by cohort date; recent cohorts are still maturing
API name
paywall_encounter
Measures
Day 0 (Percent), Day 1 (Percent), Day 3 (Percent), Day 7 (Percent), Day 14 (Percent)
Filter and segment by
Country, Platform, App version
Definition
Customers are grouped by their cohort date. RevenueDot finds each customer's first paywall_impression event, which the SDK posts to /v1/events. A customer counts at day 0 when the first impression falls on the calendar day (UTC) of the cohort date, and at day N when it falls by the end of that day N. The five measures are cumulative, so each is at least as high as the one before.
The chart only knows about paywalls the SDK reports. A screen your app shows that never sends a paywall impression is invisible here. Customer filters apply: country, platform and app version. The cohort is marked incomplete until 14 days have passed, and the sandbox switch does not change customer counts.
You can open it in the dashboard under Charts or fetch it with GET /v2/projects/{project_id}/charts/paywall_encounter. The response has the same shape as RevenueCat's Charts API, so scripts written for that API keep working. The secret key needs the charts_metrics:charts:read permission. The Charts guide lists every parameter.
Worked example
A cohort of 1,000 new customers.
| Point in time | Customers who had seen a paywall | Paywall encounter |
|---|---|---|
| Day 0 | 700 | 70.0% |
| By day 1 | 780 | 78.0% |
| By day 3 | 820 | 82.0% |
| By day 7 | 850 | 85.0% |
| By day 14 | 860 | 86.0% |
70 percent meet a paywall in the first session and 14 percent never meet one in two weeks.
Why it matters
Conversion is exposure times the offer. If 40 percent of new customers never see a paywall, then even a perfect paywall converts at most 60 percent of them. This chart tells you whether to work on the paywall or on getting people to it.
The day 0 against day 7 gap shows when customers meet the paywall. A hard paywall in onboarding puts day 0 near the top. A freemium app that asks later shows a slow climb, and the gap tells you how long customers use the app before they are asked.
API
Same path and response shape as RevenueCat's Charts API, so existing scripts keep working.
curl "https://api.revenuedot.app/v2/projects/$PROJECT_ID/charts/paywall_encounter?resolution=day" \
-H "Authorization: Bearer $SECRET_KEY" # sk_... with charts_metrics:charts:read Reference: Charts guide · REST API v2
FAQ
It is the share of new customers who saw a paywall on their first day and by day 1, 3, 7 and 14. It shows how many people your paywall can convert at all.
The SDK sends a paywall impression event to RevenueDot. RevenueDot matches it to the customer and uses the earliest one.
Either the paywall is placed after the first session, or the app is not sending impression events for some screens. Check placement first, then the events.
No. They are cumulative. Day 7 includes everyone counted at day 0 and day 1.
Get started
Connect your app to RevenueDot Cloud, free up to $10,000 a month in tracked revenue, and all 43 charts fill from your store history after import.
Already have an account? Sign in · Prefer your own servers? Self-host free