In the Server Postbacks section, you can check the logs for the postbacks that your advertiser sent. If something goes wrong while integrating with the advertiser, you get the 'Status: 2' message. It means that Affise accepted a postback, but didn't register the conversion due to some specific reason.

Postback errors

Error message

Description

How to fix

Access denied

Secure postback code was set on the offer’s, advertiser’s, or platform level in the Settings. The advertiser didn't pass or didn't pass the correct secure code via a postback with the help of the secure parameter.

The advertiser must pass the correct secure code via a postback with the help of the secure parameter.

Current IP-address is denied

IP whitelisted on the offer’s or advertiser’s level differs from the IP, which the postback came from.

Check the IP whitelisted on the offer’s or advertiser’s level, and the IP which the postback came from. If they are different, change the IPs whitelist.

Broken clickid

The advertiser did not pass the correct clickid value. Affise unique clickid value should contain 24 symbols.

Check the way you set a tracking URL for the offer, and the way the advertiser set up the postback. Both of you can use only correct parameters & macros.

Broken impression ID

You used the view-through attribution integration, and the advertiser didn't pass the &aimp_id parameter via the postback link.

Read more about the VTA integration.

The advertiser must pass the aimp_id parameter via the postback link.

Missing mandatory parameter clickid/click_id or ref_id or aimp_id

  • Pixel integration
    A clickid parameter wasn't saved in cookie files. Read more about Pixel integration.

  • S2S integration
    The advertiser didn't pass or didn't pass correctly a mandatory clickid parameter via the postback link. Read more about the S2S integration.

  • VTA

    The advertiser didn't pass or didn't pass correctly a mandatory aimp_id parameter via the postback link. Read more about the VTA integration.

  • Pixel integration
    There are many reasons for this error. Read about how to fix them here.

  • S2S integration
    The advertiser must pass a mandatory clickid parameter via the postback link.

  • VTA
    The advertiser must pass a mandatory aimp_id parameter via the postback link.

Missing mandatory parameters offer_id and pid

You used the probabilistic attribution integration, and the advertiser didn't pass mandatory parameters offer_id and pid.

Advertiser must pass the offer_id and pid parameters via the postback link.

Offer disabled

The advertiser sent the postback for the offer, which had a disabled status on Affise.

Change the offer status to active if you want to get traffic to it.

Conversion status is not pending

The advertiser sent the postback for the existing conversion, which is not in pending status, to change its status.

The advertiser can change the conversion's status via the postback only if the system registered it in pending status.

Conversion exists

The advertiser sent the postback for a duplicate conversion. Read more about conversion uniqueness.

Advertiser must send the postback for unique conversion.

📃 Related topics


Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].

Did this answer your question?