Install Attribution

Also known as: Attribution, Install Source Tracking, User Acquisition Attribution

Definition

Install Attribution is the process of identifying and crediting the specific source—such as organic search, app store browse, paid ads, web referrer, or external app referrer—that drove a user to install an app. Attribution connects installs to their origin, enabling ASO professionals to measure organic vs. paid performance and optimize spend allocation.

How It Works

Apple App Store

App Analytics in App Store Connect automatically attributes installs to source: App Store Search, App Store Browse, Web Referrer, App Referrer, and Other. For Search, attribution is immediate upon tap and install. For paid campaigns (Search Ads), SKAdNetwork (SKAN) provides privacy-preserving attribution data without IDFA, reporting postbacks to campaign and conversion values.

Google Play Store

Google Play Console's Acquisition section shows install sources: Organic Search, Browse, Paid Campaigns (Google Ads), Referred by App, and Web Referrer. Google Play Install Referrer API (legacy) allowed third-party attribution; post-privacy changes, Google Play Measurement Partner Program via Google Analytics 4 is preferred.

Amazon Appstore

Amazon Developer Dashboard provides install source reports: Category Browse, Search, Paid Ads, Referrals. Attribution is less granular than Apple/Google but functional for paid campaign tracking.

Formulas & Metrics

Attribution Formula (Install Source):

Total Installs = Organic Search + Browse + Paid Ads + Web Referrers + App Referrers + Other

First-Touch vs. Last-Touch Attribution:

First-Touch: Attributes install to first source user encountered (discovery)
Last-Touch: Attributes install to last source before install (conversion trigger)

MMPs (Mobile Measurement Partners) Attribution Model:

Adjusted Installs = (Platform Reported Organic) + (MMP-Attributed Paid) + (Unattributed Estimate)

SKAN Conversion Value Mapping (iOS):

Each SKAN postback includes a conversion value (0–63), mapped to fine-grained outcomes (specific events, revenue tiers, retention milestones).

Best Practices

Use Official Platform Data First — App Store Connect and Google Play Console organic data is gold standard for ASO. Never override official data with MMP estimates for organic.

Implement SKAdNetwork/SKAN Properly — Ensure app is registered in App Store Connect, sk-networks configured in Info.plist. Map conversion values to meaningful business events.

Establish Baseline Organic — Track organic installs before paid campaigns to establish true baseline, avoiding over-attribution of paid installs.

Segment by Platform — iOS (SKAN) and Android (Google Analytics 4 + Play Measurement Partner) have different attribution latency. Report separately.

Monitor Attribution Lag — SKAN postbacks delayed 24–72 hours. Google Analytics 4 similarly delayed. Plan reporting 3–5 days post-campaign.

Reconcile MMP vs. Official Reports — MMPs and official platforms may diverge by 5–15%. Document methodology and accept variance.

Examples

Example 1: App Store Attribution

October 2025 organic search installs: 5,000
October 2025 organic browse installs: 800
October 2025 paid search installs (Search Ads, SKAN-reported): 2,000
Total monthly installs: 7,800
Organic: 5,800 (74%), Paid: 2,000 (26%)

Example 2: Multi-Touch Attribution

User discovers app via Google Search (first touch) → bookmarks
Later taps App Store Browse recommendation (last touch) → installs
System attributes to Browse; user journey involved Search (organic visibility driver)
Decision: Use first-touch for organic strategy evaluation, last-touch for install driver analysis

Dependencies

Influences

Organic Installs — Attribution determines organic vs. paid split
Download Velocity — Attribution reveals which sources drive fastest growth
Conversion Rate — Attribution tracks store page views to installs by source

Depends On

App Store Connect — Official attribution data source for iOS
Google Play Console — Official attribution data source for Android
Search Visibility — Organic attribution requires search impressions
Ranking Factors — Ranking determines search install volume available for attribution

Platform Comparison

Metric	Apple App Store	Google Play Store	Amazon Appstore
Install Attribution	SKAN (SKAdNetwork) for paid; native App Analytics for organic. Postback delay 24–72 hours. Conversion values 0–63.	Google Analytics 4 + Play Measurement Partner integration. Near-real-time for organic via Play Console. 24–48 hour delay for paid.	Basic install source reports. Limited paid campaign integration. Best-guess estimates for performance.