Skip to main content

Optimization Rules for Postback Decision

This article describes how the optimization rule works on the Postback Decision level

Updated over 2 weeks ago

Postback Decision

The optimization rule for Postback Decision gives you the flexibility to choose when a certain condition is not met, and how the system should decide whether the conversion will be attributed to the publisher or not. Once the rule has been set up and activated, any conversion which doesn't fulfill the created criteria will be set up as Passed or Failed based on the measurement you have selected for the rule. You can create the rules for Postback Decision with the following measurements in the Optimization section.


Rules for Postback Decision

  • Action to Action Time: If a conversion has status approved/pending, but the time between the selected Initial Event and Second Event is less than the Min Duration or greater than the Max Duration defined in the rule, the decision will be marked “Failed” and postback will not be sent to the publisher.

  • Advertiser Blocked Publisher: If any conversion is set up as approved but the publisher is blocked on the advertiser page then the conversion will be marked as "Failed" and it will not be attributed to the publisher.

  • Blacklisted Sub ID: If any conversion is set up as approved, but the publisher sub ID is blocked on the offers or advertiser page, then the conversion will be marked as "Failed" and it will not be attributed to the publisher.

  • Traffic Control: Any conversion setup as Approved but that did not follow the Traffic Control configuration, will be marked as "Failed" and will not be attributed to the publisher.

  • Budget Reached: If any conversion is set up as Approved/Pending but the publisher budget or offer soft budget has been fulfilled then the conversion will be marked as "Failed" and not be attributed to the publisher.

  • Click to Install Time(CTIT): If any conversion is setup as approved/pending but the time between click and conversion is less or more than the Optimization rule which has been set up and activated then the conversion will be marked as "Failed" and it will not be attributed to the publisher.

  • Click to Action Time(CTAT): If any conversion is setup as approved/ pending but the time between click and Event is less or more than the Optimization rule (i.e. does not fall in the time threshold) which has been set up and is activated then the conversion will be marked as "Failed", and it will not be attributed to the publisher.

  • Click to Default Action Time(CTDAT): If any conversion is set up as approved/ pending but the time between click and Default Event is less or more than the Optimization rule (i.e. does not fall in the time threshold) which has been set up and activated then the conversion will be marked as "Failed" and it will not be attributed to the publisher.

  • Inactive Offer: If any conversion setup as Approved/Pending but the offer is not active anymore then the conversion will be marked as "Failed" and it will not be attributed to the publisher

  • Private Event: If any conversion is set up as approved but the event type is set up as private on the offer details page then the conversion will be marked as "Failed" and it will not be attributed to the publisher.

  • Publisher Not Approved: If any conversion setup as Approved/Pending but the publisher is not approved in the offer details page anymore then the conversion will be marked as "Failed" and it will not be attributed to the publisher

  • Random Evaluation: Any random conversion (paid, or not paid) will be marked as "Failed" and it will not be attributed to the publisher based on the percentage inserted in the form. See below for more details on configuring this rule.

  • Rejected Postback: Any conversion setup as rejected will be marked as "Failed" and it will not be attributed to the publisher

Deleting a Rule

If you delete an optimization rule (even if it is active) it is considered as deactivated.

Random Evaluation Fields

Below you will find a description for each of the fields or thresholds you can utilize when configuring a Random Evaluation Optimization Rule.

  • Chance - The percentage of total Approved conversions will be marked as failed because of random evaluation and not pass to the publishers.

  • Event Types - A selected event can be chosen if any specific offer is selected, but if nothing is selected, then all events are considered.

  • Threshold - The rule does not apply if the given amount of conversions were not yet achieved on the respective rule.

    • 💡 Note: If the rule contains multiple advertiser/ offer/ publisher combinations, then the threshold applies to their combined traffic (and not individually). Also, deleting and re-creating a rule will reset the threshold.

  • Threshold Reset - Set whether the threshold resets Daily or Total.

    • Daily requires the given threshold amount of conversions are archieved each day before the random evaluation rule is applied

    • Total only requires the given threshold amount of conversions are achieved once before the random evaluation rule is applied

  • Batch Size - When using the non-randomized chance, postbacks will be evaluated in batches of the given size.

    • For example, if chance is 50% and batch size is 2, then one postback will be passed, afterwards one will be failed.

    • You need to disable Randomize to edit the batch size value.

  • Randomize - When selected, the Chance is applied randomly.

    • For example, if you set it to 20% out of 10 conversions 2 random ones will be failed (e.g. the second and seventh). If not selected, the first eight will be passed, the next two will be failed.

  • Trigger only on paid postbacks - Whether it is Triggered only on paid postbacks or all postbacks.

Did this answer your question?