# Docs

- [Introduction](/docs): One shared core, three native SDKs for subscriptions, entitlements, and credits.
- Getting Started
  - [Installation](/docs/getting-started/installation): Add the Rovenue SDK to your React Native, iOS, or Android app in three steps.
  - [Quick Start](/docs/getting-started/quickstart): Configure the SDK, check an entitlement, fetch offerings, make a purchase, and identify a logged-in user — end to end in one page.
  - [Core Concepts](/docs/getting-started/core-concepts): The mental model behind the Rovenue SDK — two IDs, cache-first reads, the change stream, and how purchases flow.
- Guides
  - [Configuring the SDK](/docs/guides/configuring): Initialize the Rovenue SDK once at startup before making any other calls.
  - [Identifying Users](/docs/guides/identifying-users): Understand the two-identifier model and how to attach your backend user ID to the current install.
  - [Checking Entitlements](/docs/guides/entitlements): Read a user's active entitlements and refresh them from the server.
  - [Processing Purchases](/docs/guides/processing-purchases): Use the SDK to fetch offerings and drive the purchase flow end-to-end.
  - [Production & Sandbox](/docs/guides/environments): How Rovenue separates test purchases from real revenue — per-transaction environments, the dashboard toggle, and what stays production-only.
  - [Placements](/docs/guides/placements): Resolve a placement to a native funnel, run A/B tests, and track views — without shipping an app update.
  - [Experiments](/docs/guides/experiments): How Rovenue decides an A/B test's winner — the stopping rule, its four gates, and what it does and does not guarantee.
  - [Virtual Currencies](/docs/guides/credits): Read virtual-currency balances in your app and understand how granting and spending work server-side.
  - [Reacting to Changes](/docs/guides/reacting-to-changes): Subscribe to real-time SDK events for entitlement, identity, and credit updates.
  - [App Lifecycle](/docs/guides/app-lifecycle): Wire up foreground/background signals so the SDK can manage polling and background work.
  - [Identity Context & Consent](/docs/guides/identity-consent): Understand which PII fields are forwarded, how they are hashed, and where consent responsibility lies.
  - [Audit Proof Bundle](/docs/guides/audit-proof): Export a per-project audit hash chain and verify it offline, running none of Rovenue's server code — and know exactly what that does and does not prove.
  - [Data Retention Policies](/docs/guides/retention-policies): How long each kind of data is actually kept on each plan, which tables age out and how a project's window is resolved, and what stays until a project is deleted.
  - [Self-Service DSAR API](/docs/guides/dsar): Let your own backend fulfil GDPR/KVKK subject-access and erasure requests for your end users, without a support ticket to Rovenue — four secret-key endpoints, what each one actually does, and what it doesn't.
- Funnels
  - [Funnels](/docs/funnels): One product, two targets — build a funnel once, then serve it on the web or natively inside your app.
  - [Targets](/docs/funnels/targets): A funnel is built for one target — web or native — and each target forbids what it cannot serve.
  - [Publishing](/docs/funnels/publishing): What a funnel is checked for before it goes live, which findings block a publish and which only warn, and what visitors see while you keep editing.
  - Web
    - [Hosting & Embedding](/docs/funnels/web/hosting): Where a published web funnel runs — its slug, your own domain, and what a page that embeds it can hear.
    - [Checkout](/docs/funnels/web/checkout): How a web funnel sells — the checkout action on its own screen, the Stripe gate on publish, and what the runner and the server do when the visitor pays.
    - [Claiming the Result](/docs/funnels/web/claiming-results): How what a visitor did on a web funnel reaches your app — the claim token, the four ways an install finds it, and exactly which fields you get back.
  - Native
    - [The Native Path](/docs/funnels/native): How a placement serves a native funnel to the device — the envelope, the variant draw, and what the device caches.
    - [Show a Funnel](/docs/funnels/native/show-a-funnel): Resolve a placement to a native funnel and host it — getFunnel into RovenueFunnelView on every SDK.
    - [Purchases & Effects](/docs/funnels/native/purchases-and-effects): What a native funnel session yields — effects, the store purchase path, attributes, dismissal, and resume.
    - [Offline Fallback](/docs/funnels/native/offline-fallback): Bundle resolved placements with the app so a first launch with no network still opens its funnel.
  - [Conversion](/docs/funnels/conversion): Changing a funnel's target — preview what the other target cannot carry, then convert.
  - [Events & Analytics](/docs/funnels/events-and-analytics): Device and web funnel events, the one outbox-to-ClickHouse pipeline, the Sessions tab, and the funnel webhooks.
- Platforms
  - [React Native](/docs/platforms/react-native): Install and wire the Rovenue SDK in an Expo or bare React Native app.
  - [iOS (Swift)](/docs/platforms/ios-swift): Install and wire the Rovenue SDK in a Swift app.
  - [Android (Kotlin)](/docs/platforms/android-kotlin): Install and wire the Rovenue SDK in an Android/Kotlin app.
  - [Flutter](/docs/platforms/flutter): Install and wire the Rovenue SDK in a Flutter app.
  - [Web](/docs/platforms/web): Read entitlements, record experiment exposures and start Stripe checkouts from a browser.
- Reference
  - [SDK API Reference](/docs/reference/sdk-reference): Full, generated API reference documentation for every Rovenue SDK.
  - [Methods](/docs/reference/methods): Every Rovenue SDK method, grouped by capability.
  - [Types](/docs/reference/types): Data types returned by the Rovenue SDK.
  - [Errors](/docs/reference/errors): The RovenueError family and how each surfaces per platform.
  - [API Errors](/docs/reference/api-errors): Every error code the API can return, documented by its exact wire value.
  - [API Explorer](/docs/reference/api-explorer): Browse every /v1 endpoint against apps/api/openapi/openapi.json and try requests against your own deployment.
- Resources
  - [Versioning](/docs/resources/versioning): How the Rovenue SDKs are versioned.
  - [Migrating from RevenueCat](/docs/resources/migrating-from-revenuecat): Concept mapping and step-by-step history import from RevenueCat to Rovenue.
  - [Migrating from Adapty](/docs/resources/migrating-from-adapty): Concept mapping and step-by-step history import from Adapty to Rovenue.
  - [Using Rovenue with AI & LLMs](/docs/resources/using-with-ai): Machine-readable docs endpoints, copy-paste context primers, and tips for integrating Rovenue with coding assistants and AI agents.
- Integrations
  - [Meta Conversions API (CAPI)](/docs/integrations/meta-capi): Forward Rovenue subscription and revenue events to Meta's server-side Conversions API for reliable attribution without client-side pixels.
  - [TikTok Events API](/docs/integrations/tiktok-events): Forward Rovenue subscription and revenue events to TikTok's server-side Events API for reliable attribution without client-side pixels.
  - [Amplitude](/docs/integrations/amplitude): Forward Rovenue revenue and subscription-lifecycle events to Amplitude for funnel, retention, and cohort analysis.
  - [Mixpanel](/docs/integrations/mixpanel): Forward Rovenue revenue and subscription-lifecycle events to Mixpanel for cohort analysis, retention, and behavioral analytics.
  - [AppsFlyer](/docs/integrations/appsflyer): Forward Rovenue revenue and subscription-lifecycle events to AppsFlyer's server-to-server (S2S) in-app-event API for mobile attribution.
  - [Adjust](/docs/integrations/adjust): Forward Rovenue revenue and subscription-lifecycle events to Adjust's server-to-server (S2S) event API using your own Adjust event tokens.
  - [Slack](/docs/integrations/slack): Post real-time Rovenue revenue, subscription, funnel-session, and credit-ledger events to a Slack channel via an incoming webhook.
  - [Firebase / GA4](/docs/integrations/firebase-ga4): Forward Rovenue revenue and subscription-lifecycle events to a Firebase app stream via the Google Analytics 4 Measurement Protocol.
  - [Braze](/docs/integrations/braze): Sync Rovenue revenue and subscription-lifecycle events into Braze for customer engagement and lifecycle messaging.
  - [OneSignal](/docs/integrations/onesignal): Sync Rovenue revenue and subscription-lifecycle events into OneSignal as custom events, so you can trigger Journeys and target push by subscription state.
  - [Iterable](/docs/integrations/iterable): Sync Rovenue revenue and subscription-lifecycle events into Iterable as purchases and custom events, so you can trigger cross-channel campaigns on subscription behavior.
  - [Airbridge](/docs/integrations/airbridge): Sync Rovenue revenue and subscription-lifecycle events into Airbridge as in-app events, so you can attribute revenue back to ad campaigns.
  - [Singular](/docs/integrations/singular): Forward Rovenue revenue and subscription-lifecycle events into Singular as Server-to-Server (S2S) events, so you can attribute revenue back to ad campaigns.
  - [Discord](/docs/integrations/discord): Post real-time Rovenue revenue, subscription, funnel-session, and credit-ledger events to a Discord channel via an incoming webhook.
  - [Outbound Webhooks](/docs/integrations/outbound-webhooks): Receive Rovenue subscription, revenue, funnel, and credit-ledger events on your own HTTPS endpoint — payload shape, signature verification, retries, and idempotency.
  - [Subscriber Identity Attributes](/docs/integrations/subscriber-identity-attributes): Reserved subscriber attributes for third-party vendor ids (AppsFlyer, Adjust, Firebase, Mixpanel, Amplitude, OneSignal, Braze, Iterable, Airbridge, Singular) used to resolve identity across outbound integrations.