Install referrer and identity

Google Play Install Referrer

When collection is enabled, the SDK requests the Google Play install referrer, waits up to five seconds, and includes available referrer data in the installation request. Missing or unavailable referrers are omitted. Available referrers are persisted for install retries.

Referrer collection support is implemented. End-to-end attribution from a Play-distributed install has not yet passed acceptance. The emulator validation does not establish paid-campaign attribution accuracy. Do not assume every ad network exposes its attribution through a Play referrer.

Installation identity

AttributeHQ.getAppInstanceId() returns the app-scoped random installation UUID after initialization while collection is enabled. It returns null before the ID is available or while collection is disabled.

The SDK does not collect GAID or Android ID and does not declare AD_ID permission. There is no advertising-ID fallback chain. SharedPreferences and Android backup/restore behavior affect identity persistence; review your host app’s backup exclusions.

Attribution results

getAttribution() exposes the cached response from AttributeHQ after install acknowledgement. The result type includes DEVICE_ID, FINGERPRINT, INSTALL_REFERRER and ORGANIC; an enum value’s presence does not mean that every matching path is validated for this release. No fixed attribution confidence or matching success rate is promised.

Android Meta/X delivery and paid attribution remain separate validation gates. SDK installation and sandbox evidence upload do not enable them.