EF Helpdesk

Postback Controls provide automated conversion management through customizable rules and timing controls, allowing networks to accept, reject, or hold conversions based on specific criteria and schedules.

Overview

The Postback Controls feature allows you to set up rules for automatically approving, rejecting, or holding conversions based on received variables.

This is a guide for building Postback Controls, which are configurable for specific time windows and can be applied to all or selected Offers and/or Partners.

Key Terms

Review these postback-related terms before diving in:

➔ Postback Controls: A system for automatically managing conversions based on predefined rules and criteria.
➔ On Hold Conversions: A feature that enables networks to fire conversions with a preset timer, determining when the conversion becomes realized. This mechanism ensures conversions are created and become payable at the right time while providing visibility on future conversions.
➔ Control Type: Determines how conversions are handled (Accept/Reject/On Hold).
➔ Rule Variables: Parameters used to evaluate incoming conversion data.
➔ Effective Period: The timeframe during which a postback control is active.

Setting Up Postback Controls

General Configuration

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

Fill in the required fields: Name, Status (Active/Inactive), Effective Between (Always On or Set Specific Period), Control Type (Accept/Reject/On Hold).

On Hold Control Type:

When selecting On Hold as the Control Type:

A hold period configuration appears.

Select the time unit (Seconds, Minutes, Hours, Days, or Weeks).

Enter the duration number.

The system will hold Conversions for the specified period before releasing them.

Rules Configuration

Choose application criteria:

Apply to all Postbacks or specific ones.

Select specific Offers, Advertisers, or Events.

Choose specific Partners from the available list.

Build Rules:

Set Condition (All Must Apply/One Or More Must Apply).

Configure Variables, Comparison Methods, and Values.

Add multiple rules by clicking the Rules button.

Use Cases

E-commerce Fraud Prevention

An eCommerce Advertiser with a free product offering can prevent unwanted partner payouts by setting up a rule where the SKU (posted back under Adv5) triggers automatic rejection when it matches the free product's ID.

RevShare Protection

For RevShare partnerships, set up automatic rejection of Postbacks where the purchase Amount exceeds 9999 to prevent potential fraudulent transactions.

App Promotion with Fraud Detection

When promoting an App using an MMP (Mobile Measurement Partner) with Anti-Fraud capabilities, configure the advertiser's Postback to include Fraud Flags under &fraud=[fraud flag]. Then set up Postback Controls to approve conversions only when the custom &fraud parameter is empty.

Quick Tips

View Postback Control edit history in the conversion report by clicking the three vertical dots at the row's end and selecting History.
Rejected conversions due to Postback Controls will show Error Code: 26 and Error Message: Blocked_Postback_Control in reporting.
Rules apply to event postbacks even when variables aren't passed. For example, if a postback URL like http://everflow-demo.servecvr.com/?nid=63&oid=3&transaction_id=86b850e639a248a289739debd6e6eadc&event_id=77 doesn't include an adv1 parameter, and your rule requires adv1, the conversion will be rejected.
When using On Hold Conversions, you can set up a default rule (e.g., "Adv1 / Does not contain / random_value_I_will_never_use") if you want the hold period to apply to all conversions.

The Timestamp variable should only be used when the parameter ×tamp=XXX is included in the conversion pixel or postback. The Custom variable works with data passed in custom parameters, such as &first_ref=XXX.

Did This Help You Today?

Yes

Next in This Series

Lorem Ipsum Dolor Sit

Overview

Setting Up Postback Controls

Use Cases

Quick Tips

Looking for extra support?