Testing Re-Targeting

Before running any Re-Targeting campaigns, it is important to test the three types of re-targeting conversions both in the testing environment and live production:

  1. Test Re-engagement via App Open
  2. Test Re-engagement via Deeplinking
  3. Test Re-attribution (re-install)

IMPORTANT NOTES:

  • To test in a live production environment, request from the network to re-target your device and test with the live ad itself 
  • You must wait ten minutes between tests, since the algorithm attempts to match the click and the re-targeting conversion every ten minutes.
  • AppsFlyer begins to count launches of the app for re-targeting campaigns from the the third launch.
  • Re-targeting tracking links must contain the parameter is_retargeting=true
  • For details of how to generate a Tracking Link, click here

Re-Engagement via App Open

Re-engagement via app open must be based on ID Matching only and not fingerprinting. Device IDs must be included on the AppsFlyer tracking link allowing AppsFlyer to match this with the Device ID when the app is opened.

Available IDs include IDFA / (Hashed Sha1) IDFA, GAID and (Hashed Sha1) GAID

Testing Procedure

  1. Make sure the app is installed on your test device and has been launched at least twice
  2. Wait 10 minutes
  3. Generate a re-targeting link with your Device ID and send it to your mobile device (e.g. via email)

    Example:

    iOS: https://go.onelink.com/{app_id}?pid=retargeting_test&c=test1&is_retargeting=true&idfa={test device IDFA}
    Android: https://go.onelink.com/{app_id}?pid=retargeting_test&c=test1&is_retargeting=true&advertiser_id={test device GAID}

  4. Click the re-targeting link from your mobile device (expect to be re-directed to the store)
  5. Manually open the App via the Open button in the store or from the device launch pad
  6. You should see +1  for Re-Engagements conversion in the AppsFlyer Re-Targeting Dashboard

Re-Engagement via Deeplinking

The app is opened by the deeplink and AppsFlyer can attribute the install.

For this to work, the appropriate version of AppsFlyer’s SDK must be integrated.

NOTE: For Android apps, you must place a code on all activities, to ensure there is no route to open the app without notifying AppsFlyer.  For iOS it is sufficient to place the code on the first entry point only.

Testing Procedure:

  1. Make sure the app is installed on your test device and has been launched at least twice
  2. Generate a deeplinking re-targeting link and send it to your mobile device (e.g. via email)

Example:

https://go.onelink.com/{app_id}?pid=retargeting_test&c=test1&is_retargeting=true&af_dp=myscheme%3A%2F%2F

3.  Click the re-targeting link from your mobile device (expect to be re-directed to the store)
4.  Ensure the app is automatically launched and the relevant deeplink content served
5.  You should see +1  for Re-Engagements conversion in the AppsFlyer Re-Targeting Dashboard  

Re-Attribution (Re-Install)

Testing Procedure:

  1. Make sure the app is installed on your test device and has been launched at least twice
  2. Make sure your device is removed from the test device whitelist
  3. Uninstall the app
  4. Wait 10 minutes
  5. Generate a re-targeting link with your Device ID and send it to your mobile device (e.g. via email)

    Example:

iOS: https://go.onelink.com/{app_id}?pid=retargeting_test&c=test1&is_retargeting=true&idfa={test device IDFA}
Android: https://go.onelink.com/{app_id}?pid=retargeting_test&c=test1&is_retargeting=true&advertiser_id={test device GAID}

  1. Click the re-targeting link from your mobile device (expected to be re-directed to the store)
  2. Install and launch the app
  3. You should see +1  for Re-Attributions conversion in the AppsFlyer Re-Targeting Dashboard

 

Was this article helpful?
0 out of 0 found this helpful