At A Glance: This article provides a deep understanding of preload attribution using Google Play Auto Install (PAI) within Apptrove.
In preload campaigns, Original Device Manufacturers (OEMs) and mobile carriers ("Preload Partners"), preload apps on devices before they reach the user. This can be done by the OEM at the factory or by providers upon first device activation.
Preload campaigns allow advertisers to reach a potentially large audience without running online campaigns.
Google Play Auto Install (PAI) Preload Attribution Flow:
Device Activation: When a new device is activated for the first time, predefined apps are automatically installed from the cloud according to rules set by the Preload Partner.
App Launch: Upon the user's first launch of a preinstalled app, the Apptrove SDK queries the Google Play referrer API.
Attribution Decision: Apptrove determines attribution based on the data retrieved from the referrer API.
Installs attributed to Preload Partners are recorded as follows:
Media_source: Partner ID
Match_type: preload_pai
Campaign_name: preload campaign by <preloadpartner ID>
Flow for preload
A new device is activated for the first time and predefined apps are automatically installed on it from Google Play according to rules set by the preload partner.
The user launches a preloaded app for the first time.
The AppTrove SDK queries the Google Play referrer API.
We attribute based on the data retrieved.
Pre-load attribution method
Partner is required to configure the media source information in the Google Play Referrer API for PAI campaigns
utm_source=play-auto-installs&utm_medium=preload&utm_campaign={partnername}_oempai
OEM Campaigns Configuration - Other than Preload
Postback Configuration
You can also place your postback as part of the account
Adding parameters to the attribution link here enables you to later perform thorough drill-down analyses. Parameters that are already defined on the attribution link can be edited by adding them and their new values here.
Campaign - add it to compare different campaigns running with you ads
Adset - set ad set names to compare different ad sets within specific your Ads campaigns.
Ad Name - set ad set names to compare different creatives within specific ad sets
Site ID and Sub Site ID - set Site ID parameter to attribute installs to specific publishers
To know more about it click here and for macros support click here
APK Hardcoding
One can hardcode the partner name, ID, campaign, ad etc as part of the APK being shared with the users
This ensures that installations can be accurately attributed to the respective partner.
Once you start working with an advertiser you can ask them to pass below in the init block of their application -
val sdkConfig = TrackierSDKConfig(applicationContext(), TR_SDK_KEY, "development")
val attributionParams = AttributionParams(
parterId = "pass your partner id",
siteId = "pass your site Id",
subSiteID = "pass your sub site Id",
channel = "pass your channel",
ad = "pass your ad",
adId= "pass your ad id"
)
sdkConfig.setAttributionParams(attributionParams)
TrackierSDK.initialize(sdkConfig)
Broaden Your Knowledge:
We are delighted to have assembled a world-class team of experienced professionals who are ready to take care of your queries and answer any questions you may have.
Feel free to reach out to us at any time by emailing us at support@apptrove.com or by using the in-platform chat feature. We'd love to hear from you!
