Mobile attribution is the process of connecting actions and activities that occur outside of a mobile app, to those that occur in the app. Singular tracks these attributions via linking an impression or click action that happens on a device, to the install (first session) of a mobile app on that same device.
Singular’s mobile attribution tracking uses the following methods to perform install attribution:
|Referrer (Android only)||
This is considered as the most reliable way for attribution. It uses a unique Singular referral ID that is passed on to Google Play store once a user clicks on an ad. Once the user installs the app, the Singular SDK sends the Singular referral ID forwarded by the Play Store, and attribution is performed.
Additionally, Singular uses same referrer technology to capture other attributions labelled in Singular as "UTM Referrer" attributions.
|Identifier Matching||In this method, the attribution is done based on the Google Advertising ID (AIFA) or iOS Advertising ID (IDFA) that are sent in the tracking link. Once the install event arrives from the Singular SDK, it is matched to the click based on that ID. Identifier matching has a maximum of a 30-day attribution window.|
|Fingerprint Matching||In this method, a tracking URL collects basic information of the device, including IP address and model, which results in a unique fingerprint. The same fingerprint is generated locally on the device once the app is installed and then sent via Singular SDK session. The click and the session are then fingerprint matched. Fingerprint matching is limited to 24 hours.|
Using this method, we query special API’s for attribution data of special partners like: Facebook, AdWords, Twitter, Apple Search Ads, Snapchat, Yahoo Gemini.
In accordance with Google and Apple privacy policies, Singular tracks unique devices and their attribution information, using the user-resettable Google Advertising ID (AIFA) and iOS Advertising ID (IDFA).
Singular retains a device’s install attribution information for two years to ensure attribution and cohort accuracy. Re-engagements can be tracked any number of times with supported partners.
Re-engagement attributions are where existing users who have installed the app already, are actively re-targeted by a campaign. These attributions are only supported through campaigns where the tracking tag is enabled for re-engagement. In the case of self-attributing networks who do not use tracking tag, ensure re-engagement tracking in enabled in partner configurations.
Event attribution is based on the device’s attribution. For example, an event that occurs on the device will be attributed to the source of the device’s last attribution, whether it be the install attribution or re-engagement attribution.
Android apps with the Singular SDK leverage the Android Referrer API to pass a Singular referral ID for attribution. Attributions to the Singular referral ID are prioritized as they are attributions tracked via Singular tracking links. However, referrer technology also allows Singular to capture attributions from anyone who clicks on a Play Store URL with UTM referrers appended.
Since these are attributions not tracked through a paid source via Singular, UTM Referrer attributions are only counted if no other paid source claims the attribution. UTM Referrer attributions can often offer interesting insights to where additional "Organic" traffic can be coming from. For example, apps downloaded from the app search tab in the Android Facebook app will be tracked in Singular as a "UTM Referrer" attribution to "app.facebook.com".
If you would like to enable UTM Referrer tracking for your Android apps, please reach out to your customer success manager, or email@example.com!