Your onboarding starts on the web — a calculator, a rate check, a lead form — and ends with Download. Inside an in-app browser both parts are at risk: the store handoff fails, and so do the things that need real cookies.
Web onboarding · paid social · comparison pages · referral programmes
You cannot always send people straight to the store — disclosures, eligibility and KYC live on your pages. That makes the last-step handoff unavoidable.
Payments, cookies and web analytics behave differently there. Sending the funnel into a real browser fixes several problems at once, not just one.
In this category a single lost install is expensive. The delivery rate is worth measuring rather than assuming.
You do not get to rebuild onboarding to dodge a browser quirk — legal signed off on this flow. Changing one destination URL is a change you can actually ship this week.
Delivery depends on which app the link opens in, and the spread is wide. These are our own numbers, not an industry estimate. Sample: 606 taps through our own links, 3–5 August 2026. Every link reports back when a tap fails to leave the in-app browser, so these are counted, not modelled.
| Source | Reached the store | Detail |
|---|---|---|
| 99% | 3 taps stalled, 2 of them recovered by pressing the button | |
| 81% | 35 stalled, 17 recovered — this is where the system asks for confirmation | |
| TikTok | 86% | small sample, but the pattern matches Facebook |
| Plain browser | 100% | nothing to escape from, the store opens directly |
It reads where the tap came from and takes the route that survives there: the external browser out of Instagram and Threads, the store's own scheme where that is what works, an immediate button where the system asks for confirmation. If everything is blocked, the tap still ends on a visible button instead of a blank screen.
No SDK and no changes in the app. You swap one address for another.
An attribution link can be the destination. We hand the tap over and leave your parameters alone.
Each link reports when a tap failed to leave the in-app browser, so the dashboard shows delivery, not just clicks.
Yes, once you verify the domain. Then the tap opens your funnel in the real browser, where payments, cookies and analytics work normally.
You upload one static file to prove the domain is yours. Without that we only accept store and attribution links — otherwise the service would be an open redirector.
No. If you run on an MMP link, it stays the destination and keeps its parameters.
Yes, after verifying the domain. Here that is often the better route: in a real browser your payments, cookies and analytics all behave normally.
One static file at a known path proves the domain is yours. Without it we accept only store and attribution links — otherwise the service would be an open redirector.
Free while you try it: up to three apps, unlimited links under each, full routing and per-source stats. The paid plan buys a shorter address.