Success step

The Success step confirms the purchase and points people to your app: store links, deep links, optional QR code for easy phone install.

What to include

• Headline and subheadline — thank them and set expectations
• Primary button — “Open app”, “Download”, etc.
• Link URLs — App Store, Play Store, or a deep link into the installed app
• QR code — optional; useful for desktop-to-mobile handoff

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.