Troubleshoot Broken Tracking Links

circle-exclamation

If you encounter any discrepancy in data from what you see in your internal system, you may be required to perform some troubleshooting steps. Some Discrepancies can include:

  • A flatline in the number of actions in reports.

  • For UTT: In the Browser Console, if the UTT, Identify, or Conversion tagarrow-up-right shows anything besides a 200 response code.

  • For API: If you are submitting actions to the conversions endpointarrow-up-right and the response is anything other than a 200 response code.

  • For Plugins: If you make an order using an impact.com tracking link and it does not show in your impact.com account. In the Browser Console, if the PageLoad event is showing a 400 response code, check if your site definition is correct. If there is no PageLoad event showing, reinstall the plugin.

  • For FTP: If you submitted your batch file and the actions do not show in the platform after 2 hours.

  1. Identify your tracking option.

  2. Identify the date on which the issue started.

  3. Identify if any changes were made to the UTT placed on your website that coincide with the drop in tracking data.

    • Website updates can sometimes unintentionally break your tracking integration if there is interference with the UTT. Refer to your technical integration plan to see how the tracking tags should be set up.

  4. Identify potential causes for the broken tracking link.

  1. If impact.com’s technical support is needed, contact supportarrow-up-right and include a summary of your findings from the steps above for an expedited response from our team.

Last updated

Was this helpful?