An Advertiser postback is when your Advertiser sees a conversion from a click generated from your tracking link, they send that successful conversion data to your Advertiser Postback so that it can be tracked in your Everflow instance.
​
In the diagram below, *you* are the Network:

You may want to provide your Advertiser with a Global Postback URL, which can be used for any/all Offers using Server Postback (S2S) as the Conversion Method. Please note that a Global Postback URL for Events does not exist - this is ONLY for Base Conversions.

To locate your advertiser postback for an offer we recommend using the Postback found on the Offer page, as it helps with confirming that the Conversion Method and Revenue & Payout settings are properly defined. If they are not defined properly, the Postback shown here will be incomplete or incorrectly formatted.

Please note that the drop-down defaults to the Base Conversion. You can find the Event Postbacks by selecting the Event from the drop-down menu.

Receiving a dynamic sale amount goes as follows, for Offers using Revenue and Payout types such as RPS (Revenue Per Sale) / CPS (Cost Per Sale), the amount received is used for calculating the Partner Payout. For example:

If you want to receive a dynamic sale amount for each conversion, you will need to
append &amount= to the postback. Please note that the Postback URL provided on the Offer page will include this parameter automatically if the defined Revenue & Payout settings require a sale amount for these calculations.

You will need to either:

In either case, the TRANSACTION_ID placeholder should be replaced by your Advertiser click ID macro. This macro varies depending on the Advertiser and their platform, which is why we use placeholders as shown here:

https://YourDomain.com/?nid=YOUR_NID&transaction_id=YOUR_ADVERTISERS_MACRO_FOR_CLICK_ID&amount=YOUR_ADVERTISERS_MACRO_FOR_SALE_AMOUNT

You can test your Advertiser postback once the postback is implemented on the Advertiser side, you can ask your Advertiser to fire a conversion to test the postback integration using an Advertiser Test Link.

If you're having issues testing the Advertiser Postback, here are a few troubleshooting steps to verify:

For example, if your Advertiser gives you the tracking link:

https://advertiser.com?s1=CLICK_ID

then your Base Destination URL will look like this:

https://advertiser.com?s1={transaction_id}

and your Postback implemented on their side will look like something like this:

https://YourDomain.com/?nid=YOUR_NID&transaction_id={s1}

If the Advertiser or MMP wants to fire conversions into Everflow without an associated Transaction_ID (i.e. click), the Postback must include the Offer ID (oid) and Affiliate ID (affid).

https://YOUR_DOMAIN.com/?nid=YOUR_NID&oid=OFFER_ID&affid=AFFILIATE_ID

When discussing Fraud Flags for mobile MMP campaigns, you can add additional parameters for receiving relevant fraud indicators. This allows the MMP or the Advertiser to send you data when the conversion is deemed fraudulent on their side so that you are able to identify and block those conversions and traffic sources via SmartSwitch.

Append the following parameters to the Advertiser Postback: &fraud_code=&fraud_flag=&fraud_reason=

When the conversion received includes &fraud_flag=1, then the conversion will be rejected. When fraud_flag=0, the conversion is considered non-fraudulent and nothing will be passed under fraud_code. Additional non-mandatory parameters outlining the reason may be passed under fraud_reason.

&adv1= Advertiser Sub ID 1
​&adv2= Advertiser Sub ID 2
​&adv3= Advertiser Sub ID 3
​&adv4= Advertiser Sub ID 4
​&adv5= Advertiser Sub ID 5

&amount= Sale amount (will be used in a context of RPS)
​&timestamp= Unix timestamp of the action (i.e. install) in the Advertiser system. This will override the timestamp displayed in Everflow.
​&order= Specific to e-commerce integration, JSON payload associated to the order
​&user_ip= The IP of the user to be passed in to the Conversion IP field in Everflow. In the absence of this value being passed, the conversion IP will be the IP of the server which fired the conversion.
​&order_id= The order ID specifically for e-commerce.

&email= The email address used during the order, specifically for e-commerce.
​&currency= The currency of the sale, this will be converted automatically into the currency set at the account or offer level. You can include the 3 letter ISO acronym as the currency parameter in the postback. Please see here for details on ISO codes. (i.e ...&currency=USD). When adding the currency to the SDK, please use the parameters object inside the EF.conversion() method to pass it as a string. For information on currency configurations - [Click Here]

&oid= Used to generate a clickless conversion, this is the offer ID.

&advid= Advertiser ID

&aid= Advertiser ID

&affid= Used to generate a clickless conversion, this is the affiliate ID.
​&coupon_code= Coupon code or discount code used. This can be used to generate a clickless conversion, please see this documentation.
​&source_id= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the source ID to register that to reporting.

&sub1= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the sub1 to register that to reporting.

&sub2= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the sub2 to register that to reporting.

&sub3= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the sub3 to register that to reporting.

&sub4= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the sub4 to register that to reporting.

&sub5= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the sub5 to register that to reporting.
​&idfa_sha1= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the idfa_sha1 to register that to reporting.

&google_aid_md5= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the google_aid_md5 to register that to reporting.

&google_aid_sha1= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the google_aid_sha1 to register that to reporting.

&android_id= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the android_id to register that to reporting.

&android_id_md5= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the android_id_md5 to register that to reporting.

&android_id_sha1= (clickless) When generating a clickless conversion with the coupon code or offer ID/Affiliate ID combo this can be used to pass the android_id_sha1 to register that to reporting.