Data Layer Events

fraud0 pushes DataLayer events you can act on in Google Tag Manager, any other tag manager, or your own logic — for example, excluding invalid traffic from remarketing audiences, or firing personalized website services only for real users.

Which event should I use?

For triggers, audience exclusion, and negative-audience workflows, use f0_event_invalid_traffic. It is a clean, confirmed-bot-only signal and the simplest, most reliable event to build on.

The fraud0 event (f0_bot_traffic) is a secondary, reporting-oriented event. Reach for it only when you need a yes/no classification of all traffic — for example, the GA4 user property. It is not the recommended trigger for exclusion use cases.

---

Recommended: f0_event_invalid_traffic

When fraud0 confidently confirms a visit as invalid bot traffic, it pushes a dedicated event:

Invalid Traffic Event

{
   event: 'f0_event_invalid_traffic',
}

• Fires only for confirmed invalid bot traffic. A first, uncertain visit (for example, a brand-new visitor we have not yet seen interact) does not fire it — so what you exclude is high-confidence bot traffic.
• Ideal for audience exclusion and dedicated GTM triggers — there is no value to read, it is a bare signal you trigger on.
• Repeatable, not one-shot. There is no once-per-session or once-per-page de-duplication: the event fires at most once per pageview or single-page-app navigation, and re-fires on each subsequent page for as long as the visitor stays a confirmed bot. A confirmed bot browsing five pages produces roughly five events. Configure any GTM trigger or audience condition to treat it as a repeatable event, never a one-shot.

Don't confuse the event with a data-layer variable

f0_event_invalid_traffic is an event signal (a value of the event key), not the name of a data-layer variable and not the value read by the GA4 fraud0_traffic_status user property. That property reads f0_bot_traffic from the fraud0 event below — see the GA4 guide.

---

Secondary: the fraud0 event (f0_bot_traffic)

For both bot and human traffic, fraud0 also pushes a fraud0 event carrying a yes/no classification:

fraud0 Event

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

f0_bot_traffic values

• no -> Human User
• yes -> Bot User

Use this event when you need a classification for all traffic — most commonly to feed reporting and segmentation such as the GA4 user property. For acting on bot traffic (triggers, exclusion), prefer f0_event_invalid_traffic above.

Our invalid-traffic detection is highly reliable, and in the vast majority of cases traffic is classified clearly. Occasionally a brand-new visit cannot be classified immediately; in that case the value starts as no and updates to yes as soon as we are certain.

---

Technical details

Timing and sequence. Both events are pushed to window.dataLayer only after fraud0 has (1) collected page data, (2) sent it to the fraud0 API endpoint, and (3) received a scoring response — so the event always reflects fraud0’s classification. This happens once per tracked pageview or SPA navigation (never twice for the same page load): the fraud0 event on every response, and f0_event_invalid_traffic additionally whenever the visit is a confirmed bot. The first pageview of a session is often still uncertain and will not fire f0_event_invalid_traffic; it typically begins firing from a later pageview or navigation once fraud0 is confident, then repeats on each page after that.

Tealium sites

If your site runs Tealium (utag), fraud0 sends the result through utag.link instead of pushing to dataLayer. The event is fraud0_scoring_result, carrying is_bot and uncertain fields. Build your Tealium triggers on that event; the dataLayer events above do not fire on Tealium sites.

---

Note

Do you still have questions or require further details? Contact our support team for assistance: support@fraud0.com

---

Imprint Privacy Policy Terms & Conditions DPA