Overview

The Postback Controls feature allows you to set up rules for automatically approving or rejecting conversions based on received variables. This is a how-to guide for building Postback Controls which are configurable for specific time windows and can be applied to all or selected Offers and/or Partners.

__________________________________________________

Use Case Examples

  • An eCommerce Advertiser has a free product offering and does not want to fire payout conversions to Partners. You could have the SKU (the internal product ID) posted back under Adv5, and reject the Postback conversion whenever Adv5 equals that SKU number.
  • You pay your partners on a RevShare, and want to automatically reject any Postbacks where the Postback purchase Amount is greater than 9999, as that is likely fraud.
  • You're promoting an Advertiser's App that is using an MMP (Mobile Measurement Partner), and that advertiser has an Anti-Fraud package. You could set up the advertiser's Postback to include those Fraud Flags under &fraud=[fraud flag]. You can then set up your Postback Control to only approve Postback conversions where the custom &fraud parameter is empty.

__________________________________________________

A How-To Guide to Configuring Postback Controls

Step #1

Navigate to Advertisers - Postback Controls and click the + Add Postback Control button.

Step #2

Designate a name and status which are required fields. You have the option to assign an effective time period and/or specific Offers or Partners to which the Postback Control applies.

If you would like to apply the Postback Control to a specific Offer or Partner, toggle off Apply to All Offers / Brands and Apply to all Partners.

Once you've selected which Offers and/or Partners to attribute the Postback Control to, click Continue.

Step #3

Fill in each field to configure the rules to follow when accepting or rejecting conversions. A rule consists of a Variable, a Comparison Method, and a Value. As you enter information, a preview will appear to summarize the rule logic you are creating.

Please note that the Timestamp variable should only be used if the parameter &timestamp=XXX is being passed into Everflow in the conversion pixel or postback, and the Custom variable will use data passed in a custom parameter, such as &first_ref=XXX.

__________________________________________________

*Pro Tips

  • When a conversion is rejected due to a Postback Control, Error Code: 26 and Error Message: Blocked_Postback_Control will be visible in the respective Error columns in reporting.
  • These rules also apply to event postbacks. For example, if the variable selected is not being passed in the advertiser postback, the rules will still work. If the event postback looks like this http://everflow-demo.servecvr.com/?nid=63&oid=3&transaction_id=86b850e639a248a289739debd6e6eadc&event_id=77 and the variable of adv1 doesn't match any of the values, this conversion will be rejected since there is no adv1, and therefore no values to match.

_________________________________________________________________

NEED HELP? OUR CUSTOMER SUCCESS TEAM IS HERE FOR YOU!

We've assembled a superstar team of industry veterans that are available around the clock to make sure that your issues are resolved and questions are answered. You can reach out any time in-platform via Chat or by emailing support@everflow.io.

Did this answer your question?