Tracking Testing and Debugging

Once you set up the Conversion Tracking for your offer, it is time to check how everything works.

Go to Offers > Offer page > Link Builder. Learn more about Link Builder.

Once you get the correct tracking link, you can paste in your browser tab and visit the landing page. If everything set up correctly you will get click recorded at the Transactions > Clicks section.

Then make the conversion. If you are not a direct advertiser, ask your advertiser how you can make a test conversion. Once you made the conversion, it will be recorded in Scaleo platform at the Transactions > Conversions section.

However, quite often, during the testing, click and conversion can fail on the Scaleo platform. If you are not an experienced user or just a beginner, it can be quite difficult to understand the reason.

Anyways, don't panic. A few simple rules will help you to understand what is going on and fix an issue:

First, make sure the click is recorded in Scaleo system and user is redirected to the advertiser landing page. Go to Transactions > Clicks and see if click is there. If not, please check Transactions > Invalid Clicks page. If you have Offer status as "Active", offer targeting should be met.

Then, if click is recorded at Transactions > Clicks section, make sure the conversion is recorded on the Advertiser’s side. Only a successful conversion will generate a postback call or pixel fire. If something goes wrong on the advertiser side, he doesn't send conversion info to our system.

If the conversion is successfully recorded on the advertiser side, check whether the Scaleo postback pixel was called correctly on the Advertiser side. Go to Transactions > Advertiser Postbacks section. Do you see the information about the postback tracking pixel? In most cases system can not recognize the incorrect call call and can not assign it to any offer or affiliate. So you need to check all records there.

If the pixel call is not recognized or you can’t even find it in the log, contact your Advertiser and ask to provide you the postback log, where you can see what exactly postback/pixel was called.

If you found the postback call (or advertiser provided you one), please check it carefully. It must include the correct Click ID value in the correct place. If not, ask the Advertiser to check whether the postback is filled with the correct Click ID data.

If you cannot find any postback/pixel calls at the Transactions > Advertiser Postbacks section, most likely, the postback/pixel was not called on the Advertiser’s side. Contact your Advertiser for further assistance.

In all other cases, use Error Codes to find out the reason for the issue:

Title	Description
Incorrect Click ID	The Click ID value is not correct. Please, check the value passed in `click_id` parameter. It should be 32 characters long, alphanumeric characters. Example: 4cccfaf1aa0e855b01704864e548b4e1
Multiple Conversions are not Allowed	Received when more than one conversion happens from one click and option Multiple Conversions is set to OFF for the Goal. If you want to allow more than one conversion from the single click (recurring conversions), please go to Offer - Goals, edit the Goal and set Multiple Conversions = ON.
Wrong Cookies	This error usually happens when our tracking pixel is fired for unattributed user session. In other words, this conversion is not caused by our affiliate. Sometimes advertisers can not recognise the traffic sources and fire all available pixels for all conversions. Also, it can be cause any issues with cookies: Incognito mode is used, cookies turned off in the browser or expired.
Offer Inactive	The Offer status is set to Inactive.
Affiliate is not accepted for the Offer	The offer is not available for this affiliate. Please, check Affiliate Access in the offer details. The affiliate should be on the Allowed Affiliates list and/or should not be on the Denied Affiliates list.
Affiliate inactive	The Affiliate's status is set to Pending or Inactive. Also, it can appear because the Affiliate does not exist or has been deleted.
The cap is reached	The goal has reached the daily, monthly, or total limit set up in the Cap parameter. Please, check this parameter in Edit Goal form or in the Custom parameters.
Unique IP required	There must be a unique IP address. The Unique IPs feature is enabled in the Tracking tab of the offer.
Incorrect Offer	The Offer ID value is not correct. Please, check if the values passed in the `goal_id` and `click_id` parameters belong to the same offer. Also, it can appear because the Offer does not exist or has been deleted.
Incorrect Goal ID	The Goal ID value is not correct. Please, check the value passed in `goal_id` parameter and compare it with the active goals in the offer.
Incorrect Creative ID	The Creative ID value is not correct. Please, check the value passed in `creative_id` parameter and compare it with the active creatives in the offer.
Incorrect Source ID	The Affiliate Source ID value is not correct. Please, check the value passed in `source_id` parameter and compare it with the active source in the Affiliate’s profile.
Incorrect Link ID	The Landing Page ID value is not correct. Please, check the value passed in `link_id` parameter and compare it with the available landing pages in the offer.
Unique Track ID required	The error appears when the Unique Track ID feature is enabled for the Goal and the `adv_track_id` parameter is the same for several conversions. Please, set the function Unique Track ID = OFF in the edit form of a specific goal or use a unique `adv_track_id` for conversions.
Postback Lifetime is Expired	Click session duration, during which conversions can be made, has expired.
IP is blacklisted	The IP is on the Blacklist IPs list in the Tracking tab of the offer.
IP is not in whitelist	The IP is not on the Whitelist IPs list in the Tracking tab of the offer.
Wrong Geo	Country, region, or city is not allowed for this offer. Please, check Geolocation in the Tracking tab of the offer. Geo is on the Geo Denied list or not on the Geo Allowed list.
Device type is not allowed	The Device type is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The Device type is on the Deny list or not on the Allow list.
OS is not allowed	The OS is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The OS is on the Deny list or not on the Allow list.
OS Version is not allowed	The OS Version is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The OS Version is on the Deny list or not on the Allow list.
Connection Type is not allowed	The Connection Type is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The Connection Type is on the Deny list or not on the Allow list.
Mobile Operator is not allowed	The Mobile Operator is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The Mobile Operator is on the Deny list or not on the Allow list.
Brand is not allowed	The Device Brand is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The Device Brand is on the Deny list or not on the Allow list.
Model is not allowed	The Device Model is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The Device Model is on the Deny list or not on the Allow list.
Browser is not allowed	The Browser is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The Browser is on the Deny list or not on the Allow list.
Language is not allowed	The Language is not allowed for this offer. Please, check Advanced Targeting in the Tracking tab of the offer. The Language is on the Deny list or not on the Allow list.
At least one of new_status or new_amount params should be set	`new_status` and/or `new_amount` were not filled when the conversion status and amount were changed via postback.
Invalid new_status param value	The `new_status` value is not correct when the conversion status was changed via postback. Correct new_status: `approved`, `pending`, `rejected`, `trash`
Invalid new_amount param value	The `new_amount` value is not correct when the conversion amount was changed via postback.