AppsFlyer OneLink, honestly

OneLink is a good attribution product. The confusion starts when people expect it to fix a browser problem it was never designed to touch.

6 August 2026 by PAD team

What it does

A OneLink URL records the click, decides where to send the visitor based on platform and app presence, carries campaign data, and matches the eventual install back to the original tap through the AppsFlyer SDK inside your app.

That last part is the valuable one. Deferred deep linking, where someone installs from an ad and lands on the exact screen the ad promised, needs something running in the app at first launch, and this is it.

What it does not do

It does not change which browser the tap is running in. A OneLink URL tapped inside Instagram resolves inside Instagram's WebView, follows its redirects there, and ends at apps.apple.com, where Apple replies with the itms-appss:// scheme that the WebView cannot open.

The click is recorded accurately. The visitor still sees a blank page. You end up with a precise count of taps that reached nothing, which is arguably worse than not measuring, because the dashboard looks healthy.

Using both

These are complementary rather than competing. Point the escape at your OneLink URL instead of the raw store link, and the tap leaves the in-app browser first, then hits AppsFlyer in a real browser where its routing works as designed.

Attribution answers where installs came from. Routing decides whether there is an install to attribute. Neither replaces the other.

Cost and scale

OneLink is part of AppsFlyer's paid platform, priced on volume. For a small app sending a few hundred installs a month, the SDK integration and the cost are hard to justify if all you need is a link that reaches the store. For a portfolio spending real money on user acquisition, the deferred deep linking alone usually pays for itself.