OOmnistu

Blog / Mobile App Development

Mobile App Development

Deferred deep links still work; the tracking around them changed

Routing new users to what they tapped survives ATT - what changed is measurement: Apple's prompt, its attribution frameworks, and rebuilding reporting around aggregate answers.

OOmnistu
Reviewed 2026-11-19 · 3 min read

A user taps your ad, installs the app, opens it - and lands on the generic home screen instead of the product they tapped. Deferred deep linking fixes that (carry the destination through the install and open it on first launch), and it used to be trivially measurable. Apple's App Tracking Transparency framework changed the measurement half: the linking still works, but the attribution pipeline around it now runs on privacy-preserving rails. Planning an app in 2026 means knowing which half you are building.

Deferred deep links still work - they are just links

Mechanically nothing about ATT blocks the feature itself. A deferred deep link is a parameterised URL (typically via a linking provider or your own referral parameter) that survives the trip through the store: click, install, first open, match, route. Universal links on iOS and Android App Links still open installed apps directly; carrying the destination through the install is the platform-specific part. On Android, the Play Install Referrer API hands your app the referrer URL of the installed package on first open, so your own campaign parameter survives the store trip on rails Google documents. On iOS, Apple's documented universal-link behavior stops at the install boundary: if the person has not installed your app, the system opens the URL in their default web browser and your website handles it. Carrying a campaign destination through an App Store install is something universal links do not do, so apps that need it rely on a linking provider's own click-to-first-open matching. Whether that matching counts as tracking under ATT depends on what is done with the data: delivering the destination inside your own app is a different case from linking it with other companies' data for advertising measurement, which is what ATT defines as tracking. And identifying a device or user from derived signals is prohibited outright: Apple's user-privacy page answers the fingerprinting question with a flat no, consent or not. What changed is not the routing - it is what you are allowed to learn and share about the user who arrived.

What ATT actually constrains

Apple's framework requires apps to obtain permission through the ATT prompt before tracking - linking user or device data collected from your app with data from other companies' apps, websites or offline properties for advertising or measurement, or sharing it with data brokers. If a user declines, you may not use the IDFA or equivalent identifiers for that cross-context measurement, and Apple's policies extend the spirit to fingerprinting-style workarounds. Many users decline; plan your measurement assuming the prompt answer is often no.

The privacy-preserving rails that replaced it

Apple's own answer is its ad attribution frameworks (SKAdNetwork and the newer AdAttributionKit, which interoperate): ad networks register with Apple, and conversion values and attribution postbacks come back through Apple's framework, aggregated rather than tied to device-level identifiers. You get campaign-level measurement without tracking individual users across companies. On Android, Google Play still offers the install referrer for first-party measurement, while its Privacy Sandbox initiative pushes similar privacy-preserving attribution APIs. Practically: you can still answer "did this campaign drive installs and signups" - you cannot build the old per-user, cross-app profile to do it.

What this means for your onboarding

The planning takeaway

Deferred deep links: build them, they are table stakes for paid acquisition UX. Cross-app user tracking: treat as opt-in and rare. Aggregate attribution: design for it as the default, because it is the default the platforms chose.

Sources

Prepared with AI assistance and reviewed before publication. ATT scope and the attribution frameworks are paraphrased from Apple's developer documentation checked on 19 November 2026. This article is information, not legal advice.