Server postback errors
Daria Mamchenkova avatar
Written by Daria Mamchenkova
Updated over a week ago

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 "validation error" and/or the error message itself.
It means that Affise accepted a postback, but didn't register the conversion due to some specific reason.

The validation errors come instead of the legacy "status:2" errors after the release of the new conversion processor (aka asynchronous postbacks).
With the asynchronous postbacks, the postback is always accepted with status 200 as successful. It means the Affise system accepted the postback and will further process it.

Validation errors

Error message

Description

How to fix

Access denied

Secure postback code was set on the offer, advertiser, 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 should pass the correct secure code via a postback with the help of the secure parameter.

Read more about secure postback code.

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.

The advertiser should pass the offer_id and pid parameters via the postback link.

Offer disabled

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

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

Read more about offer statuses.

Conversion status is not pending

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

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

Read more about conversion statuses.

Conversion exists

The advertiser sent the postback for a duplicate conversion.

The advertiser should send the postback for unique conversion.

Read more about conversion uniqueness.

Nothing to update

This conversion already exists in the system and there's nothing to update.

The conversion should not exist in the system, or there should be something to update.

Secure required when promo code is sent

The secure postback code wasn't passed.

The advertiser should pass the secure postback code in the postback.

Read more about Promo code tracking.

Promo code feature disabled

The promo code feature is not active.

Activate the promo code feature. It's available for certain plans. Read more about advanced features.

Read more about promo code tracking.

Promo code usage limit is reached

The limit on promo codes is reached.

Once the limit is reached, the system stops receiving conversions with this promo code. You should increase the promo code usage limit.

Read more about promo code limits.

Wrong offer ID

The offer ID in the postback parameter differs from the offer ID in click.

In the postback, the advertiser should pass the offer ID, which matches the offer ID in click.
In the case of pixel integration, the pixel with same offer ID could have been set up in the advertiser's site. The advertiser should remove offer ID from all the pixels.

Bad IP

It's not allowed to send postbacks from this IP.

The advertiser should change the IP to send postbacks.

Bad conversion status

Invalid conversion status passed in the postback.

The advertiser should pass the valid conversion status in the postback.

Read more about conversion statuses.

Impression attribution disabled

The Impression attribution feature is not available.

This feature is available for certain plans. To get it, you need to pay for it at first. Read more about advanced features.

Read more about VTA integration.

Offer not found

Invalid offer identifiers are passed in the parameter or there's an infrastructure failure.

In case of invalid identifiers, the advertiser should pass valid offer identifiers in the parameter.

In case of an infrastructure failure, the advertiser should try again later.

Affiliate not found

Invalid affiliate identifiers are passed in the parameter or there's an infrastructure failure.

In case of invalid identifiers, the advertiser should pass valid affiliate identifiers in the parameter.

In case of an infrastructure failure, the advertiser should try again later.

Conversion not found

Invalid conversion identifiers are passed in the parameter or there's an infrastructure failure.

In case of invalid identifiers, the advertiser should pass valid conversion identifiers in the parameter.

In case of an infrastructure failure, the advertiser should try again later.

Promo code not found

Invalid promo code identifiers are passed in the parameter or there's an infrastructure failure.

In case of invalid identifiers, the advertiser should pass valid promo code identifiers in the parameter.

In case of an infrastructure failure, the advertiser should try again later.

Conversion in pending already

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

The advertiser should send only one request to change the conversion status to Pending.

Read more about conversion statuses.

Failed to identify conversion

Such parameters were passed in the postback for which it wasn't possible to create a conversion. If the system didn't find a click, conversion, promo code, or there was broken click id, you see this error.

The advertiser should pass parameters by which the system will be able to create a conversion:
- check if click ID is correct and not broken
- check if the offer is Active
- check if promo code is correct, etc.

Also, the server postback response can contain the message without the "validation error" text. It means postback is successful, and the conversion is created, but with the decline reason.


Legacy status:2 errors


Legacy postback errors to be depreciated soon:

Error message

Description

How to fix

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 a 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.

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

Read more about VTA integration.

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 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 VTA integration.

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

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

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

Click session lifespan is expired

Click session lifespan is a period when a conversion is allowed for clicks or impressions. This period is expired.

Change the Click session lifespan settings, so that the conversion can match the offer settings.


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

Did this answer your question?