Editors sell by showing the result: a before-and-after in Reels, a template in TikTok, a filter in a creator's post. Every one of those taps starts inside an app's own browser.
Reels and TikTok demos · creator templates · UGC · trend-driven spikes
Attention on a viral demo lasts hours. Taps lost during the spike do not come back later, and no retargeting recovers that moment.
Nobody copies your link into Safari after seeing a filter. If the handoff fails inside the feed, the install does not happen.
A template link gets reshared into DMs and other apps — each with its own browser, each needing its own route out.
A template link forwarded into DMs, then into another app, passes through several embedded browsers on its way. Each one needs its own route out, and you cannot know in advance which it will be.
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. The link detects where the tap came from and takes the route that works there — you publish the same address everywhere.
Yes, with a deep link: people who already have the app land on that template, everyone else goes to the store.
Yes. Clicks split by platform and source app, plus a delivery rate showing how many taps actually left the in-app browser.
Yes, with a deep link. People who already have the app land on that template; everyone else goes to the store first.
The page is static and the routing runs in the browser, so a spike costs nothing on our side.
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.