Mobile App Attribution in 2026: Install Tracking, Deeplinks, and Beyond

Mobile app attribution has changed dramatically since Apple's App Tracking Transparency framework effectively killed IDFA-based tracking for most users. In 2026, only about 25% of iOS users opt in to tracking, which means the old approach of matching advertising IDs across install and ad impression is no longer viable as a primary strategy.

This does not mean mobile attribution is dead. It means the industry has shifted to a combination of first-party data, probabilistic modeling, and deep integration between app and web experiences. This post covers the practical techniques that work today and how Gurulu implements them.

Install Tracking: $app_install and $first_open

Gurulu defines two canonical events for app installs. The $app_install event fires when the app is first downloaded and opened, capturing the install source, campaign parameters, and app version. The $first_open event fires on the first meaningful interaction after install, which may happen in the same session or days later.

On Android, the Google Install Referrer API provides deterministic attribution data -- you know exactly which ad or link drove the install because Google passes the referrer string through the Play Store. Gurulu's Android SDK automatically captures this data and attaches it to the $app_install event.

// iOS – track install and first open
gurulu.track('$app_install', { platform: 'ios', version: '2.1.0' });
gurulu.track('$first_open', { campaign: 'spring_sale', source: 'instagram' });

// Android – with Google Install Referrer
gurulu.track('$app_install', {
  platform: 'android',
  referrer: installReferrerData,
  version: '2.1.0'
});

Universal Links, App Links, and Deeplink Attribution

Deeplinks are URLs that open directly to a specific screen in your app rather than a web page. Universal Links (iOS) and App Links (Android) are the modern standard for deeplinks, replacing the older custom URL scheme approach. Gurulu auto-generates the Apple App Site Association (AASA) file and Android assetlinks.json file from your Settings page, so you do not need to manage these configurations manually.

When a user clicks a deeplink from a campaign, Gurulu captures the full URL with its UTM parameters and campaign identifiers. If the app is installed, the user lands directly on the target screen with attribution data attached to the session. If the app is not installed, the user goes to the App Store or Play Store, and Gurulu uses deferred deeplinks to attribute the install back to the original campaign.

Deferred deeplinks work by storing the campaign context server-side with a 48-hour TTL. When the user installs and opens the app, Gurulu matches them to the stored context using a combination of IP address, device characteristics, and timing. The match rate for deferred deeplinks is typically 60-75%, which is lower than direct deeplinks but significantly better than having no attribution at all.

Cross-Platform Identity Linking

The real power of modern mobile attribution comes from connecting the dots across web and app. A user might discover your product through a Google ad on desktop, visit your website, download the app on their phone, and make a purchase in the app a week later. Without cross-platform identity linking, you would attribute the purchase to organic app install and miss the web touchpoints entirely.

Gurulu solves this with its canonical identity system. When a user authenticates on any platform -- web, iOS, or Android -- the system links all their sessions into a unified profile. This means the attribution chain is preserved across devices: the initial Google ad click, the website visit, the app install, and the in-app purchase are all connected in a single journey.

Practical Implementation

Setting up mobile attribution in Gurulu follows three steps. First, integrate the iOS or Android SDK and configure the canonical events ($app_install, $first_open, and your conversion events). Second, set up Universal Links and App Links from the Settings page -- Gurulu generates the required configuration files automatically. Third, ensure your web and app share the same identify() calls so cross-platform identity linking works.

For campaign tracking, append standard UTM parameters to your deeplinks. Gurulu parses utm_source, utm_medium, utm_campaign, utm_term, and utm_content from both web URLs and deeplinks, ensuring consistent attribution across platforms.

The post-ATT world is more complex than the old IDFA approach, but it is also more privacy-respecting and more accurate for users who authenticate. By combining deterministic identity linking with probabilistic install attribution, Gurulu provides a complete picture of your mobile acquisition funnel without relying on deprecated tracking techniques.