Success step
The Success step confirms the purchase and points people to your app: store links, deep links, confirmation messaging, and an optional QR code for desktop-to-mobile handoff.
What to include
- Headline and subheadline — thank them and confirm the order
- Confirmation text — optional extra reassurance (for example "Check your email for access instructions")
- Primary button — “Open App”, “Download”, etc.
- Button URL / App Store link — store listing or download page
- Deep link (mobile) — mobile URI scheme (for example
myapp://welcome) to open the app directly - Show QR code — optional; allows desktop buyers to scan with their phone and download the app immediately
OneLink priority
When AppsFlyer OneLink is enabled in funnel settings, the Open App button and QR code use OneLink first. The button URL and deep link act as fallback destinations.
Referral prompt
Optional invite a friend block at the bottom of the success screen:
- Open the Success step in the editor.
- Under Referral, turn on Show "invite a friend" referral prompt.
- Set headline, optional subheadline, share text, optional share URL, and button text.
Tapping the button opens the device share sheet (or copies text) so happy customers can spread the word. If share URL is empty, the step falls back to your main app button or deep link.
Web-to-app
This step closes the loop from web ad → pay → app. Align the copy with what happens inside the app (onboarding, restore purchase, login) so users aren’t confused.
In Funnel Settings → Web-to-App Access, choose how access is handled:
- Managed Access — web2app creates a purchase token and short access code, listens to Stripe/Paddle webhooks, and exposes app endpoints for claim/access.
- Webhook Relay — your backend receives signed purchase and claim events and owns app access.
- Attribution Only — web2app only builds AppsFlyer OneLink attribution/deferred deep links.
When AppsFlyer OneLink is enabled, the success button uses OneLink with deep_link_value=purchase_success, deep_link_sub1 as the purchase token, and deep_link_sub2 as the access code. External payments for digital content can depend on Apple/Google country, category, and entitlement rules; review the current App Store and Google Play requirements before launch.