DOCSEARCHbyAlgolia
Submit Docs

RevenueCat Documentation

website·Indexed 42 days ago

https://www.revenuecat.com/docs/

A platform for developers to build, analyze, and grow in-app purchases and subscriptions on iOS, Android, and other platforms. Documentation covers SDK installation for Flutter, React Native, Unity, Expo, Kotlin Multiplatform, and Web, as well as product setup for Apple, Google Play, Amazon, Stripe, Paddle, and Roku.

Tokens
371.4K
Snippets
747
Records
2.4K
Agent score
74%

What's inside RevenueCat

  1. Overview of the RevenueCat Stripe Dashboard App

    The RevenueCat App for Stripe integrates RevenueCat's cross-platform SDK and subscription data directly into the Stripe Dashboard. This allows users to view RevenueCat project metrics, customer metadata (app user ID, SDK version, locale, timestamps), and transaction events from Stripe, Apple App Store, Google Play Store, and Amazon Appstore in a single view. Note that RevenueCat data within Stripe is read-only and cannot be used for filtering within the Stripe interface.

  2. Overview of Sales Tax and VAT in RevenueCat Billing

    RevenueCat Billing allows developers to collect sales tax and VAT for web subscriptions and purchases. Unlike mobile app stores, web sales require manual compliance based on business location, customer jurisdiction, product category, and revenue thresholds.

    Key behaviors across all tax providers:

    • B2C Only: Only supports consumer products. It does not collect customer tax IDs or issue B2B reverse charge VAT invoices.
    • Pricing Logic: US and Canada use tax-exclusive pricing (tax added to price); the rest of the world uses tax-inclusive pricing (tax included in price).
    • Reporting: Tax reports and analytics are managed within the chosen tax provider's dashboard, not in RevenueCat.
    • Reversals: Tax reversals are created for refunds, but not for disputes or chargebacks.

  3. Overview of Targeting by Placement

    Targeting by Placement allows you to define specific paywall locations (Placements) within your app to serve unique Offerings to customers based on their journey. For example, you can serve different offers at the end of onboarding (onboarding_end), when a user hits a feature gate (feature_gate), or during a specific sale (sale_offer).

  4. Overview of RevenueCat Ad Rewards

    RevenueCat allows you to grant in-app currency or temporary entitlements to users who complete AdMob rewarded or rewarded interstitial ads. To prevent spoofing, RevenueCat uses AdMob Server-Side Verification (SSV) to verify rewards server-side before granting them. A single ad unit can grant one in-app currency reward and multiple entitlement rewards simultaneously.

  5. Overview of RevenueCat Customer Center

    Customer Center is a self-service UI that can be integrated into an app to allow customers to manage their subscriptions independently. It is designed to reduce support tickets and prevent churn using features like pre-emptive promotional offers and exit feedback prompts. Customer Center is available exclusively on Pro and Enterprise plans.

  6. Overview of RevenueCat Web

    RevenueCat Web allows developers to sell subscriptions and purchases on the web while unlocking the same entitlements used on mobile platforms. It decouples the billing engine (which handles products, renewals, taxes, and emails) from the integration path (how the user interacts with the purchase flow).

  7. Overview of Airbridge integration capabilities

    The Airbridge integration allows developers to attribute subscription revenue and lifecycle events to specific Airbridge campaigns. It enables streaming of trial conversions, renewals, and cancellations directly from RevenueCat (without requiring the app to be in the foreground) and supports long-tail revenue measurement.

    Integration Support:

    • Revenue Support: Yes
    • Negative Revenue: No
    • Sandbox Events: Yes
    • Transfer Events: No
    • Optional Event Types: non_subscription_purchase_event, expiration_event, billing_issue_event, product_change_event.

  8. Overview of RevenueCat Mixpanel Integration

    The RevenueCat Mixpanel integration allows developers to track app events and revenue, formulate data models based on user interactions, and use interactive reports to analyze conversion. The integration supports revenue tracking, negative revenue, customer attributes, and optional event types. Sandbox events require a token to be sent.

  9. Overview of RevenueCat and Customer.io integration

    The RevenueCat integration with Customer.io allows developers to automate personalized user journeys based on subscription data. Key capabilities include creating onboarding flows for new subscribers and sending win-back notifications to churned users. The integration supports revenue tracking (converted to USD), customer attributes, and sandbox events (requiring an API key). It does not support transfer events.

  10. Overview of RevenueCat Airship Integration

    The RevenueCat Airship integration allows developers to send custom events to Airship based on purchase behavior. These events can be used to trigger personalized Airship Journeys and Automations, such as sending reminders when a trial is about to expire or notifying users of billing issues.

    Key integration capabilities:

    • Supports recording revenue and negative revenue.
    • Sends customer attributes.
    • Supports sandbox events (requires Token and App key).
    • Does NOT send transfer events.

  11. Overview of RevenueCat Test Store

    RevenueCat Test Store is a built-in testing environment that allows developers to simulate in-app purchases and subscriptions without requiring platform-specific store setup (like App Store Connect or Google Play Console). Test purchases behave like real transactions: they update CustomerInfo, trigger entitlements, and appear in the RevenueCat dashboard as sandbox data.

  12. Overview of RevenueCat Events and Integrations

    RevenueCat events provide near real-time notifications of changes to a customer's subscription (e.g., trial conversions, renewals, cancellations). These events are detected server-side by connecting directly to app stores, ensuring they are triggered even when the app is inactive. Events can be automatically forwarded to third-party tools and attribution networks to maintain consistent data across systems.