App install campaigns are fine — Meta opens the store natively there. Traffic, engagement and conversion campaigns are not: the tap lands in Facebook's own browser, and the store link can end on an empty screen. The click is billed either way.
Traffic · Engagement · Conversions · Lead ads · anything with a URL
App install and Advantage+ App campaigns open the store natively, straight from the Install button. Every other objective opens a browser first — and that browser is the problem.
A raw App Store URL is refused in a traffic campaign: Meta answers that app URLs belong to the app install objective. So you put a landing page or an attribution link in the ad, the chain gets longer, and the last step stays exactly the same.
Facebook's in-app browser stopped identifying itself in the User-Agent. To your analytics those sessions look like plain Safari, so the loss hides inside your organic numbers.
Meta counts the click when the browser opens, not when the store does. A campaign that loses part of its taps at the handoff looks like a campaign with a weak landing page — the numbers never point at routing.
Of 180 taps we measured from Facebook, 81 per cent reached the store. The rest ended on the fallback button — 35 stalled, 17 recovered — this is where the system asks for confirmation. 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.
Everything that opens a link: traffic, engagement, conversions and lead campaigns, plus any W2A funnel behind them. App install campaigns are safe, because the store opens natively from the Install button.
No. If your ads run on an attribution link, that link stays the destination and keeps measuring the tap exactly as it does now. We do not rewrite your parameters.
No. You swap the destination URL for a GoToApp link. Creatives, audiences, budgets and reporting stay untouched.
Across 606 measured taps our Facebook traffic delivered 81 per cent to the store, and another 17 taps arrived only because the person pressed the fallback button. Instagram, over the same period, delivered 99 per cent.
Yes. Create a link, put it in a post or a comment, and open it from the Facebook app on your phone. The dashboard will show whether that tap left the in-app browser.
Longer read: Why Facebook ads send people to a blank App Store page.
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.