GA4 Mobile App Attribution: Methods and MMP Decision Guide
GA4 mobile app attribution covers Android and iOS routes; use GA4 if reports suffice, assess an MMP for cross-channel costs and subscription revenue.
GA4 can attribute mobile app installs, with a different route for each source.
first_openrecords the first app launch after installation, rather than the download itself.- Android offers Google Ads auto-tagging, Play Store referrals, and campaign-tagged Android App Links.
- iOS supports Apple Search Ads attribution, campaign-tagged Universal Links, and SKAdNetwork postbacks.
- GA4 may be enough when its configured sources answer your install and app-event questions.
- Add an MMP to your evaluation when you need one view of paid-channel costs and subscription revenue.
GA4 mobile app attribution can identify install sources through supported campaign routes that vary by platform, and Airbridge publishes this guide. The first app launch after installation is recorded as first_open.
The practical choice is not “GA4 or an MMP for every app.” Use GA4 when the configured routes answer your campaign questions. Evaluate an MMP when you need to compare paid acquisition sources against shared cost and subscription revenue data, then choose based on the channels and reports your team actually needs.
What first_open tells you about an install
Google's automatically collected events documentation defines first_open as the first launch after installing or reinstalling an app, so the event marks first use.
The Firebase Analytics SDK collects first_open automatically, with no separate event code needed.
first_open answers “which new users opened the app for the first time?” Campaign attribution answers the next question: “which source or campaign receives credit for those users?” In GA4, that answer comes from a supported route such as Google Ads auto-tagging, a Play Store referral, campaign tags on a link, or Apple Search Ads attribution.
GA4 app install attribution routes for Android and links
Google's app attribution guide covers Google Ads auto-tagging, Play Store referrals, Universal Links, Android App Links, and Apple Search Ads as install-attribution routes.
| Route | Best fit | What GA4 can report | Setup detail to get right |
|---|---|---|---|
| Google Ads auto-tagging on Android | App campaigns or web campaigns that direct people to download an Android app | Source, medium, and campaign information from the ad event after a person clicks, installs, and opens the app | Enable auto-tagging and use the tagged download link; this route applies to Android, with Universal Links or Apple Search Ads for iOS. |
| Google Play install referral | People who reach the Play Store listing from a tagged referral link, or discover the app in Play Store search | google-play can identify a Play Store referral or an organic Play Store discovery | Include a referrer in a link to the Play Store listing when you want the referral identified. A Play Store link with no referrer can appear as (direct). |
| Android App Links with campaign tags | A website or campaign link that routes people to an Android app or store | Campaign information from manual or static utm_source, utm_medium, and utm_campaign tags | Use Android App Links for the app route and preserve the UTM parameters on the path to the store or app. |
| iOS Universal Links with campaign tags | A website or campaign link that routes people to an iOS app or store | Campaign information from manual or static UTM tags | Use Universal Links and add the campaign parameters to the link. Apple's Search Ads installs use a separate documented route. |
Use a consistent source, medium, and campaign naming pattern across links your team controls.
iOS installs, Apple Search Ads, and SKAdNetwork
GA4 has an Apple Search Ads install-attribution route. The app's Xcode project must include the AdServices framework to attribute Apple Search Ads installs in Analytics, per Google's app attribution guide. For these installs, Analytics reports source Apple, medium search, and the AdServices keyword ID as the term.
Campaign-tagged Universal Links are another iOS route when a person follows a link to the app. Add utm_source, utm_medium, and utm_campaign to the link and keep those values intact through the route. This gives a small team a way to label its own web campaigns alongside the Apple Search Ads path.
Google's SKAdNetwork guide for iOS campaign measurement describes SKAdNetwork (SKAN) postbacks as a route for measuring iOS ad campaigns. Apple's StoreKit documentation defines conversion values as six-bit values set by the app or ad network; only postbacks with ad attribution can include a conversion value.
Google Analytics can receive SKAdNetwork postbacks for reporting and conversion modeling. With the Google Analytics for Firebase SDK, registration of relevant SKAdNetwork postbacks happens automatically; teams that send postbacks to Google Analytics themselves send each as campaign.details within four days of receipt for reporting and conversion modeling, per Google's implementation guide. Google also recommends configuring a SKAdNetwork conversion value schema when the goal is to measure post-install events or optimize toward a return-on-ad-spend target.
Google Analytics integrates SKAdNetwork postbacks into first_open key events and event reporting; use Source platform = SKAN to segment this data, as described in Google's postback guide.
When GA4 is enough, and when to evaluate an MMP
GA4 can be enough when it reports the acquisition routes you use and the in-app actions you need to understand. Google's Android User acquisition report defines first-user source and medium as the source and method that led a user to the app. Google's iPhone and iPad User acquisition report includes first-user acquisition dimensions and channels such as Paid Search, Paid Social, Organic Search, and Referral.
Use this short decision process before adding another tool:
- Write the budget question in one sentence. Examples include “Which campaign brought first-time app users?” or “Which paid channel brought subscribers who renewed?” The second question needs subscription outcomes alongside source information.
- List the routes and platforms behind current spend. Mark each as Google Ads, Play Store referral, tagged link, Apple Search Ads, or another paid network. Then match each route to the relevant GA4 setup in the table above.
- Compare the reports with the decisions you make. Check whether source, medium, campaign,
first_open, and the app events tied to activation or subscription answer your question. When the decision is about spend efficiency, include campaign cost and subscription revenue in the report requirement. - Evaluate an MMP when your budget question needs cross-channel attribution tied to cost or subscription outcomes. Adjust defines an MMP as a third-party provider that attributes, collects, and organizes app data to give a unified view of campaign performance, in its MMP glossary. Adjust's explanation says MMP SDKs typically link ad engagements with installs and post-install events; when a device ID is unavailable, such as for iOS users who have not opted into ATT, it describes aggregated SKAdNetwork attribution.
A useful test is to take a recent campaign and follow one user journey in your reporting: campaign link, store visit, first app open, trial, and paid subscription. If GA4 shows the acquisition source and the app events you need, you may have enough reporting for that decision. If the team also needs comparable acquisition cost and subscription revenue across paid networks in the same workflow, an MMP is a reasonable option to assess.
When Airbridge Core fits a subscription team's reporting need
Airbridge Core fits when a consumer subscription team needs paid-channel attribution and cost aggregation alongside subscription revenue reporting for its supported channels. Airbridge Core includes paid ad network attribution for Google, Meta, Apple Ads, and TikTok, cost and ad spend aggregation, subscription revenue aggregation, and Revenue, Funnel, Retention, and Cohort reports.
Those reports map to practical founder questions. Revenue reports connect channels with subscription revenue; Funnel reports help locate drop-off between install, trial, and subscription; Retention and Cohort reports help compare what happens to groups of users over time. Airbridge Core includes channel-level Cost per Subscription, ROAS, and revenue reporting, so a founder can compare acquisition costs with subscription outcomes; see the Core Plan introduction.
For subscription teams whose paid mix includes Google, Meta, Apple Ads, or TikTok, consider Airbridge Core when the budget question needs channel costs alongside subscription revenue; keep GA4 for configured app events and acquisition routes.
FAQS
FAQ
Can GA4 attribute mobile app installs?
Yes. GA4 records first_open and attributes installs through supported campaign routes.
What attribution does GA4 use?
GA4 uses the source information available through the configured campaign route. Depending on the platform and setup, that can include auto-tagged Google Ads campaigns, Play Store referrals, UTM-tagged Universal Links or Android App Links, Apple Search Ads, and SKAdNetwork postbacks.
What is mobile app attribution?
Mobile app attribution connects an install or later app event with an acquisition source or campaign. For a subscription app, the next useful step is connecting that acquisition view with trial and paid subscription outcomes.
Does GA4 work for mobile app attribution?
Yes. GA4 can attribute mobile app installs and report app events; evaluate an MMP when your budget question also requires cross-channel cost and subscription-revenue reporting.
Get Started Free
See how these criteria hold up on the real thing.
Related reading
