Skip to content
Knowledge Center

Data Layer Events

fraud0 creates one DataLayer event which can be used for a GTM setup but also for other tag managers as well as own logic (e.g., use personalized website services only for real users):

For both - bot and human traffic - a fraud0 event is triggered, providing information about bot traffic:

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

f0_bot_traffic

Section titled “f0_bot_traffic”

Bot Traffic can have the following values:

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

In general, our invalid traffic detection works very well and reliably. In 99% of cases, the traffic can be clearly assigned. Nevertheless, it is possible that, from a technical point of view, an assignment is not fully possible. In all other cases, the status of the event will change to yes/ no as soon as we are certain.

f0_event_invalid_traffic

Section titled “f0_event_invalid_traffic”

When fraud0 classifies a visit as invalid bot traffic with a confirmed result, it pushes a separate event for negative-audience use cases:

Invalid Traffic Event
{
   event: 'f0_event_invalid_traffic',
}
  • event: 'f0_event_invalid_traffic' is only pushed for confirmed invalid bot traffic
  • This event can be used for audience exclusion or dedicated GTM triggers

Enhanced Technical Details for Data Layer Events

Section titled “Enhanced Technical Details for Data Layer Events”

Event Timing and Sequence

The fraud0 event is dispatched to window.dataLayer only after the following sequence:

  1. Data collection is completed.
  2. The collected data is sent to the fraud0 API endpoint.
  3. A TrackingResponse is received from the fraud0 API.

This ensures that the event contains the classification returned by fraud0.

Structure of the fraud0 Event

The primary event pushed to the data layer has the following structure:

fraud0 Event
{
   event: 'fraud0',
   f0_bot_traffic: 'no',
}
  • event: Denotes the name of the event, which is ‘fraud0’.
  • f0_bot_traffic: Indicates whether the traffic is identified as bot traffic (‘yes’) or not (‘no’).

If the traffic is confirmed invalid bot traffic, fraud0 also pushes:

Invalid Traffic Event
{
   event: 'f0_event_invalid_traffic',
}
  • event: Denotes the dedicated invalid-traffic event name f0_event_invalid_traffic.
Imprint Privacy Policy Terms & Conditions DPA