SubmetryBlog

Free trial conversion rate: measure finished cohorts, not today's trial count

Define a trial-to-paid cohort, wait for its outcome and check event coverage before interpreting a subscription conversion rate.

A trial-to-paid conversion rate should answer a precise question: of the people who started a trial, how many reached their first paid period? Dividing this week's purchases by this week's trial starts mixes people at different stages.

Define the cohort before the percentage

Choose trial starts during a fixed interval, a single app and one environment. Define whether the unit is a customer or a subscription. Document how repeat trials and multiple products are treated. Keep trials still running out of a completed-outcome comparison.

For example, suppose 100 eligible trials started in one week. After their scheduled end and your documented payment-resolution window, 24 have a confirmed first paid period. The cohort conversion is 24%. This invented example illustrates the calculation; it is not a benchmark.

Let the observation window finish

A seven-day offer and a thirty-day offer cannot be compared after ten days. Group them separately or wait until both have had a complete opportunity to convert. Record the cutoff date and report pending outcomes alongside successes and non-conversions.

A cancellation notice is not proof that paid access has ended. Likewise, a trial-start event is not paid revenue. Keep conversion distinct from subscription churn.

Check the events, not just the dashboard

Submetry's RevenueCat guide documents trial-start and trial-conversion normalization. Client and subscription events need the same RevenueCat app user ID to connect the journey. Importing apps does not backfill old purchases, and a TEST webhook verifies connectivity rather than revenue.

Before interpreting results, validate a sandbox purchase, separate sandbox from production, and inspect missing or late events. This article's cohort method is an analytical recommendation, not a claim that Submetry exposes this exact report.

Investigate one useful difference

Compare equivalent cohorts by trial duration or onboarding experience, with counts beside percentages. Look for the first useful action users did or did not complete. Change one experience at a time; a percentage alone does not explain causation.

Explore Submetry and review the integration requirements before connecting product behavior to subscription outcomes.

Submetry’s public site currently offers a launch waitlist. Review the documented integration and join the waitlist if the planned launch fits your app.