Troubleshooting Tracking Integration Issues

Image Description
Written by Luisa Woodfine Updated over a week ago

This article is written keeping AppsFlyer in mind however most of the points discussed here should be similarly applicable to other tracking methods as well.

Overview:

  1. App must be live on app/play store with latest SDK:
  2. Make sure to test the tracking SDK integration:
  3. Make sure to activate CPIDroid as partner & default postbacks:
  4. Make sure Advanced Privacy is disabled:
  5. Make sure to enable install/event postbacks:
  6. Make sure the event name is configured precisely:
  7. Check & make sure the tracking link is correct:
  8. Make sure tracking link is redirecting to app/play store:
  9. Check & make sure at least these parameters are there:
  10. Trigger conversion from SDK correctly & immediately:
  11. Check if you are getting organic/non-organic installs:
  12. Check if your pricing plan is active:

 

1. App must be live on app/play store with latest SDK:

  • After integrating the Tracking SDK into your app, please don't forget to upload your latest apk or ipa file and take it live into the Play Store or App Store. 

Important: Do NOT run campaign until your latest app is live in the Play Store or App Store.

2. Make sure to test the tracking SDK integration:

Please note that testing the integration is highly recommend, please find below some relevant official articles:-

3. Make sure to activate CPIDroid as partner & default postbacks:

Mark sure to activate us (CPI Droid) as a partner or enable postbacks for us (CPI Droid) as per the instructions given in below article:

4. Make sure Advanced Privacy is disabled:

Please keep Advanced Privacy disabled (IMPORTANT)

5. Make sure to enable install/event postbacks:

It's a very common mistake, advertiser forget to enable Install postbacks (for CPI campaign) and event postbacks (for CPA campaign)

6. Make sure the event name is configured precisely:

It's a very common mistake, advertiser either don't configure event name or leave it to default.

  • We strongly recommend to ensure & check that the even name you provided while creating CPA campaign, exactly the same event name should be configured in your tracking system.
  • Please make sure you send exactly the same event name (as provided while creating CPA campaign from your advertiser dashboard) to our event postback url.
  • If event name we receive on our event postback url is not same as the event name configured in the CPA campaign then tracking will not work.

7. Check & make sure the tracking link is correct:

Always Pull Tracking nlink from your Appsflyer Dashboard only and it should look like;

8. Make sure tracking link is redirecting to app/play store:

  • Kindly very that if tracking link is actually taking users to the app/play store after clicking.
  • You may use our inhouse Affiliate Link Tester at https://affops.io/tester to check redirections.

9. Check & make sure at least these parameters are there:

  • Make sure link contains correct app id,
  • pid=cpidroid_int and
  • clickid={click_id}
  • af_siteid={pub_id}
  • af_prt=agency_int (if you have appsflyer agency partner account)

10. Trigger conversion from SDK correctly & immediately:

Make sure the Tracking SDK triggers installs and events from the app as per the conversion flow only.

  • As for Installs, it should be triggered from SDK upon app download or open immediately.
  • As for events, it should be triggered from SDK upon user completed the certain action as defined by that event.

11. Check if you are getting organic/non-organic installs:

  • Kindly make sure you are getting organic installs recorded into your appsflyer dashboard, otherwise it's an indication that your SDK is not working correctly.

12. Check if your pricing plan is active:

  • You may have to activate/upgrade your plan on appsflyer for mobile attribution.

Was this article helpful?

0 out of 0 found this helpful

Related articles