Skip to content

App stores & OEMs Attribution

paulotrezentos edited this page Feb 28, 2020 · 29 revisions

The Attribution Process

When the App wants to know what Store or OEM is eligible for rewards it will follow five steps sequentially. This means that the App will try the first method (Android DB + MAP) to get the the eligible store, if it fails, then will try the second method (Install Broadcast) and so on. The same is applied to OEM.

As represented in the image below, these are four distinct methods to fetch the Store and the OEM.

Attribution Table

Available methods:

1. Android DB + MAP

This method, The App with request either the Local storage or operating system (data base) for the assign Store.

2. Install Broadcast

When the app is installed, it broadcasts the store and the OEM. This methods fetchs those values.

3. Device file

This method will check if there is a assigned Store or OEM in the device file.

4. APK File

This method will check the installed APK file for the store and the OEM.

5. Model of the device

This method will check the Brand / Model of the device and can attribute to specific brands that support AppCoins.

The attribution flow can be represented in the following image:

Attribution OEM Flow

Usecases

Different App Store use cases exist that can benefit of attribution:

  • OEM Android app store: this store is pre-loaded in the device
  • OTT (over-the-top) app store: side loaded by the user from the app store website
  • Direct APK download site: APK of the app is downloaded directly by the user
  • Developer's website: app / game developers make available the APK in their site