Skip to content

RevenueCat analytics · Planned

RevenueCat analytics,with the evidence attached.

RevenueCat is planned and is not available in the current beta. This page describes the intended read-only integration: revenue, subscriptions, trials, and conversions alongside reviews and competitor changes. No release date is announced.

RevenueCat shows the number.Add the surrounding context.

A trial-to-paid change raises questions beyond the subscription chart. Was there a release that week? Did pricing complaints rise? Did a competitor change its price? The planned integration would bring that surrounding evidence into the investigation.

Dashboards that sum everything also mislead quietly: active subscriptions are a stock, not a flow, and adding them across days produces a number that means nothing. Today's trial-to-paid ratio mixes cohorts that have not matured.

Monetization analytics should keep scope exact and put the number next to evidence that may help explain it.

The planned read-only connectionto a finding with context.

  1. 01

    Verify the binding

    Planned: verify the RevenueCat project and app binding before reading supported metrics through an authorized, server-side connection.

  2. 02

    Read a small, exact set

    Revenue, active subscriptions, trials, and paid conversions, with currency, timezone, and window recorded on every observation.

  3. 03

    Keep scope honest

    Project totals and app-level series stay separate. Stocks are never summed across days. Trial-to-paid is computed from matched mature cohorts.

  4. 04

    Detect the change

    A trial conversion drop or a revenue movement is detected against a baseline window with a minimum sample.

  5. 05

    Explain with evidence

    The finding on Today cites the release, the review theme, or the competitor price change that preceded it.

  6. 06

    Fail closed

    A failed sync is shown as failed with the last good read. It is never shown as zero revenue or a disconnected integration.

What RevenueCat analyticsis intended to include.

  • Revenue, active subscriptions, trials, and paid conversions with exact project or app scope
  • Trial conversion drops and revenue movements ranked on Today with evidence
  • Planned monetization context next to releases, review themes, and competitor changes; timing alone would not prove a cause
  • Source labels separating connected first-party metrics from competitor estimates
  • A connection card showing exactly what is read, the last sync, and usage against RevenueCat's limits
  • Read-only. Nothing is ever written back

What Appfox refusesto do with revenue data.

  • Sum stocks like active subscriptions across days.
  • Report today's trial-to-paid ratio as a conversion rate before cohorts mature.
  • Show a failed read as zero, empty, or disconnected.
  • Write anything to RevenueCat, or create provider accounts on your behalf.

RevenueCat analytics,common questions.

Something else? Email us from the contact page and a person will answer.

Is the RevenueCat integration read-only?
The planned integration is intended to be read-only, with credentials kept server-side. RevenueCat is not available in the current beta.
Which plans include RevenueCat?
The proposed pricing places RevenueCat on Indie and above, but the integration is not available in the beta. Final availability and plan limits may change.
Does Appfox replace the RevenueCat dashboard?
No. RevenueCat would remain the source of truth for subscription data. The planned Appfox connection would put a supported subset alongside reviews, releases, and competitors.
What if I do not use RevenueCat?
Appfox is useful with public store data alone, and accounts without a connection get a clearly labeled public-data experience. App Store Connect and Google Play Console integrations are planned.

Private beta

Put your revenue next to its reasons.

RevenueCat is planned. Request access to the current beta to research ideas and track public store data.

Invitations are sent by email.