Time to read: 7 min.
Integration test with Advertiser
a) Once tracking URL is updated with the needed parameters & macros on Offer edit page, you can proceed with a test with Advertiser to check how postbacks are received by Affise server and whether conversions are generated.
❗ Integration test with Advertiser should be performed on Advertiser’s end. That's why generate a test link on the Offer Preview Page and share it with Advertiser:
If you use a tracking domain that allows both HTTP and HTTPS protocols, enable Use SSL option to have
https://, and disable it to have
Once the link is shared with the Advertiser, they can proceed with the Integration test on their side.
b) Below you’ll find a guide on how to make an integration test with the Advertiser:
Find your Postback URL on 'Offers' section - > 'Offer’s edit' page - > ‘Postbacks’ section - > 'Integration pixels' field:
❗ Right now we support the following samples of the default Admin domain, which is used in Affise Postback URL:
2. Update this Postback URL with all the needed parameters.
3. Share Postback URL with Advertiser and ask the advertiser to make a test on their side.
4. Once Advertiser fires a postback, you will see how it was fired in ‘Statistics’ section - > ‘Server postbacks’:
5. You can check whether a test was successful or not by checking the ‘Response’ column:
‘Status: 1’ means that Affise accepted a postback, and the conversion was registered.
‘Status: 2’ means that Affise accepted a postback, but the conversion was not registered due to some specific reason:
Press on ‘status:2’ in ‘response’ column to find out the reason:
Access denied - ‘access denied’ message means that there is a ‘secure postback code’ set on offer’s level, advertiser’s level, or platform level in the Settings. Make sure that advertiser passes or passes the correct one via a postback with the help of the &secure= parameter.
Current IP-address is denied - ‘current IP-address is denied’ message means that there is an IP whitelist set on the offer’s level or advertiser’s level. Check the IPs whitelisted and IP where a postback has come from. If they are different, make the needed changes.
Broken clickid - ‘broken clickid’ message means that Advertiser does not pass Affise client the correct clickid value. Affise unique clickid value should consist of 24 symbols. It’s passed to Advertiser via a tracking URL and passed back to Affise client via Advertiser’s postback. Check the way you have set a tracking URL for the offer and the way postback is set up on Advertiser’s side. Make sure that correct parameters & macros are set up in both cases. If this step is done correctly, refer to the Advertiser and request them to pass your Affise clickid value via a postback. Otherwise, a postback will not register correctly.
Broken impression ID - the message means, you use the view-through attribution integration. In this case you need to pass the Affise impression ID to the advertiser and get it back via the Affise postback link. If the postback link doesn't contain the Affise impression ID value, such a error appears. Learn more about the VTA integration.
Missing mandatory parameter clickid/click_id or ref_id or aimp_id - the message is received:
For pixel integration. It means that a click ID wasn't saved in cookie files. There could be many reasons for that: chain of redirects has not been initiated by Affise tracking link, a wrong domain, incognito mode, and so on.
For S2S integration. It means that mandatory parameter clickid (click_id) was not used in Affise postback link or it was used not correctly;
For VTA (view-through attribution). It means that mandatory parameter aimp_id was not used in Affise postback link or was used in a wrong way.
Missing mandatory parameters offer_id and pid - this message means that two mandatory parameters ‘offer_id’ and ‘pid’ were not used in the Affise postback link. They both are needed to identify the conversion as well as to successfully register it. It is relevant for Probabilistic Attribution only.
Offer disabled - ‘offer disabled’ message means that postbacks are sent for the offer, which has a disabled status on Affise. Notice that disabled offers are ‘closed’ for conversions.
Conversion status is not pending - 'conversion status is not pending' means that a postback for the existing conversion, which is not in pending status, was sent to change the status of conversion. Conversion's status via a postback can be changed if the conversion has been registered in 'pending' status.
Conversion exists - 'conversion exists' means that a postback for a duplicate conversion was sent. The uniqueness of conversion in Affise is defined by three categories in the following scenarios: 1) If conversion does not have 'action_id' (i.e., conversion ID) passed by the Advertiser, the uniqueness of conversion is defined by a) offer ID b) goal c) clickid. 2) If a conversion has 'action_id' (i.e., conversion ID) value passed by the Advertiser, the uniqueness of conversion is defined bya) offer ID b) goal c) action_id.
❗If the advertiser sends postbacks with different click ID, but the same action ID, conversions won't be registered. The postback will have status '2' and the comment 'Conversion exists'. The thing, that if the advertiser sends a value in &action_id=parameter, click ID will be ignored when defining the conversion's uniqueness.
❗ Find out more How Does Affise Define Click's/Conversion's Uniqueness here.
You may also find helpful the following Articles:
If you feel like there are some questions left upon the Integration Test process with Advertiser, feel free to address them to Affise Support Team via firstname.lastname@example.org or your internal live-chat as long as to contact your dedicated Account Manager.