Google Ads app campaign measurement
Google Play services and the Firebase SDK report installs and in-app events straight to Google Ads.
In one line
Can tell Google Ads about your installs and in app actions
Google Play services and the Firebase SDK report installs and in-app events straight to Google Ads.
Google already knows the click, the install and the account. The SDK adds in-app events, closing the loop with no third-party MMP.
What it can and can't do
What the user does: You tap a Google ad, install the app, then use it
It can
- Tell Google an ad led to an install, using the Play install referrer
- Report in app purchases and events back to Google Ads
- Use the Android ad ID, or the IDFA only if you allow it on iPhone
It cannot
- Send the IDFA on iPhone after you tap Ask App Not to Track
- Send data you did not generate in the app
- Skip Google's own matching; no outside tool is needed
How it differs between platforms: Android uses the install referrer and ad ID. iPhone uses Apple's delayed reports and the IDFA only if allowed.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Not available | Not available |
| Permission or entitlement | AD_ID for ID use | NSUserTrackingUsageDescription for IDFA use |
| Protection level | none | prompt |
| How access is granted | none | prompt |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | Data safety must mention ad ID, app activity; consent mode in EEA | ATT; privacy manifest for Google SDKs |
| API | Firebase Analytics, Google Ads conversion linking, Play services | Firebase Analytics, SKAdNetwork |
| Notes | Uses Play Install Referrer and AAID on Android, SKAN and IDFA (if allowed) on iOS. | iOS conversion modeling and SKAN conversion value mapping inside Google Ads. |
Data you get
What comes back: Conversion events and ID
Shape: object
How often: continuous
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
gclid / gbraid / wbraid | string | None | click IDs for web and app flows | Not listed |
Technical limits
- Needs Firebase link to Google Ads
- Consent signals required in EEA
The story
What it is
Google counts installs and in app actions straight from your phone, to prove its ads worked.
For you
You tap an ad on Search or YouTube, install the app and play. Google quietly learns that this ad led to your install and, later, to your first purchase.
For makers
Google already knows the click, the Play install and the account, so the SDK only has to add what happens in the app. That closes the loop with no third party tool, and feeds Google's bidding with real results.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A studio runs an app campaign and sees which ads bring players who spend money in week one. | Clash Royale, Subway Surfers |
| shopping | A retailer measures how many YouTube viewers install the app and buy within a day. | Walmart, Wish |
| rideshare | A ride app measures first ride completions after an ad install, to set its bids. | Uber, Lyft |
| banking | A bank counts approved accounts from ads and bids more for similar people. | Chime |
| ads | Google's automated bidding learns to show ads to people like past buyers. | Google Ads |
| analytics | A growth team sends the same events to Firebase and Ads and compares the two reports. | None named |
Risks
- Joins ad click to in app behavior
- Hard to opt out except by device reset
Android and iPhone in short
- Android: Uses the Google advertising ID and the Play install referrer.
- iPhone: On iOS, Google uses SKAdNetwork and consented IDs because of ATT.
What the platform says
- Google: App campaign conversion tracking. Link Google Ads with Firebase to see which ads lead to installs and in app actions.
Good uses and abuse
Legitimate uses
- Optimizing app install campaigns
Known abuse
- Linking across Google properties
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2024-03, Android Play services: Consent Mode v2 requirements for EEA ads data (mobile and web)
Related capabilities
Related
- Google Analytics for Firebase. Can give each install an ID and log your taps and screens for Google
- Install referrer. Can learn which ad or link led to your install, for 90 days after
Same idea on the web
- Ad click IDs (gclid, fbclid, msclkid and more). Can tag your ad click so a later purchase links back to that exact ad
Sources
How well checked: Based on official documentation.