Pre-install tracking

Much like ad campaigns, pre-installs are a good way to tap into new audiences. You can arrange with a device manufacturer or a retailer about the pre-installation of your app on their devices. MyTracker is here to help you gauge the effectiveness of that approach.

• how many pre-installs resulted in the launch of your app;
• what kind of audience the manufacturer brought in (age, activity, LTV, etc.);
• how much money each pre-install and the manufacturer overall generated.

Pre-install tracking is available only for Android devices

How it works

MyTracker offers several methods for tracking pre-installs:

• PAI (Google Play Auto Install) when apps are automatically loaded and installed from the cloud after users activate the devices.

  To track pre-installs, generate referrer with PAI parameters in the MyTracker interface and share it with a device manufacturer to insert it in the utm_campaign parameter. When a user launches your app for the first time, MyTracker queries the Google Play Install Referrer API and retrieves pre-install data.

This method is available only for apps published on Google Play

• ApkPreinstallParams, when retailers install the app in the device sale.

  To track pre-installs, generate APK parameters in the MyTracker interface, add them to the app build, and share the APK file with the retailer. With the customer's consent, the retailer installs the APK on the device. When a user launches your app for the first time, MyTracker reads APK parameters and retrieves pre-install data.

Use this method when no other options are possible. If the user decides to update the app before the first launch, APK parameters will be erased and the pre-install will not log.

• System Properties when apps are installed on devices before they go on sale.

  To track pre-installs, generate key-value in the MyTracker interface and share it with a device manufacturer to insert it in the device’s system properties. When a user launches your app for the first time, MyTracker retrieves pre-install data.

• System Properties (additional method) is an outdated method. A manufacturer places key-value in the special file and specifies the path to the file in the device's system properties.

Where to start

1. Make sure MyTracker SDK has been integrated into your app.
2. In MyTracker, add an ad campaign listing Pre-install as Campaign type and the device manufacturer or retailer as Partner.
3. Add a separate tracking link to the campaign for every app to be pre-installed:
   • On the Tracking links tab, click Add.
   • Enter the link title (for MyTracker lists and reports) and select the Android app that you need to pre-install.
   • Click Add. MyTracker will generate parameters for pre-install tracking.
4. Optionally, you can add additional parameters to get more information about the campaign with the pre-install event. For example, a factory name or a campaign launch time.
   • Click Add parameters.
   • In the opened window, enter the values for the parameters SubID. At the bottom of the window, you will see the resulting parameters you need to share with your partner.

Be sure to copy the result, because the entered parameters will be deleted when you close the window


5. Provide the manufacturer or retailer with obtained parameters. Depending on the tracking method you choose, follow the instruction below: PAI, ApkPreinstallParams, System Properties, System Properties (additional method).

PAI

The Google Play Auto Install (PAI) method allows you to track the pre-install performed when a user activates a new device.

This method is available only for apps published on Google Play

1. Provide the manufacturer with referrer obtained by the instructions above, for example:

mt_link_id=abc123&mt_sub1=factory1&mt_campaign=summer2023

2. Ensure that the manufacturer inserted referrer in the utm_campaign parameter.

When a user launches your app for the first time, MyTracker can query the Google Play Install Referrer API, retrieve referrer, and attribute the pre-install to your ad campaign and the manufacturer.

ApkPreinstallParams

The ApkPreinstallParams method allows you to track the pre-install performed when selling devices in retail:

1. Create a separate APK with MyTracker SDK v3.0.12 or higher. Specify APK parameters, obtained by the instructions above, in the SDK configuration using the setApkPreinstallParams method. For example:

final MyTrackerConfig myTrackerConfig = MyTracker.getTrackerConfig();
  myTrackerConfig.setApkPreinstallParams("mt_link_id=a12345&mt_sub1=retailer1&mt_campaign=summer");

The app build with APK parameters is for the retailer only. You should not upload APK to the app store, as all installs will be attributed to the one partner.

2. Share the APK file of the app with the retailer (partner). With the customer's consent, the retailer installs the APK on the device.

When a user launches your app for the first time, MyTracker can read APK parameters and attribute the pre-install to your ad campaign and the retailer.

If the user decides to update the app before the first launch, APK parameters will be erased and the pre-install will not log. If possible, use other methods to track pre-installs.

System Properties

The System Properties method allows you to track the pre-install performed before a device goes on sale.

1. Make sure MyTracker SDK that supports pre-installs (v2.1.1 or higher) has been integrated into your app.
2. Give the manufacturer key-value obtained by the instructions above.

Maximum value length is 91 symbols.

3. Ensure that the manufacturer placed the key name and value in system properties (build.prop) and granted all users the read permission (644). For example:

adb root
adb remount
adb pull /system/build.prop
echo ro.mtpi.00000000000000000000={"mtLinkId":"aaaaa0", "sub1":"factory1", "campaign":"summer2023"} >> build.prop
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot

When a user launches your app for the first time, MyTracker can read key-value and attribute the pre-install to your ad campaign and the manufacturer.

System Properties (additional method)

You can use the System Properties (additional method) method if the main System Properties method is not suitable for you.

We recommend using the main System Properties method, because the additional method involves editing of a key-value file, what can cause errors and loss of keys.

1. Make sure MyTracker SDK that supports pre-installs (v2.1.1 or higher) has been integrated into your app.
2. Crete a special pre-install.mytracker file.
3. Add key-value obtained by the instructions above to the pre-install.mytracker file.
4. Share this file with the manufacturer for the further placement in devices.
5. Ensure the manufacturer copied the file to the device and specified the file path in the system properties (build.prop) by using the ro.mytracker.preinstall.path key. If the file had already been copied, ensure the manufacturer enhanced it by adding a new line.

When a user launches your app for the first time, MyTracker reads the patch to the pre-install.mytracker file along with key-value and attribute the pre-install to your ad campaign and the manufacturer.

Pre-install reports

MyTracker retrieves pre-install data after a user launches your app.

To analyze pre-install campaigns, use Report builder. For example, Select from list → Dimensions → Traffic source → Campaign → Partner to compare data by different manufacturers.

For details, refer to the Analytics section