Postback Controls: A rule-based system for accepting and blocking postback fires : Helpdesk

Postback Controls: A rule-based system for accepting and blocking postback fires

Overview

The new Postback Controls concept allows you to set up rules for automatically approving or rejecting conversions based on received variables. Postback Controls are configurable for specific time windows and can be applied to all or selected offers and/or partners. Please note that this feature is currently only accessible to network admins.

Use Case Examples

1) 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.

2) 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.  

3) 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.

How-To Guide

Step 1

Postback Controls can be found in Advertiser - Postback Controls

Step 2

You will be taken to this screen.

Select a status, effective between time period (optional), and the Offers and/or Partners to which the Postback Control applies.

Step 3

Fill in the each field to complete the rules for Postback Controls 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.

1. Configure Control Type

Create a rule which either: accepts conversions based on specific variables or rejects conversions based on specific variables. 

2. Define Condition

If more than one rule will be created, it is important to define whether all rules must match or only one of the rules must match for the Postback Control to activate. 

You can configure the control so that all rules must match (using the 'AND' operator), 

OR so that at least one rule must match (using the 'OR' operator).

3. Create Rule(s)

Choose the Variable (adv1, adv2, adv3, adv4, adv5, amount, order or timestamp) or create a custom Variable to associate with a specific Comparison Method and Value, both of which will be defined in next steps.

Choose the Comparison Method by which the approval or rejection logic analyzes the variables and associated values. Possible Comparison Methods include but are not limited to "begins with", "contains", "does not contain", "equals". Please note that each Comparison Method has a character limit for its associated Value, which will be defined in the next step. 

Enter associated Value(s) by line which are analyzed in relation to the chosen Variable(s) via the Comparison Method. Please note that Value should left blank if the associated Comparison Method selected is "Empty".

Pro Tip: The Preview on the right is the best way to make sure you’ve set up your rules correctly.
Once you 'Save', you will be taken to a summarized list which includes the status and last modification date for each Postback Control configured.

Reporting: How To See If A Postback Is Blocked

When a conversion is rejected due to a Postback Control, a message with the ID of the Postback Control is added to the notes section in conversion reporting.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.