Subscription Analytics and Paywall Tools for Indie App Developers
Solo and small-team app developers rarely have a data analyst or a growth engineer on hand. The value of a subscription platform therefore comes down to how quickly one person can answer three questions: what is my revenue doing, where are paying users coming from, and which change actually moved the numbers. The capabilities below — charts, Apple Search Ads attribution, Slack notifications, experiments, and paywalls — each answer one of those questions. This guide walks through what each does and the specific settings or fields you need to configure it. Which capabilities are available on which plan is a commercial detail to confirm with the platform owner before you rely on it.
Charts: read revenue before you change anything
The charts tab in the dashboard presents a set of revenue and subscription views. The default view is useful, but the real leverage is the Segments dropdown, which splits a single metric by a dimension you choose.
A few configurations worth knowing:
- Break down Active Subscriptions by product to see which SKU carries the business.
- Break down Revenue by product to compare a new offering against an established one.
- Build a cohort-style view by setting the MRR chart's segment to "First purchase month", the view option to "Stacked area", and the date range to "All time". The result is a layered chart showing how each acquisition cohort's contribution to recurring revenue accumulates over time.
Before you act on any chart, confirm three settings: the metric, the segment, and the date range. A revenue drop that looks alarming on a 30-day view can disappear on an all-time view, and a segment that looks flat can hide two products moving in opposite directions.
Apple Search Ads attribution: separate paid quality from paid volume
If you run Apple Search Ads, the Apple Search Ads integration pulls campaign data into the platform so it appears alongside subscription metrics in charts. Once connected, you can segment charts by campaign or ad group.
Download volume from ads tells you almost nothing on its own. The question that matters is whether users acquired through ads convert to paid at a comparable rate to organic users. A blended lifetime value figure mixes both groups together, so a campaign can look healthy in aggregate while its own cohort underperforms. Segmenting by campaign or ad group separates the two populations and shows where the gap sits.
The practical check: compare conversion rate and lifetime value for ad-acquired versus organic users on the same chart, then decide whether the campaign is worth scaling or whether the paywall or onboarding needs work first. If ad-driven users start trials at a similar rate but cancel sooner, the fix belongs in the retention path rather than the ad creative.
Slack integration: a real-time pulse on purchase events
The Slack integration posts a message to a channel of your choosing each time an in-app purchase event occurs in your iOS or Android app. Setup takes only a few minutes: create a dedicated channel, connect the integration, and pick the events you want to see.
Two uses stand out for a solo developer. First, it is a motivating, concrete signal that real people are buying. Second, it functions as an early-warning system — an unexpected burst of new trials or a spike in cancellations shows up in the channel before it shows up in a weekly report. Keep the channel focused on purchase events so the signal stays readable.
Experiments: test across the whole customer journey, not just the tap
Experiments is an A/B testing tool built for in-app purchases. It works through the offerings model: users are automatically split between two offerings, and the system measures the difference in outcomes across the customer journey between them. Because the split is at the offering level, anything attached to an offering — including paywalls and offering metadata — can be tested.
That scope is the point. A pricing change can be evaluated not only on how many users start a trial, but also on how many cancel and on lifetime value per customer. A test that only measures trial starts can easily reward a change that increases sign-ups while quietly increasing churn.
A concrete first experiment: test when the paywall appears. Create an offering metadata field named "showOnFirstLaunch" and give the two offerings opposite values — "false" on one, "true" on the other. Your app then reads that field at launch and presents the paywall only when the value is "true". The offering split handles assignment, and the results show whether an immediate paywall helps or hurts across the full journey.
Paywalls: two migration paths, one testing loop
The Paywalls feature offers two ways to get started, and the choice depends on how much of your existing paywall you want to keep.
Footer view. Keep your custom marketing view and place the platform's footer view beneath it. The footer handles the StoreKit and payment code, displays copy that reflects the user's trial eligibility, and shows the products and pricing you configure remotely in the dashboard. This is the lower-effort path if you already have a paywall design you like.
Full templates. Replace the paywall with a customizable template built to industry best practices. All configuration happens in the dashboard, so copy and layout changes ship without a code change or an App Review wait.
Either path connects to Experiments, so you can test the result rather than guess. The decision rule: if your current paywall design is a differentiator, start with the footer view; if speed of iteration matters more, start with a template.
A starting checklist
If you are adopting these capabilities for the first time, work through them in this order:
- Open the charts tab and confirm the metric, segment, and date range on the view you rely on most.
- If you run Apple Search Ads, connect the integration and compare ad-acquired versus organic conversion on one chart.
- Create a Slack channel for purchase events and watch it for a week to learn your baseline.
- Pick one experiment — paywall timing is a good first candidate — and define the outcome you will judge it on before you launch.
- Choose footer view or a full template for your paywall, then feed the result into the next experiment.
Frequently asked questions
What does the Segments dropdown actually change in a chart?
It splits one metric by a dimension you select, such as product or first purchase month. The metric, the segment, and the date range together determine what the chart shows, so check all three before drawing a conclusion.
Why would ad-acquired users be worth less than the blended lifetime value suggests?
A blended figure averages ad-acquired and organic users together. If the ad cohort converts to paid at a lower rate, its own value is lower than the average implies, and segmenting by campaign or ad group makes that visible.
How does an offering-level experiment differ from testing a single button?
Because users are split between two offerings, every element attached to an offering — paywall design, pricing, and offering metadata — can be compared, and the measurement covers trial starts, cancellations, and lifetime value rather than one interaction.
Should I use the paywall footer view or a full template?
The footer view keeps your existing marketing design and adds the platform's payment and product-display layer beneath it. A full template replaces the paywall with a configurable design you can change from the dashboard without shipping code. Choose the footer if your design is a differentiator; choose a template if fast iteration matters more.