Registering test devices

At a glance: When performing attribution tests, register your test device to make sure each install is recorded as a new install. A registered test device prevents installs from being recorded as reinstalls.

Overview

When performing attribution tests, the re-attribution window limits install attributions to one per 90-day window. Therefore, if you repeatedly use the same device to test install attributions, nothing is recorded. Registering a test device prevents installs from being recorded as reinstalls. 

Methods for registering a test device

Registering a test device includes selecting the device's operating system (Android, iOS, or Windows), and adding the device identifier.

You can use one of the following methods to register:

Keep in mind the following:

  • Registered test devices are available to all apps that belong to the account.
  • Ad networks need to ask an advertiser to add devices; agencies can add their own devices.

Supported device identifiers

Device identifiers include the following:

  • Android: AID (GAID or OAID), IMEI, Android ID

     Note

    When registering a test device, you should only add IMEI or Android ID device identifiers if your app uses these identifiers.

  • iOS: IDFA, IDFV
  • Windows Phone: Windows advertising ID

Managing the registered-device list

Add a device using the AppsFlyer device ID app (admin only)

To download the AppsFlyer device ID app:

  1. Download and install the app using the QR code (Google Play store) or one of the provided links.

    AndroidiOSWindows

     

  2. On an iOS 14.5+ device, if you want to allow IDFA collection, tap Allow when the ATT prompt displays.

    ATT_prompt

  3. On the Android/iOS/Windows screen, tap Register to register the device.

    AndroidiOSWindows

    AndroidRegisterAppsFlyer_us-en.png

  4. Enter your AppsFlyer login credentials. The device is now registered.  
  5. Tap Share details to share Device ID information.

Add a device manually via the user interface

Account users can manually add a device identifier to the list of test devices. 

To add a device to the list:

  1. In AppsFlyer, in the upper-right click on your email address.
  2. Select Test devices.

    Register_Test_Device

  3. Click Add device
  4. Complete the following:
    • Name (only use English letters): Enter an identifying name for the device.
    • OS: Select an operating system. 
    • Device ID type: Select a device identifier. 
    • Device ID: Provide the device ID according to the operating system :
      AndroidiOSWindows

      Get identifiers by using the AppsFlyer Device ID app or by dialing the codes into the device: 

      Identifier Retrieval method Google Play Other
      AID (GAID or OAID) Use the AppsFlyer Device ID app Mandatory Can be used to register the device
      IMEI *#06#* Not applicable Can be used to register the device
      Android ID *#*#8255#*#* (may not work on newer devices) Not applicable Can be used to register the device
  5. Click Save
    The device displays in the list of registered devices. Note! Although the device displays in the list of registered devices immediately, it may take a few minutes to register in the system and function as intended.

 Note

There can be cases in which you want to add more than 1 identifier to your test device, for example, you want both IDFA and IDFV on the same device.

To add an additional identifier:

  1. Click Add device.
  2. Use the same name for the test device, and add the 2nd identifier.
  3. Click Save.

Guidelines for registering IDFA or IDFV to iOS 14+ test devices

Follow these guidelines when adding a test device manually:

  • Register for IDFA - do this if AppTransparency Tracking (ATT) was implemented on your app and you want to run tests as a consenting user. When launching the app for the first time, make sure to click Allow in the ATT prompt.
  • Register for IDFV - do this if you have more than 1 of your apps, besides the test app installed on the device, and one of the following applies:
    • ATT was implemented, and you want to run tests as a non-consenting user. When launching the app for the first time, make sure to click Don't Allow in the ATT prompt.
    • ATT was not implemented.

    Reason: When at least 2 of your apps are installed on a device, uninstalling and then reinstalling the test app results in the device getting the same IDFV, and the install is recorded as a reinstall. Registering the device allows the install to be recorded as a new install.

  • Don't register your device - do this if ATT was not implemented and you don't have additional apps. In this instance, probabilistic modeling is used for attribution. Each install is recorded as a new install on the test device.
    This method can help with registering repeated test installs for the same device if at least one of the following happens:
    • Reinstall detection is disabled for the app (not recommended for live apps)
    • The AppsFlyer iOS SDK is v6.8.0 or below

    • The test attribution link contains "is_retargeting=true". In this case, installs are recorded as re-attributions and are available in the retargeting dashboard and retargeting raw data reports.

Workflow_register_iOS14_device

Delete a registered device

AppsFlyerAdmin_us-en.png

A maximum of 200 devices can be registered per account. Only an admin user can delete test devices.

To delete a device from the list:

  1. In AppsFlyer, in the upper-right click on your email address.
  2. Select Test devices.
  3. Click the delete icon to remove devices.