Google Ads

Guide · 24 Oct 2026

Google Play Install Referrer: verify MMP install data

Separate store-data retrieval, MMP attribution rules and Google Ads conversion handling when investigating Android install reports.

G2P Media · · 4 min read

Google Play Install Referrer: verify MMP install dataGoogle Ads

At a glance

FieldDetail
WhatVerify how Google Play referral data reaches an app's attribution reports.
Who it matters toAndroid app buyers and developers investigating install attribution, including Google Ads campaigns.
WhereGoogle Play installs; MMP behavior depends on the provider's integration.
When it appliesDuring SDK integration, release checks or an install-reporting investigation.
ActionCheck retrieval, field definitions and attribution handling separately.

Google Play Install Referrer supplies referral information that a mobile measurement partner (MMP) can use for attribution. For app buyers, the practical decision is where to investigate: the app's access to store data, the MMP's interpretation or the handoff into Google Ads measurement.

Prerequisites and ownership

Google documents an API exposed by the Play Store app. It returns referral content including the installed package's referrer URL, click and installation-start timestamps, and the app version at first installation. Google also requires a Play Console account. See the official overview.

PrerequisiteDocumented requirement or capabilitySuggested check
Store accessThe API depends on a supported Play Store app version.Confirm the test device meets Google's documented requirement.
Development approachGoogle provides a client library for Kotlin and Java.Identify whether the app or its measurement SDK handles retrieval.
Adjust integrationAdjust's Android guide includes the install referrer dependency.Review the integration instructions for the SDK actually shipped.

Our suggested ownership split is simple: ask the developer to confirm retrieval and the measurement owner to confirm how the returned information appears in reporting. Keep those findings in the same test record so that a successful SDK build does not become the sole acceptance criterion.

How MMPs use the information

AppsFlyer describes install referrer attribution as a deterministic method that does not use a device ID. Its attribution model also prioritizes clicks over impressions and deterministic methods over probabilistic methods when multiple valid engagements exist. Those are AppsFlyer's rules; review your own provider's model before interpreting a result. AppsFlyer attribution model

AppsFlyer records an acquisition install after download and launch, with the install timestamp representing first launch. Our suggested reporting check is to identify which event each timestamp represents before treating differences as missing installs.

Set up the retrieval path

Confirm the SDK implementation

For Adjust, the Android SDK integration guide instructs developers to add the Android install referrer dependency. It separately requires an app token and environment when initializing the SDK, with a sandbox environment for local testing. Check those elements against the app build under investigation rather than assuming the dependency alone completes integration.

Review direct API handling where applicable

For direct integration, Google's library guide describes an asynchronous connection, a setup callback, retrieval of ReferrerDetails and closing the connection.

Google advises invoking the API once during the first execution after installation. Our suggested implementation review is to confirm who owns that behavior before adding separate retrieval logic alongside an MMP SDK.

Check the Google Ads handoff

Google's Privacy Compliant App Attribution guide addresses consumers of its App Conversion Tracking and Remarketing API. For the documented Android install scenario, it says to parse gclid from the install_referrer field when the user first opens the app, store it and pass it through market_referrer_gclid.

That guidance establishes a specific conversion API handoff. Our suggested check is to ask the integration owner how that handoff is implemented in your measurement route. A readable referrer by itself does not demonstrate that the conversion request carries the expected field.

Verify results and investigate problems

AppsFlyer's raw data field dictionary distinguishes gp_referrer, the installed package's referrer URL; gp_click_time, the Play app-page load time following an ad click; and gp_install_begin, when installation begins. Use those definitions when reviewing an available test record.

Symptom or questionSource-backed distinctionSuggested check or fix
Direct API setup reports FEATURE_NOT_SUPPORTEDGoogle's example identifies an unavailable API on the current Play Store app.Review Play Store compatibility.
Direct API setup reports SERVICE_UNAVAILABLEGoogle's example identifies a connection that could not be established.Investigate the connection; distinguish it from unsupported functionality.
Referrer stays unchanged between app launchesGoogle says the information stays unchanged unless the app is reinstalled.Review the test's installation state before expecting new referral data.
Install time differs from installation-start timeAppsFlyer's install timestamp represents first launch.Compare event meanings before classifying the difference as an error.
Referrer data exists but the Google Ads handoff is uncertainGoogle specifies a separate conversion request field for the documented scenario.Ask the integration owner to verify market_referrer_gclid handling.

What to review

  • Confirm the tested build and its referrer integration.
  • Check API connection outcomes separately from report attribution.
  • Compare store timestamps with the MMP's install definition.
  • Review the documented Google Ads conversion handoff with its owner.
  • Keep event and reporting definitions together in a measurement data-path review.

Universal report availability across MMPs is not specified in the cited documentation. Check the provider and reporting route you actually use.

Discuss your app.

Discuss your app