Frequency Capping

    Suspicious touchpoints can be detected by determining whether unusually excessive numbers of touchpoints occurred during a set time period. For example, if 10 touchpoints per minute are considered to be normal, and 15 touchpoints have been collected per minute, the last 5 touchpoints will be tagged as fraud.

    Rule Setup

    1. Navigate to [Settings]>[Fraud Validation Rules].

    2. Select the [Frequency Capping] tab and click Add a rule.

    3. Select Click or Impression as [Touchpoint].

    4. Select IP, Device, or Sub-Publisher as [Property].

    5. Enter the cap amount. Touchpoints that occur beyond the cap amount will be treated as suspicious.

    6. Set the time period. You can set 1 to 10 minutes in 1-minute increments, 10 to 55 minutes in 5-minute increments, and 1 to 24 hours in 1-hour increments.

    7. Select [Prevention Level] and click Save.

    Attention

    It is advised to start from "Prevention Level 1" and switch to higher levels after consulting with your media partner, as the prevention level setting may have a direct impact on the ad performance.

    8. Click Add a rule to add more rules. When you have added multiple rules, any touchpoint that matches at least 1 of the configured rules will be considered suspicious.

     

    Prevention Level

    Suspicious touchpoints detected by the frequency capping rules are processed according to the set prevention levels.

    When the Prevention Level is set to 2 or higher, suspected fraud events are excluded from postbacks. However, you can send them with limitations by completing the Postback settings below.

    Data included in postbacks

    • Sends Target events only: Installs (App), Deeplink Opens (App), and Deeplink Pageviews (App).

    • Sends events as unattributed.

    • Sends the identified fraud type.

    Eligible channels

    • Postbacks are sent to channels that would have received attribution if not suspected as fraud. These are channels that met all other Airbridge attribution model rules, including touchpoint priority and last-touch attribution (LTA).

    • Postbacks are sent only to channels with the Postback settings below configured.

    Postback settings

    • In the postback delivery rule, set [Attribution] to All Events

    • Edit the postback URL as follows. If using the POST method, contact your CSM or reach out through the Airbridge Help Center.

      • Add a postback parameter. Enter the parameter name specified by the channel and select {unattributedTouchpointFraudReason} as the parameter value.

      • Some channels require {unattributedTouchpointClickID} as the Click ID parameter value. Confirm with the channel.

    Reporting

    Suspicious touchpoints detected by the set rules can be viewed in your Airbridge reports and raw data export files.

    In the Actuals Report, select "Touchpoint Fraud Tag" as a GroupBy to visualize the suspicious touchpoints tagged as fraud.

    In the [App Raw Data Export], select "Touchpoint Fraud Tag" and "Fraud Tags" in the [Select Property] step to export suspicious touchpoints as a CSV file.

    • Fraud_Touchpoint_BlacklistingByServersideIP

    • Fraud_Touchpoint_BlacklistingByOverseaIP

    • Fraud_Touchpoint_ClickFrequencyCapped

    • Fraud_Touchpoint_ImpressionFrequencyCapped

    • Fraud_Touchpoint_ClickFrequencyCappedByIP

    • Fraud_Touchpoint_ClickFrequencyCappedByDevice

    • Fraud_Touchpoint_ClickFrequencyCappedSubpublisher

    • Fraud_Touchpoint_ImpressionFrequencyCappedByIP

    • Fraud_Touchpoint_ImpressionFrequencyCappedByDevice

    • Fraud_Touchpoint_ImpressionFrequencyCappedBySubpublisher

    • Fraud_Touchpoint_ClickShortLagTime

    • Fraud_Touchpoint_ClickLongLagTime

    • Fraud_Touchpoint_ImpressionShortLagTime

    • Fraud_Touchpoint_ImpressionLongLagTime