Knowledge Base/Administrator/Offers

Tracking Debugging

Alexey Zelensky
posted this on May 18, 2011 04:43

EFFECTUS provides great features for tracking debugging. If the conversion numbers and the advertiser side numbers differ, you will be able to see the reasons why.

Fired Pixels Log

This shows the history of a fired EFFECTUS pixel and whether if it has been converted or not.

  1. Go to "Edit Offer" and find the icon "Tracking Debugging"on the top right side.

    Example:

  2. In the popup, you will see the history of a fired pixel and additional details such as transaction status, pixel URL, your affiliates 3rd party pixels (if any)

    Example:

Pixel status explanations

  • Success (Transaction ID: XXX) - The transaction has been successfully converted.
  • Fail(Invalid cookie) - it could be the following reasons:
    • Offer does not support Client Side Tracking. In this case Server Side Tracking should be used
    • Conversion has NOT been initiated by EFFECTUS platform. Most likely the Advertiser has shared the conversion page with other networks also.
  • Fail (Invalid Offer ID) - The pixel code is not correct. You need to send the advertiser the correct pixel code.
  • Fail (Invalid HASH) - This is for Server Side tracking only. The HASH code is not found at the transactions DB. The Advertiser needs to check if he passes the HASH code properly.
  • Fail (Invalid HASH format) - This is for Server Side tracking only. The HASH code is incorrect. The Advertiser needs to check if the passes HASH code properly.

Why an EFFECTUS pixel is not fired?

90% of the time tracking issues happen because the EFFECTUS pixel has not been fired. Here are a few reasons why:

  • The conversion page uses a secure connection (HTTPS) but a non-secure pixel is placed.
  • The pixel is placed at the very bottom of the page and the page is not fully loading during conversion.
  • The conversion page code is broken.

See Also