Skip to Content
Platform.Ontology

Google Ads app campaign measurement

Google Play services and the Firebase SDK report installs and in-app events straight to Google Ads.

Used to track youAds and install trackingGoogle attributionAndroid and iPhoneBefore you installWhen the app opensWhile you use it

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

AndroidiPhone
StatusSupportedSupported
First versionNot availableNot available
Permission or entitlementAD_ID for ID useNSUserTrackingUsageDescription for IDFA use
Protection levelnoneprompt
How access is grantednoneprompt
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyData safety must mention ad ID, app activity; consent mode in EEAATT; privacy manifest for Google SDKs
APIFirebase Analytics, Google Ads conversion linking, Play servicesFirebase Analytics, SKAdNetwork
NotesUses 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

FieldTypeUnitRangePrecision
gclid / gbraid / wbraidstringNoneclick IDs for web and app flowsNot 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

TypeExampleApps
gamesA studio runs an app campaign and sees which ads bring players who spend money in week one.Clash Royale, Subway Surfers
shoppingA retailer measures how many YouTube viewers install the app and buy within a day.Walmart, Wish
rideshareA ride app measures first ride completions after an ad install, to set its bids.Uber, Lyft
bankingA bank counts approved accounts from ads and bids more for similar people.Chime
adsGoogle's automated bidding learns to show ads to people like past buyers.Google Ads
analyticsA 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

Good uses and abuse

Legitimate uses

  • Optimizing app install campaigns

Known abuse

  • Linking across Google properties

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction1 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2024-03, Android Play services: Consent Mode v2 requirements for EEA ads data (mobile and web)

Same idea on the web

Sources

How well checked: Based on official documentation.

On this page