Injection Prevention

    Injection Prevention blocks click injection, a type of ad fraud that only occurs on Android devices. Click injection inserts fake touchpoints after an app is installed but before the app opens for the first time, stealing credit for the install.

    Injection Prevention uses touchpoint timestamps and app installation timestamps collected through the Google Play Install Referrer API and Airbridge SDK to identify fraudulent touchpoints and block click injection. Therefore, it cannot block click injection when apps are installed outside the Google Play Store or when Install Referrer data is not collected for other reasons.

    Fraud Validation Rules

    Injection Prevention identifies fraudulent touchpoints based on their timestamps. The typical flow and timestamps recorded during an app installation are as follows:

    1. The user opens the Google Play Store. At this point, referrerClickTimestampSeconds is recorded.

    2. The user clicks the “Install” button in the Play Store. At this point, installBeginTimestampSeconds is recorded.

    3. App installation is completed on the user’s device. At this point, systemInstallTimestamp is recorded.

    4. When the user opens the app for the first time, the Airbridge SDK is activated and an Install (App) event occurs. At this point, eventTimestamp is recorded.

    Injection Prevention considers the moment a user clicks “Install” button in the Google Play Store as the moment they decided to install the app. Therefore, touchpoints occurring before the “Install” button click are considered valid, while touchpoints occurring after the button click are identified as fraudulent.

    However, touchpoints occurring more than 30 days after installation is completed are not identified as fraudulent. This is because if a user installs the app but doesn’t open it for an extended period, then opens it for the first time after a new touchpoint occurs, that touchpoint may have driven the user to open the app.

    Settings

    Go to [Settings]>[Fraud Validation Rules]>[Injection Prevention] to configure the default settings and the settings by channel.

    Default Settings

    Note

    For Airbridge Apps registered with Airbridge before October 23, 2024, the Default Settings for both Click and Impression will be automatically enabled with the prevention level set to "Level 3."

    The default settings apply to all channels that do not have customized settings. The events that are attributed to the suspicious touchpoints will be processed according to the set prevention level.

    1. Switch on the toggle for click or impression, or both, depending on how you want to set the rule.

    2. Select the [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.

    Settings by Channel

    Customized settings apply only to specific channels. The default settings don't apply to channel with customized settings. Note that the customized settings can be configured for only non-SAN channels. The events that are attributed to the suspicious touchpoints will be processed according to the set prevention levels.

    1. Click Add a rule.

    2. Select a channel. The customized settings can be configured for non-SAN channels only, and therefore, the SAN channels and custom channels won't appear in the search bar.

    3. Switch on the toggle for click or impression, or both, depending on how you want to set the rule.

    4. Select [Prevention Level] and click Save.

    Prevention Level

    Events attributed to the suspicious touchpoints detected by the injection prevention rules are processed according to the set prevention levels.

    #{"width":"100px"}

    Prevention Level

    #{"width":"200px"}

    Description

    Level 1: Tag as fraud

    - Events attributed to the suspicious touchpoints will be tagged as fraud in the Airbridge reports and raw data export files.

    Level 2: Don't send postbacks

    - Events attributed to the suspicious touchpoints will be tagged as fraud in the Airbridge reports and raw data export files.

    - Events attributed to the suspicious touchpoints won't be sent as postbacks.

    Level 3: Don't attribute

    - Events attributed to the suspicious touchpoints will be tagged as fraud in the Airbridge reports and raw data export files.

    - Events attributed to the suspicious touchpoints won't be sent as postbacks.

    - Events attributed to the suspicious touchpoints won't be attributed or aggregated.

    Reporting

    The events attributed to the suspicious touchpoints detected by the set rules can be viewed in your Airbridge reports and raw data export files.

    このページは役に立ちましたか?

    ご質問やご提案はありますか?