How web-to-app attribution works

The problem it solves

An app store sits between your web page and your app, and your page's UTM parameters do not reach the app on their own. A visitor can arrive on a landing page from an ad, tap "Get the app", install, and open the app, and the app has no built-in way to know which page or ad started it. Web-to-app attribution rebuilds that connection.

What the web page adds to the chain

From the click onward, a web-to-app journey is matched like any other click: the platform records it, the store opens, and the first app open is matched back. That sequence is told in full in how a tracking link carries a click to an install. The web leg adds two steps in front of it.

1. The visit is labelled. The visitor lands on your page with campaign details in the URL, usually as UTM parameters. At this point only the page knows where the visitor came from.
2. The button carries the label. The store button on the page is a tracking link, and the visit's campaign details are copied onto it before the tap. A web SDK can do the copying on each page load, so that nobody has to build one link per ad.

The second step is the one that is specific to the web. An ad that opens the store directly has one hop and one label. A web journey has two hops, ad to page and page to store, and the label has to be handed from the first to the second. If it is not, every install from the page is credited to the page as a whole and the ad behind it is lost.

The page also meets visitors an install ad never sees: people who already have the app. For them the same button should open the app, and the platform counts a deep link open with the page's campaign attached.

Where the match can fail

Three common things break the chain.

• A bare store link. If the button points straight at the store, no click is recorded and the install looks organic.
• Too much time. Every platform accepts a click only within a set period, the lookback window. A visitor who installs after it closes is not matched.
• A weak match. Some matches rest on an exact identifier passed through the store, and others on device details that are similar but not certain. The two kinds are compared in deterministic versus probabilistic matching. Web-to-app journeys lean on both, and what is available varies by device and by the user's settings.

What gets credited

A working setup credits more than the install. It also credits opens of the app by people who already had it and tapped your web button, and the in-app events that come afterwards. Airbridge describes its web-to-app attribution in those terms: installs, deep link opens and in-app events, and it includes the feature in the Core Plan.^[1]

What it does not credit is behaviour on the website before the click. A page view or a newsletter signup on the site is a web event, and measuring those is a separate feature on most platforms.

What to check first

Open your landing page on a phone, tap the store button, and look at the address it sends you to. If it goes directly to the store, start there: replace it with a tracking link. Then run one install from a test phone and confirm that the platform shows the page's campaign as the source. Once that works, measuring a landing page end to end covers which numbers to read and in what order.