Fraud0 currently creates three one DataLayer eventsevent 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). To keep it simple, we would advise you to use the fraud0 event only and skip the first two events:
...
When a bot is detected, the f0_event_invalid_traffic event is triggered (deprecated):
| Code Block |
|---|
{ event: 'f0_event_invalid_traffic' } |
...
When a low-quality user is detected, the f0_event_low_quality_traffic event is triggered (deprecated):
| Code Block |
|---|
{ event: 'f0_event_low_quality_traffic' } |
...
:
For both - bot and human traffic - a fraud0 event is triggered, providing information about bot traffic:
| Code Block | ||
|---|---|---|
| ||
{
event: 'fraud0',
f0_bot_traffic: 'no', |
...
|
...
} |
| Info |
|---|
Bot Traffic |
...
can have the following values: |
low = low possibility of a conversion
standard = no specific probability
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 the status of the event can change afterwards if further checks clearly indicate that a change of the bot status is required.
Need support?
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Do you still have questions or require further details? Contact our support team for assistance! |