·8 min read

App Install Attribution: Apple Search Ads vs Google Ads

Apple and Google can both connect an app install to an ad, but they deliver the attribution through different device and account mechanisms. Here is what to capture—and how to measure what happens next.

What is app install attribution?

App install attribution identifies the marketing source associated with a new installation. It answers the first acquisition question: which campaign, ad or keyword brought this user to the app?

That is necessary but incomplete. A useful attribution system carries the source into onboarding, activation, retention and purchases. Otherwise a campaign that produces many low-quality installs can appear more successful than one that produces fewer paying customers.

Apple Search Ads attribution

On iOS, Apple provides AdServices attribution for Apple Search Ads. An enabled SDK obtains a token from the device, and the server resolves it into attribution data such as a campaign and keyword identifier. This flow does not require IDFA access or an App Tracking Transparency prompt.

The numeric identifiers become useful when joined to Search Ads account metadata and spend. OnRamp can resolve them to campaign and keyword names, then compare those cohorts by onboarding completion, retention and purchase.

Learn how the complete connection works on the Apple Search Ads integration page.

Google Ads app attribution

For an Android install from Google Play, the app can read referral information through the Google Play Install Referrer API. A React Native or Android SDK can capture that context and attach it to the first user journey.

When the journey starts on the web, retain the campaign UTMs and Google click identifiers—gclid, gbraid or wbraid as applicable—and preserve them when the visitor signs up or moves into the product. Google Ads account connectivity can add campaign spend for comparison with attributed installs and product outcomes.

See the current support and boundaries on the Google Ads integration page.

Apple vs Google at a glance

AreaApple Search AdsGoogle Ads
Primary device mechanismAdServices attribution tokenGoogle Play Install Referrer on Android
Web click contextCampaign landing-page parameters where usedUTMs plus gclid, gbraid or wbraid
Keyword detailSearch Ads keyword attribution when availableDepends on campaign type and reported fields
SpendSearch Ads API campaign and keyword syncGoogle Ads account and campaign sync, beta in OnRamp
IDFA requiredNoNo for Play Install Referrer
Best downstream measureKeyword-to-activation and revenueCampaign-to-activation and revenue

Preserve identity after the install

Attribution often arrives before the person creates an account. Store the source against an anonymous visitor or installation first, then associate the existing journey when the user identifies. Do not create a fresh profile that drops the acquisition context at signup.

From there, track explicit milestones such as account creation, permission completion, first key action and subscription. The same source can now be used to filter the complete funnel.

Compare activated-user CAC, not only install CAC

Suppose Campaign A creates 1,000 installs at £1 and only 8% activate. Campaign B creates 400 installs at £2 but 45% activate. The install report favours Campaign A; activated-user CAC strongly favours Campaign B.

This is why mobile app conversion tracking and attribution belong in the same system. Rank campaigns by the conversion tied to product value, then inspect the step where weak cohorts leave.

A practical implementation checklist

  1. Enable the platform attribution mechanism before the first app session.
  2. Preserve campaign and keyword identifiers on the anonymous journey.
  3. Identify the user without discarding the original attribution.
  4. Track three to five activation milestones.
  5. Connect purchase or subscription events.
  6. Sync campaign metadata and spend.
  7. Compare install, activation and purchaser CAC by source.

Start with mobile ad attribution for the full acquisition-to-revenue model.