AppWhy
Growth analytics for mobile apps

From first search
to paying user.

AppWhy maps how people find your app,
use it and pay.
See where they drop off, and why.

We only email you about your invite. Privacy

  • Read-only access
  • Revoke any time
  • Hosted in the EU

For solo developers, growing teams,
and every portfolio in between.

AppWhy's revenue path for a sample app: from store impressions to revenue, with the step where downloads fell highlighted and its causes listed.The morning check on a phone.

Sample studio and data,
on screens from the AppWhy beta.

The whole journey

See where people drop off.
And why.

Every step from first impression
to first payment, counted.
The weakest step is flagged,
with its likely cause.

Trailhead

Last 28 days · sample data

  1. Seen in the storeImpressions · App Store Analytics
    812k28-day total
  2. Visited your pageProduct page views · App Store Analytics
    148k18.2 % of previous
  3. DownloadedFirst-time downloads · App Store Analytics
    38.2k25.8 % of previous
  4. Used the appActive users · PostHog
    24.9k65.2 % of previous
  5. Saw the paywallPaywall views · PostHog
    17.4k69.9 % of previous
  6. Started a trialTrials · RevenueCat
    2,19412.6 % of previous
  7. PaidPaying customers · RevenueCat
    82037.4 % of previous
Discover, use, pay

Every step of the journey.

Store, usage and revenue signals,
joined by app, day and platform.
See each step, and where people leave.

  • App Store Search62 %
  • Browse21 %
  • Web referrers11 %
  • App referrers6 %

Where they find you

Search, browse and referrals, by country.
Your keywords, right beside them.

Active devices24.9k
Sessions61.2k

How they use it

Sessions, active devices
and the events you already track.

BuildTop failureShare
1.0 (4)Products did not load41 %
1.0 (3)Payment canceled4 %
0.9 (12)Payment canceled3 %

Why they pay, or don't

Paywall views, trials and purchases,
and the reason each one failed.

Cause and effect

Pick any change.
See what caused it.

Every event around a change,
lined up and weighed.
What is ruled out, how sure it is,
and what would confirm it.

  • Timing
  • Platform
  • Source
  • Country
  • Build

Search downloads fell to 0

Since Oct 9

Trailhead · iOS · Sep 1 – Oct 16 · sample data

  • App Store Search
  • Other sources
App Store Search downloads, Sep 1 – Oct 16 (sample data)About 190 a day until Oct 8, then 0 from Oct 9. Other sources held at about 40 a day.080160240Sep 1Sep 15Oct 1Oct 16
Releases
Listing
Prices
No changes in this range

Likely causes, ranked

  1. 5.1.7 release · Oct 8Strong timing match

    Started the day after 5.1.7 went live.
    Only App Store Search fell.
    Browse and referrers held.

    App Store Connect
  2. Keywords edited · Sep 29Ruled out

    Search stayed near 190 a day
    for 10 days after the edit.

    App Store Analytics
  3. Price or offer changeRuled out

    No price or offer changed in this range.

    RevenueCat
  4. Market-wide dropRuled out

    Your other apps' Search downloads held steady.

    App Store Analytics
i
Correlation, not proof.
The timing and scope point to 5.1.7.
Inside AppWhy

From the number
to the why.

Follow the money
to the step that changed.

Impressions to revenue, week over week.
The first step that moved is highlighted.

  • Store page to revenue, step by step
  • Each finding linked to its source
  • Paywall health by build
The revenue path for a sample app: downloads fell 80 % while every other step held.
  • 56metrics
    from day one
    App Store Connect, RevenueCat
    and App Store ratings.
  • 11event types,
    one timeline
    Releases, listing edits, prices,
    offers, paywalls, ranks and more.
  • 4causes tested
    per change
    The release, the market,
    missing data and the season.
  • 3 hbetween Apple
    sales checks
    Until the day's report lands,
    and a flag when it is late.
Works with your stack

Bring the tools
you already use.

AppWhy reads them, read-only,
and never writes back.
You can revoke access at any time.

  • LiveApp Store Connect
  • SoonGoogle Play
  • LiveRevenueCat
  • SoonMixpanel
  • LivePostHog
  • SoonAdMob
  • SoonPaddle
  • SoonAny API
  • Read-only, alwaysAppWhy never writes to your consoles.
  • Encrypted keysStored in Vault, never in logs.
  • Apple's Admin key is never keptUsed once, then discarded.
  • Revoke any timeOne click removes a key.
  • Hosted in the EUStored in Stockholm, Sweden.
  • Export or deleteTake it all, or delete it.
Who it's for

From one app to eighty.

  • Solo developers

    «Is anything wrong?» in ten seconds.
    No analytics SDK required.

  • Studios

    Every app in one morning check.
    Roles for every teammate.

  • Agencies

    Switch between client workspaces.
    Invite each client to a read-only view.

FAQ

Questions, answered.

What is AppWhy?

AppWhy is growth analytics for mobile apps. It maps the whole journey: how people find your app, how they use it, and why they pay or don't.
When a number moves, it shows what changed, where in the journey, and the likely cause.

Can AppWhy show why people don't convert?

Yes. With PostHog connected, it counts paywall views, empty paywalls, buy taps and failed purchases per build and platform.
A paywall that breaks shows up the next morning, with the build that started it.

Can I see where my downloads come from?

Yes: App Store Search, Browse, web and app referrers, by country, next to the keywords in your listing.
Listing edits sit on the same timeline, so you can see whether a change worked.

Which tools does it work with?

Today: App Store Connect, RevenueCat, PostHog and App Store ratings.
Next: Google Play, Mixpanel, AdMob and Paddle.

Does AppWhy need write access to my accounts?

No. Every connection is read-only, and AppWhy never changes anything in your consoles.
Apple's one-time Admin step only starts Apple's analytics reports; that key is never stored.

Why does App Store Connect say «not enough data»?

App Analytics hides small numbers to protect privacy, so small apps and new countries often show nothing.
AppWhy also reads Apple's Sales and Trends reports, which count every download and sale, on the same timeline.

Is AppWhy a RevenueCat alternative?

No, it works with RevenueCat. Keep RevenueCat for purchases and subscriptions.
AppWhy puts its numbers into the whole funnel, from store page to renewal, so you can see why they moved.

Can I ask about my numbers from Claude or ChatGPT?

Yes. AppWhy has a remote MCP server and a REST API.
Tokens are named, read-only and scoped, and you can revoke any of them at any time.

Where is my data stored?

In the EU: AppWhy's database runs in Stockholm, Sweden, and keys are encrypted in Supabase Vault.
You can export everything or delete your workspace at any time.

Know what changed
overnight,
and why.

Join the beta and connect your first app
in minutes.

We only email you about your invite. Privacy