EdTech funnels are long by design: a test, a preview, a plan. All of it renders fine inside an in-app browser. The store handoff at the end is the part that breaks.
Placement tests · lesson previews · parent funnels · school campaigns
The further someone walks before the store link, the more expensive their loss at the final step.
Parents tap from Facebook, students from TikTok and Instagram. The routing that works differs by app — the link decides, not you.
Back-to-school spend is concentrated in weeks. A leak you cannot see is a leak you cannot fix in time.
The same campaign reaches Facebook on one side and TikTok on the other. The routing that works differs between them, and no hardcoded redirect covers both at once.
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.
No, the test itself works fine. Only the store button at the end needs the GoToApp link.
Yes — one per campaign or placement, all under the same app, each with its own stats by source app.
No SDK and no code in the app. You change the URL behind the button.
Not technically, but it is worth it: separate links give separate numbers, and the two audiences arrive from different apps.
Yes, it is an ordinary https link. Put it wherever the store link goes now.
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.