Skip to main content

I'm building a web to app funnel that transitions users from my web app to my iOS app, and I'm running into a challenge with purchase synchronization. Currently, I have two separate RevenueCat projects:

  • Web Purchases: Managed under RevenueCat Billing with its own API key.
  • iOS App: Managed under RevenueCat iOS with a separate API key.

When a user completes a purchase on the web, I want to ensure that once they transition to the iOS app, their entitlements (or purchase status) are correctly recognized and loaded.

My Questions:

  1. Is it possible to connect or sync the purchase data between these two RevenueCat projects?

    • If so, what’s the recommended approach to ensure that a web purchase reflects properly in the iOS app?
  2. Are there best practices or workarounds for handling separate API keys and project configurations when implementing a web-to-app purchase funnel?

    • For example, can I share user identifiers or purchase tokens between the two projects?
  3. Has anyone implemented a similar setup?

    • I'd appreciate any insights or detailed explanations on how you handled the transition from a web purchase to iOS entitlement recognition.
  4. Is there any tutorial on this?

Hi ​@viktor-346507868-90,

I’m not certain how far into your building process you are, but it would be much simpler to share purchase data for users if these two apps were within the same RevenueCat project. If these were in the same project, sharing subscriptions would only require authenticating users with the same custom id in both your web app and your mobile app. We have some more information about identifying customers for cross-platform access here in our documentation: https://www.revenuecat.com/docs/web/web-billing#identifying-customers


Reply