Follow

HTTP status codes in 'Affiliate postbacks' statistic slice

Time to read: 7 min.

topic.png The article covers the following topics:

HTTP status codes description

On the Affiliates postbacks' slice, you can check the logs of the affiliates' postback, which have been sent or not sent to the Affiliates due to a particular reason: 

Annotation_on_2020-06-10_at_19-20-28.png

click__1_.png Find out more about 'Affiliate postbacks' statistic slice here

'HTTP code' column indicates the received response of the Affiliate's server.

The HTTP status code '200' in most cases means that postback has been sent and adopted by Affiliate’s platform.

Any other HTTP status code but 200 (success) generally means the postback acceptance flow was corrupted on Affiliate's end. Check the Affiliate's postback settings on your side and make sure that the set up is correct. If a postback is set up correct from your side, contact your Affiliate directly to find out the roots of the occurred error.

import.png Note, that having a Postback URL in 'Affiliate postbacks' statistic slice guaranteed means sending a Postback URL from Affise. 

Below you will find detailed description of HTTP codes when sending Affiliate postback URL. 
  • HTTP status code 200 means that a postback was successfully received by the Affiliate’s server:

unnamed__2_.png

  • HTTP status code '0' - this is Affiliates's server response code which stands for 'access rejected'. Most probably Affiliate's server has rejected the request or the request did not reach the server since the one is missing. Double-check with the Affiliates on the Postback URL setup: are there any typos, is the domain name is actually live and running.
  • HTTP status code '400' and HTTP status code '900' - 'Bad request' status response code indicates that the server cannot or will not process the request due to something that is perceived to be a client error. Check all characters, encodings, and make sure that Affiliate's server can accept them. Most probably a technical error on their end
  • HTTP status code '404' - 'Not found' status response code indacates that the Affise server did not find a current representation for the target resource or is not willing to disclose that one exists.
  • HTTP status code '500' - 'Internal server error' status response code indicates that Affiliate's server does not respond and does not accept a Postback URL on their side.

 click__1_.png Find out more about HTTP status codes here

 What can you do with error status codes?

1. First of all, you can test the Postback URL yourself to verify the status displayed in the 'HTTP code' column. To do this, copy the Postback URL and place it in the browser address bar, click 'enter' button. In the response you will see the same error as in statistics. 

import.pngThis method will work if the Affiliate's server accepts the Postback URL sent by GET method. 

Screenshot_69.png

If the error in the browser is not displayed, then the issue is resolved. It is still necessary to clarify with Affiliate why his/her server responded with error at the time. So, you can quickly transfer missing Postbacks by this manual method.

2. Secondly, contact your Affiliate directly to find out the roots of the occurred error. Check the Postback URL with your Affiliate and make sure that the Postback URL is correct and has no errors or typographical errors. 

article.pngYou may also find helpful the following articles:

If you feel like there are some questions left upon the HTTP status codes in 'Affiliate postbacks' statistic slice, feel free to address them to Affise Support Team via support@affise.com or your internal live-chat as long as to contact your dedicated Account Manager. 

Written by Anastasia Deryugina

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.