Chapter 5: User identity: connecting the web purchaser to the right app account
Connecting the person making the purchase with the person using your app is (unsurprisingly) critical to any acquisition campaign. With web-to-app, this is trickier because the web purchase and app access happen in different environments — meaning you need to handoff the web purchaser identity to RevenueCat, so that the payee identity is connected to the customer identity who opens the app.
Without this handoff, the app purchase may not unlock, revenue may remain attached to an anonymous customer, and purchase-to-app redemption becomes unreliable.
These three handoff methods are equally effective — choose one based on what you know about the visitor before checkout:
Whichever identity path you use, test that the purchase lands on the intended RevenueCat customer and that the app unlocks the correct entitlement. For campaign measurement, purchase-to-app redemption is the key handoff metric.
RevenueCat saves funnel responses (from choice and text inputs, referenced on later screens through variables such as {{ input.goal }}) as customer attributes, viewable in the Responses view. Breaking down funnel analytics by response value isn't available just yet (this feature is coming soon), so if you currently need that kind of segment for reporting, represent it with a stable URL parameter instead, or send funnel events to product analytics.