Revenue tracking for app developers

Updated 2026-08-04

Mobile revenue is genuinely harder to see than web revenue, and it's not your tooling's fault.

Why Apple's numbers work the way they do

Reports, not an API. Revenue comes from Sales and Trends — gzipped TSV files generated on Apple's schedule, typically a day behind. There is no live "what's my revenue right now" endpoint for anyone.

Proceeds, not gross. Apple reports what you'll be paid, already net of its 15% or 30% commission. Stripe reports gross with fees itemised separately.

Apple's calendar. Fiscal periods, not calendar months.

Signed JWTs. Authentication uses an ES256-signed token built from a .p8 key, not a bearer token. See how to create an App Store Connect API key.

Every one of these makes mobile revenue harder to fold into a combined figure — and explains why so few tools do it well.

The commission cliff

The difference between Apple's tiers is large enough to change your business:

You keep on $49.99
Small Business Program (15%) $42.49
Standard (30%) $34.99

If you earned under $1M last year and haven't enrolled in the Small Business Program, do it today. It is the highest-value form available to a small developer. Commission calculator.

Note also that auto-renewable subscriptions drop to 15% after a subscriber's first year regardless of enrolment — so a mature subscription base is worth more per user than a new one, beyond the obvious retention effect.

Adding a web product

The moment you also bill on the web, you have the reconciliation problem:

  1. Normalise the fee basis. Apple's proceeds are post-commission; Stripe's volume is pre-fee. Compare gross to gross or net to net, never mixed.
  2. Normalise intervals. Annual iOS subscriptions divide by twelve, same as anywhere. How.
  3. Accept different latencies. Your combined figure is only as fresh as your slowest source, and that's Apple.

Detail: Stripe + App Store.

What FRGMNT currently does

Plainly, because this page's readers are exactly the people who need to know:

The App Store integration authenticates and validates credentials and signs the required ES256 JWT. It does not yet report sales — the Sales and Trends pipeline is still in development. The app shows this status rather than a misleading zero.

Stripe, Lemon Squeezy, Gumroad and PayPal work fully today.

So if Apple is the only platform you need visible, use Appfigures or RevenueCat instead. If Apple is one slice and the others are web or marketplace revenue, FRGMNT covers those now.

What to track meanwhile

Frequently asked

Why is App Store revenue harder to track than Stripe?

Apple provides revenue through Sales and Trends report files on a delay rather than a live API, and reports proceeds already net of commission. Stripe provides a live REST API reporting gross with fees itemised.

How do I combine App Store and web subscription revenue?

Normalise the fee basis first — Apple reports post-commission proceeds while Stripe reports gross — then normalise billing intervals, then sum. Adding the headline figures compares two different things.

Read next