Revenue analytics

Track MRR across your payment providers.

Bring recurring events from your providers together, normalize their prices and compare one MRR view across your portfolio.

Bring recurring revenue together Read the setup steps ↓
Recurring revenue30 days compared
MRR$4,286.00▲ 12.4% vs previous period
Monthly subscriptions$2,140
Annual ÷ 12$1,560
Weekly × 52 ÷ 12$586

328 subscriptions · USD display currency

Product example · illustrative data
THE PROBLEM

Does this sound familiar?

  • Providers describe recurring plans in different ways.
  • Annual, weekly and monthly prices are not directly comparable.
  • A total does not show whether recurring revenue is growing.

One recurring revenue picture across providers, apps and billing intervals.

THE SETUP

How to make it work.

  1. Connect your providers.

    Receive supported events from Stripe, Polar, Creem, App Store or Google Play. Keep sandbox activity separate from production workspace data.

  2. Collect recurring prices and intervals.

    The subscription events supply recurring amounts, currencies and billing intervals. Apple standard periods can be inferred from supported transaction data; Google Play uses the recurring price and base-plan interval from its API.

  3. Assign products to apps.

    In Manage products, assign each provider product to the app that sells it. Prices follow the product. The MRR view can then switch between one app and the whole portfolio.

  4. Choose a display currency.

    Select the currency used for combined dashboard totals. Original event amounts remain on their transactions and Telegram notifications. Missing exchange data is shown as unknown.

  5. Compare the same scope over time.

    Use the dashboard period selector. MRR compares today with the corresponding earlier date and applies the same exchange rates. Keep the app and source filters aligned for meaningful comparisons.

IN PRACTICE

What the recurring number includes.

Monthly normalization.

Monthly prices stay monthly, annual prices are divided by 12, weekly prices are annualized and divided by 12, and supported multi-month prices are divided by their number of months.

Trials and subscription states.

A free trial contributes zero MRR while remaining visible in the eligible subscription count. A successful conversion can replace it with recurring revenue.

Unknown stays unknown.

If neither the event nor reliable local evidence resolves a billing interval, the aggregate can show unknown instead of assuming a monthly plan.

Questions about this setup.

Can annual and monthly plans share an MRR total?

Yes. Supported intervals are normalized to a monthly value before aggregation.

Why might MRR show a dash?

The recurring price or interval may be unavailable, or the comparison may lack a valid earlier observation or exchange rate. A missing value stays unknown.

Do trials add MRR?

No. They contribute zero until a successful conversion, though the subscription can remain visible in the active count.

Can I compare a single app?

Yes. Select that app and source, then use the same scope for the period comparison.

PUT IT INTO PRACTICE

One recurring revenue picture across providers, apps and billing intervals.

Start in PushTheSales, then follow the setup for your provider.

Bring recurring revenue together