Integration Guides
Zellify handles the funnel experience and checkout, but it does not grant access or entitlements to your end-users. That is your responsibility.
After a visitor completes a purchase in your Zellify funnel, you need a way to:
- Create their account in your system
- Grant them the entitlements they paid for
- Route them to your product (mobile app, web app, or both)
These guides cover the most common ways to solve this, depending on your product type and tech stack.
The Linking Key: app_user_id#
Every integration scenario relies on one concept: the app_user_id.
Zellify generates a unique app_user_id when a funnel session starts. This identifier is available throughout the entire funnel journey and is attached at checkout to:
This same app_user_id is also available before payment — in the Registration Webhook payload — and on the success page through the Deep Link Button component, which can interpolate it into any URL — whether that is a mobile deeplink or a web redirect.
The app_user_id is what connects the funnel session, payment event, and the user in your system. It is the bridge between Zellify, your payment provider, and your product.
The Deep Link Button#
The Deep Link Button is a funnel component designed for success pages (or any post-payment page). It renders a button that links the end-user to your product.
In the component's configuration panel, you can build a URL that interpolates app_user_id and email — the two values most commonly needed to identify the user on the other side.
This works for:
- Mobile deeplinks — route users to your iOS/Android app via a deeplink URL (compatible with Adjust, AppsFlyer, and similar attribution tools)
- Web URLs — redirect users to your web signup page, dashboard, or any other web destination
Choose Your Guide#
| Guide | You have... |
|---|---|
| Mobile App with RevenueCat | A mobile app using RevenueCat for entitlement management |
| Mobile App with Custom Backend | A mobile app with your own backend handling entitlements |
| Web App with Signup Page | A web product where users need to create an account after purchase |
| Using Existing Webhooks | An existing Stripe/Paddle webhook setup that provisions accounts |
| Early Account Creation | A need to create user accounts before payment, then activate on purchase |
| Custom Registration Component | A need to call your own backend API from the success page to register users with custom logic |
| Free Funnel with Deep Link | A funnel with no paywall — onboarding only, then route users to your product |