DOCS / 01

Make revfox useful.

Connect your apps and stores, map subscriptions to benefits, then use verified data across customers, webhooks, and revenue analytics.

01

Projects and access

A project groups one app's store configuration, products, customers, webhooks, and analytics.

  1. Log in to the revfox panel.
  2. Create a project from the project switcher.
  3. Use a separate project for each app or environment that needs isolated data.

Share a project

Add multiple users to the same project and choose the smallest role each person needs.

  • read can view project configuration, customers, events, and analytics.
  • write can also change project settings and operational data.
02

Store credentials

Credentials allow revfox to verify purchase evidence against trusted store APIs from your server.

App Store

Add the Apple key details required for transaction and subscription checks, then scope them to the project that owns the app.

Play Store

Add a Google Play service account with access to the Android app and subscription purchase APIs.

Credential hygiene

Use store accounts with only the permissions revfox needs and keep production credentials out of source control.

03

Products and benefits

Product mapping turns store-specific purchase IDs into packages and benefits your application understands.

  1. Create or import the App Store and Google Play product IDs.
  2. Group equivalent products into packages such as Monthly or Annual.
  3. Attach benefits that represent the access each package unlocks.
04

Webhooks

Webhooks send normalized subscription lifecycle events from revfox to your backend.

  1. Add your backend endpoint from the project's integrations page.
  2. Select events such as purchases, renewals, expirations, and refunds.
  3. Monitor delivery history and retry failures after correcting the endpoint.
05

Customer timelines

Customer profiles connect verified transactions to current subscription state and entitlement history.

  • Review purchases, renewals, expirations, and refunds in sequence.
  • Compare sandbox and production events during integration testing.
  • Use the timeline to investigate entitlement and ownership changes.
06

Revenue analytics

The dashboard summarizes verified store activity into revenue, MRR, active subscribers, trials, customers, refunds, taxes, and commissions.

Filter out sandbox activity before using the numbers for production decisions, and compare chart movement with the underlying customer and transaction records.

Need deployment help?

Start with the Ubuntu install guide.

Open install guide