Skip to content
Knowledge Center

Step 5 — Verify & Connect

5.1 Verify the Main Tag is firing

Section titled “5.1 Verify the Main Tag is firing”

Open your website in a fresh browser tab and run through these checks.

  1. Open DevTools → Network tab.

  2. Reload the page.

  3. Filter for fraud0 in the request list. You should see at least two requests:

    • fz.js?cid=... — status 200, content-type application/javascript
    • pixel?cid=...&cb=... — status 200 or 204, type image

  4. Open the Console and type window.dataLayer. Within a few seconds you should see an entry like {event: "fraud0", f0_bot_traffic: "no"}.

  5. Log in to your fraud0 dashboard → Implementation → Health check. The status should turn green within minutes of the first page load.

If any of these checks fails, see the Onsite FAQ — Technical Queries section for troubleshooting guidance.

5.2 Set up the GTM variable and trigger

Section titled “5.2 Set up the GTM variable and trigger”

Even if you embedded the Main Tag directly (Variant B), you should still set up a GTM variable and trigger on the fraud0 data-layer event — this is what later lets you exclude bots from your ad-system pixels.

fraud0 data layer event
{
  event: 'fraud0',
  f0_bot_traffic: 'no'
}

  1. Create a Data Layer Variable

    Go to your Google Tag Manager Workspace → Variables → New (under User-Defined Variables).

    Setup Variables in GTM

    Set the Variable Configuration to Data Layer Variable. Name the variable DLV f0 and set the Data Layer Variable Name to f0_bot_traffic.

    Configure DLV

  2. Click Save.

  3. Create a Trigger

    Navigate to Triggers → New.

    New trigger

    Select Custom Event as the trigger type.

    Custom event trigger

    Name the trigger f0 Bot Traffic Trigger. Set:

    • Trigger Type: Custom Event
    • Event Name: fraud0
    • Fire on: Some Custom Events
    • Condition: DLV f0 equals yes

    Trigger conditions

  4. Click Save.

For more detail on the fraud0 data layer event, see Data Layer Events.

5.3 Connect your ad systems

Section titled “5.3 Connect your ad systems”

Once the Main Tag is verified and the GTM trigger is in place, connect at least one ad system so fraud0 starts protecting your spend.

Google Ads Fastest path to value — Automatic IP Blocking and Audience Exclusion.
Meta Ads Connect fraud0 with Meta Ads.
DV 360 & CM 360 Connect fraud0 with Display & Video 360 and Campaign Manager 360.
Microsoft Advertising Connect fraud0 with Microsoft Advertising.
Criteo Connect fraud0 with Criteo.

5.4 Optional: Pixel Protect

Section titled “5.4 Optional: Pixel Protect”

Once the Main Tag and at least one ad system are connected, Pixel Protect lets you go a step further — conditionally fire other pixels (retargeting, personalisation, session-based tools) only for verified human traffic, saving per-session costs and improving algorithmic optimisation.

Pixel Protect Conditionally fire other pixels only for verified human traffic.
Imprint Privacy Policy Terms & Conditions DPA