Bulletin - Open Advertiser ID (OAID) in AppsFlyer Android SDK

  • Advertisers
  • Developers

This bulletin is relevant to app owners who market their Android apps to users whose devices do not have Google Play Services/GAID. This is typically the case for Android devices marketed in China. 

Publication date Who is impacted  What's affected
November 3, 2019

App owners who market their app to Android users in China/devices without GAID

  • Unique identifiers enabling attribution in Android apps
  • Access to the IEMI is restricted starting with Android 10 (API level 29) 
  • Open Advertiser Identifier (OAID) is  supported in AppsFlyer Android SDK V4.10.3 and above

What's changing

Technology changes impact app owner ability to identify app users in the attribution process:  Access to the IMEI is restricted starting with Android 10 (API level 29). As a result, app owners can no longer rely on IMEI as a unique identifier for attribution in newer Android devices. 

During late 2019, Huawei announced that the Open Advertiser Identifier (OAID) is supported in devices, starting with HMS 2.6.2.  Market indications are that OAID will be adopted by additional device manufacturers. As such, it looks like OAID will become the standard identifier in China for attribution.  

How this affects you

In newer devices, meaning those with API level 29 and above, you will no longer be able to attribute using IMEI as it is generally no longer accessible to apps. This necessitates the use of a different unique identifier, being the OAID. 

What do you need to do

  • Continue to implement IMEI as you do today.
  • Implement OAID. This will enable the attribution of newer devices provided that the device manufacturer, implements OAID.

To implement the recommendations:

  • Integrate AppsFlyer Android SDK 4.10.3 or later into your app.
  • Enable the collection of OAID as follows:
    AppsFlyerLib.getInstance().setCollectOaid(true);
Was this article helpful?
0 out of 0 found this helpful