How Runna scaled subscriptions 30x and turned subscription events into growth
Runna is a running-coach app that pairs personalized training plans with iOS and Android delivery.
Its subscription story is a useful reference for teams weighing a build-your-own payments layer against a managed subscription platform. The path went from a web-payment workaround that App Store review rejected, to compliant in-app purchases in about a week, to a 30x subscription increase between December 2022 and December 2023. This page restates that sequence in a reader-oriented form and adds a decision checklist, an integration field map and a worked example. All company-specific figures, funding amounts, team sizes and commercial terms are treated as owner-supplied reference points rather than current claims.
What Runna is and why the subscription layer mattered
Runna gives runners tailored plans through iOS and Android apps. The case study describes a {{OWNER_APP_RATING}}-star rating across {{OWNER_REVIEW_COUNT}} reviews as of {{OWNER_RATING_DATE}} and positions the app as a top health and fitness app globally. For a subscription business of that shape, the hard part is rarely the paywall screen itself; it is the recurring lifecycle around it: trial starts, renewals, cancellations, refunds, transfers between accounts and the events that marketing, product, support and analytics teams each need.
Runna's early product was a web MVP in which users entered running history and goals into a form and received a PDF plan by email. That MVP attracted first funding and let Walter Holohan join full time as tech lead, with a mobile app as the first priority. The mobile plan was to link out from the app to the website for payment. App Store review rejected that approach.
Build versus buy: the decision that followed rejection
The rejection pushed the team to look at compliant in-app purchase options. Holohan considered an open-source React Native library but found that implementing payments was only part of the problem. The surrounding infrastructure and ongoing maintenance would still sit with Runna, and the team judged that building it themselves would not set them up for long-term success.
A practical decision checklist for teams at the same fork:
- Does the option cover the full lifecycle, not just the purchase call? Look for trial starts, renewals, cancellations, refunds and restores.
- Who owns ongoing maintenance when store APIs, receipt formats or platform rules change?
- Can the same subscription state be read consistently on iOS and Android?
- Does the vendor expose events that marketing, product, support and analytics tools can consume without custom glue?
- Is the pricing model aligned with growth, or does it penalize success?
- Is the documentation and community support strong enough for the team's actual stack?
Runna chose a managed subscription platform after evaluating those questions. The team cited documentation quality and community support for the React Native SDK. The case study describes the pricing model as {{OWNER_PRICING_MODEL_DESCRIPTION}}. In-app purchases were added and the app was approved within a week of signing up.
Growth context: the numbers as dated reference points
Runna's app launched in March 2022. The case study reports that subscriptions grew {{OWNER_GROWTH_MULTIPLE}} between {{OWNER_GROWTH_START}} and {{OWNER_GROWTH_END}}. It also reports that Runna raised {{OWNER_FUNDING_AMOUNT}} in funding as of {{OWNER_FUNDING_DATE}} and grew its engineering team from {{OWNER_TEAM_START}} to {{OWNER_TEAM_CURRENT}} people as of {{OWNER_TEAM_DATE}}, with a product roadmap planned for the following year. These are historical reference points from the case material, not a current snapshot. Treat them as a dated example and check present conditions before relying on any figure.
The engineering rationale behind the platform choice was straightforward: developers should spend time on subscriber-facing features rather than on the mechanics of subscriptions and in-app payments. Runna's roadmap at the time included a machine-learning model that adapts each user's training plan to their stats, usage and performance, plus integrations with third-party wearables and fitness apps.
Integration field map: what each tool receives
Runna's growth, marketing, support and analytics teams use pre-built integrations rather than duplicating transaction events or caching them locally. The value is in the event contract: each downstream tool receives the subscription events it needs, once, from the source of truth.
A reader-oriented map of the integrations:
- AppsFlyer (attribution and mobile marketing analytics): receives trial starts, subscriptions and cancellations from iOS and Android. Runna used this to identify markets that were raising customer acquisition cost and to optimize Apple Search Ads against top-converting keywords rather than upper-funnel events.
- Mixpanel (product analytics): receives key lifecycle event data so Runna can correlate user behaviors with customer value. The team identified traits of users with the highest trial conversion rate, including connecting a calendar.
- Intercom (CRM and lifecycle messaging): receives real-time subscription events such as trial expirations for lifecycle messaging, win-back campaigns and trial-transparency notifications.
- Customers tool (support view): gives a centralized, cross-platform view of usage and purchase timelines so support can debug issues and spot patterns such as trial fraud.
A useful distinction for support teams: a complaint about being charged immediately after starting a trial is not always a billing defect. It can be a second-trial attempt from a new account. The Customers tool shows when a user has been transferred from another user, which lets support separate a genuine billing problem from an attempt to claim an additional free trial.
Outcomes as reported, with the conditions attached
The case material reports several outcomes tied to specific integrations. Each is a dated, company-reported result rather than an independently verified benchmark:
- AppsFlyer plus the subscription platform: a {{OWNER_CAC_DECREASE}} decrease in customer acquisition cost after {{OWNER_CAC_METHOD}}, and a {{OWNER_ASA_TRIAL_LIFT}} improvement in trial conversion rate on Apple Search Ads for US campaigns after {{OWNER_ASA_METHOD}}.
- Mixpanel plus the subscription platform: a {{OWNER_MIXPANEL_TRIAL_LIFT}} increase in trial conversion rates after {{OWNER_MIXPANEL_METHOD}}.
- Intercom plus the subscription platform: a {{OWNER_CSAT_SCORE}} CSAT score over {{OWNER_CSAT_PERIOD}}, supported by trial-end notifications and lifecycle messaging.
- Customers tool: improved ability to diagnose trial fraud and give support a clear view of each subscriber's journey.
These figures describe Runna's experience in a particular period. They are not a promise that another app will see the same lift, and the underlying conditions (market mix, ad platform, product behavior) differ by business.
Worked example: from a behavioral signal to a product KPI
Runna's Mixpanel work produced a concrete example of how a subscription event becomes a product decision. The team looked at users with the highest trial conversion rate and found that those who connected a calendar had better retention. That single behavioral signal was surfaced to the business and turned into a KPI of success. The same logic is now being applied to other connections, such as wearable devices, so the product roadmap can prioritize support for the devices that correlate with retention.
A reader can reuse the pattern without copying the numbers: pick one in-product action that plausibly signals commitment, join it to subscription lifecycle events, compare conversion and retention across users who did and did not take that action, and only then decide whether to promote the action in onboarding or prioritize it on the roadmap. The value comes from the join between behavior and subscription state, not from the analytics tool alone.
Owner input template for company-specific claims
The following clauses must be confirmed by the page owner before publication. Replace each variable with an owner-verified value or remove the clause.
- Funding statement: Runna has raised {{OWNER_FUNDING_AMOUNT}} in funding as of {{OWNER_FUNDING_DATE}}.
- Team size: the engineering team has grown from {{OWNER_TEAM_START}} to {{OWNER_TEAM_CURRENT}} people as of {{OWNER_TEAM_DATE}}.
- Growth metric: subscriptions grew {{OWNER_GROWTH_MULTIPLE}} between {{OWNER_GROWTH_START}} and {{OWNER_GROWTH_END}}.
- App rating: the app holds a {{OWNER_APP_RATING}} star rating across {{OWNER_REVIEW_COUNT}} reviews as of {{OWNER_RATING_DATE}}.
- Acquisition cost result: customer acquisition cost decreased by {{OWNER_CAC_DECREASE}} after {{OWNER_CAC_METHOD}}.
- Trial conversion result (AppsFlyer): trial conversion rate on Apple Search Ads for US campaigns improved by {{OWNER_ASA_TRIAL_LIFT}} after {{OWNER_ASA_METHOD}}.
- Trial conversion result (Mixpanel): trial conversion rates increased by {{OWNER_MIXPANEL_TRIAL_LIFT}} after {{OWNER_MIXPANEL_METHOD}}.
- CSAT result: the CSAT score was {{OWNER_CSAT_SCORE}} over {{OWNER_CSAT_PERIOD}}.
- Commercial terms: the pricing model is described as {{OWNER_PRICING_MODEL_DESCRIPTION}}; any free-tier or trial terms are {{OWNER_COMMERCIAL_TERMS}}.
- Testimonial attribution: quotes are attributed to {{OWNER_SPEAKER_NAME}}, {{OWNER_SPEAKER_TITLE}}, with permission confirmed as {{OWNER_QUOTE_PERMISSION}}.
Frequently asked questions
Why was Runna's first mobile payment approach rejected by the App Store?
The initial plan was to use the app as a companion to the website and link out to pay on the web. App Store review rejected that approach because it did not use compliant in-app purchases. After adopting a subscription platform, Runna added in-app purchases and was approved within a week.
What does the AppsFlyer integration actually send?
It syncs subscription events such as trial starts, subscriptions and cancellations from iOS and Android into AppsFlyer. Runna used those events to identify high-CAC markets and to optimize Apple Search Ads against top-converting keywords rather than upper-funnel events.
How did Runna use Mixpanel to improve trial conversion?
The subscription platform sent key lifecycle event data to Mixpanel so Runna could correlate user behaviors with customer value. The team found that users who connected a calendar had better retention, surfaced that to the business as a KPI, and reported a 5.7% increase in trial conversion rates after turning those findings into product improvements.
How does the Customers tool help distinguish trial fraud from a billing complaint?
Support sometimes hears from users who say they were charged immediately after starting a free trial. In some cases the user created a new account to claim a second free trial. The Customers tool shows when a user has been transferred from another user, giving support a cross-platform view of the subscription journey so they can tell the two situations apart.
Are the reported percentages a benchmark other apps should expect?
No. The figures describe Runna's results in a specific period and depend on its market mix, ad platform, product behavior and integration setup. They are useful as a dated reference, not as a forecast for another business.