How to Configure Preload Referrer Attribution in Apptrove?

preload

To run the preload advertising initiatives, marketers can engage many users without using classic internet advertising campaigns. People will be able to make sure that all applications which they install on various new devices are associated with the correct advertisements due to the preload attribution system working for them.

The Google Play Auto Install (PAI) load attribution flow

Google Play Auto Install incorporates ID checks. This means that once people switch on their devices, certain installing happens automatically.

1. Device activation

When users switch on their devices for the first time, specific applications will be downloaded automatically from the cloud and installed on their devices according to the regulations that have been created by the advertiser in advance.

2. Application run

When users start the application that comes with the device, the Apptrove SDK uses the Google Play Referrer API to obtain the needed data.

3. Attribution process

Using the received information concerning the source of the application, Apptrove is able to realise which advertisement has brought the customer to the installation of this application.

  • Media Source: Partner ID
  • Match Type: preload_pai
  • Campaign Name: preload campaign by <preloadpartner ID>

This procedure provides for the assignment of installation to the respective preload partner.

Preload Attribution Flow

Preload

The total process of preload attribution can be explained in the following four points:

  • A device is activated for the first time.
  • The specific applications are pre-installed in the Google Play Store.
  • The user uses the application for the first time.
  • The Apptrove SDK uses Google Play Referrer API for performance attribution of the installation. 

Preload Attribution Method

For PAI campaigns the partner needs to set up media source information in the Google Play Referrer API.

utm_source=play-auto-installs&utm_medium=preload&utm_campaign={partnername}_oempai

The following parameters contain the data necessary for identifying a preload source and campaign within an attribution process. 

Configuring the OEM Campaign

If we work with OEM campaigns that are not part of the preload flow, necessary configurations should be made separately.

Configuring Postbacks 

Today, it is possible to configure necessary postbacks in the process of account configuration. 

Using different parameters in our attribution links, we get an opportunity to conduct a more precise analysis. 

Different parameters that can be modified:

Campaign

Insert a Campaign parameter into the attribution link when comparing different campaigns running alongside ads. 

Ad Set

Ad Set parameter should be used for naming ad sets and comparing different ad sets during the campaigns. 

Ad Name 

Ad Name parameter can be used for distinguishing certain creatives within the specific ad sets.

Site ID and Sub Site ID 

Site ID parameter should be used when we want to attribute installs to particular publishers. Besides, Sub Site ID could be used for attribution as well.

See the related postback macro documentation for further details about the postback macros.

APK hardcoding

Preload

Another way is to hardcode information like the name of the partner, partner ID, campaign, advertisement, etc. into the APK that will be sent to the users.  This method makes it possible to attribute the installation to the right partner. When working with the advertiser, you ask them whether they can send the necessary information via the init block of their application.

With the right preloads, Google Play Referrer information, postback parameters, or APK-level settings, you can be sure that Apptrove is provided with the necessary information for the correct attribution of the installation.

Final thoughts

 Preload campaigns allow advertisers to distribute apps by downloading them at the device level, eliminating the need for traditional online campaigns. Implementing the appropriate attribution setup will allow Apptrove to track app installations from preload partners by using the Google Play Referrer API for data collection. 

Installing all necessary PAI parameters, postback details, or APK hardcodes will result in having the attribution data being available for further analysis at the level of partners and campaigns.



from Apptrove https://apptrove.com/how-to-configure-preload-referrer-attribution/
via Apptrove

Comments

Post a Comment

Popular posts from this blog

VTR Formula: What is View Through Rate and 5 Tips to Improve VTR

Image
From six-second clips to longer videos, video marketing captures attention like never before.  As digital viewership rises, marketers spend big on video ads—hitting $176.63 billion in 2023 alone. If you aim to cut it in digital marketing, video ads can prove a game-changer.  But running ads alone isn’t enough, you must track the right performance metrics. One key metric that often goes overlooked is the view-through rate (VTR), which measures the effectiveness of your video ad campaigns. It tracks how many users engage with your video ads without skipping.  A strong VTR means your ads are making an impact and driving conversions. However, statistics reveal that around 66% of users skip in-app video ads when they can. Therefore, you need a smart strategy to improve your VTR. In this post, we’ll explain the view-through rate, VTR formula, and its significance and share five actionable tips to help you get more from your video ads by improving VTR. What Is VTR? V...
Read more

Mobile Marketing QR Codes: Dynamic Strategies for Measurable App Growth

Smartphones have become the most powerful connection between brands and consumers. Push notifications, deep linking, and in-app ads often receive the most attention, however, the most undervalued yet effective form of mobile marketing is the QR code. QR codes first appeared in the consumer market for marketing purposes around 2011 . And in the last 10 years, mobile marketing QR codes have grown from being simple black-and-white squares, to dynamic, data-driven gateways of engagement. They aren’t just for scanning a menu at a restaurant anymore! Today they drive app downloads, document offline campaigns, and unlock interactive experiences. In this blog, we’ll look at why mobile marketing QR codes should be a part of every app marketers toolbox, how to implement them in an effective manner, and how to optimise them for search engines, answer engines and generative AI. By the end, we’ll explore why mobile marketing QR codes are critical for acquisition, engagement, and retention, how to...
Read more

What is a Device ID?

Image
A Device ID, or device identifier, is a code unique to your mobile phone, tablet, or even smart TV. It acts like a name tag for your phone, telling apps and services, “Hey, I’m THIS device!” Each phone has a unique ID, and no two devices have the same one. This makes it very useful for app developers because they can use this ID to track devices without needing personally identifiable information like your name or email. There are different types of IDs and a few variations on them, especially with Android phones, such as the following: – IMEI (used for devices with SIM cards) – Android ID (which is created by the Android system) – Google Services Framework ID – Advertising ID (used for advertising personalization) Some of these IDs are permanent and some are resettable depending on their use. Why is the Device ID Important? Below are some of the ways this ID is helpful: App Personalization: Apps can save your preferred settings based on your Device ID. Security: Can ...
Read more