1. Knowledge Base
  2. Solution home
  3. Trackier Performance
  4. Advertisers

Conversion from advertiser not recorded?

If your conversion is not recorded on Trackier do not panic, we got your back, below are the possible troubleshoots you can try.


TABLE OF CONTENTS



Step 1: Select the Advertiser and Open Debug Postback page

To start with troubleshooting go to Advertiser > Debug Postback. Once you get there select:

  • An advertiser with whom you got an Issue.
  • Date range in which postback is fired from the Advertiser's end.




Step 2: Error Message And Possible Solution

  • In this section, you can check the Error message appearing in the Debug Postback and take action accordingly to resolve it on your own.



INVALID_CLICK_ID



Case 1: When you can see the Click ID in the Click ID column

Reason: Click doesn't belong to the Trackier platform, advertiser tried to manually fire postback with a random click ID
Debug
  • Copy the click ID and search in the click log if you don't find that then it is confirmed that it doesn't belong to us.
  • Make sure the security token matches the postback you have shared.
    Solution
  • Ask Advertiser to do a postback test with the system and don't use random or old click id to fire postback.
  • Ask the advertiser to use the correct postback with the correct security token.

Case 2: No click id in Click id column, instead there is some random parameter

Reason: Advertiser is not passing us correct Click ID in Postback via correct Macro or we are sending Advertiser Trackier Click ID in the wrong parameter.
Debug
  • Check In which Parameter you are passing Advertiser Trackier Click Id and confirm with Advertiser if that is the right parameter
  • Confirm with Advertiser through which macro they are passing us Click ID back in the postback.
    Solution
  • Correct if you are using the wrong advertiser Parameter in Advertiser Tracking Link.
  • Make sure the Advertiser is passing back to us the click id using the correct macro, it should be the same in which we are sending them Trackier Click ID.


DUPLICATE_CLICK_ID


Reason: When you are tracking multiple conversions from the same click id and you have not enabled the option to track multiple conversions or Goal


Debug: 

  • If you want to track multiple-goal conversion from same click id then you need to enable the option in particular goal to " track multiple-goal from same click ID"
  • If you want to track Multiple conversions from the same click id, enable the option for the same in Campaign Settings.

Solution:  you can use any one of them.

  • Add txn_id=UNIQUE_ID, where UNIQUE_ID/ LEAD_ID needs to be replaced by your advertiser if they don’t have any macro for that, use RANDOM in postback.
  • Enable the option to track multiple conversions from the same click id.



INVALID_SECURITY_TOKEN


Reason: You have shared the wrong postback to the advertiser.


Debug: Make sure the security token in the error log matches with the Advertiser level Global postback.

Solution: Share the correct Advertiser Postback and run the test again.




INVALID_GOAL_VALUE


Reason: 

  • In the case of the MMP partner, you have created a goal with the wrong goal value which is available on the MMP partner panel as an event identifier name.
  • In the case of normal postback, you have shared the wrong goal_value in a postback with the advertiser.


Debug

  • MMP Partner: Ask the advertiser the Goal value for each goal that they will be sent to us.
  • Normal Postback: Check what goal you have created in the campaign.

Solution: 

  • Create a goal with the same goal value which is on the MMP partner.
  • Check whether you have passed the correct goal_value in the postback.



Step 3: When it is Success?

  • If you find "  – –  " it means there is no Error and everything is working fine. You did a great job!

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article