What Bot Guard sends
Bot Guard can send bot_detected and bot_blocked events so automated activity can be compared with ordinary traffic. Depending on the event, parameters can include the security action, anonymized address information, strike count, time, and affected page. Raw visitor IP addresses are not sent to GA4.
Choose a connection
| Mode | Use it when |
|---|---|
| Use Existing Site Setup | The site already loads GA4 or GTM. Bot Guard pushes its event into the existing data layer and avoids loading a second analytics setup. |
| Custom GA4/GTM Configuration | You intentionally want a separate GA4 Measurement ID or GTM container for security reporting. |
| Data layer only | You use Custom mode but leave the optional IDs blank because an existing GTM rule consumes the Bot Guard data-layer event. |
Configure the existing-site mode
- Enable Google Analytics Tracking.
- Select Use Existing Site Setup (Automatic).
- Save changes.
- Open Testing Tools and confirm the reported setup.
- Select Test GA4 Event and verify it in GA4 DebugView or GTM Preview.
Configure a custom destination
- Select Custom GA4/GTM Configuration.
- Enter a valid
G-XXXXXXXXXXMeasurement ID, aGTM-XXXXXXXcontainer, or the specific combination your analytics design requires. - Save and reload the Settings screen to confirm the values remain.
- Send a test event.
- Verify the destination before relying on production reports.
Example: compare bot activity by landing pageIn GA4 Explorations, filter event name to
bot_detected and use page location as a dimension. Compare those pages with ordinary sessions to identify content receiving disproportionate automated traffic.What a successful test proves
A successful plugin response proves that Bot Guard queued the event through the configured connection. It does not guarantee that every GA4/GTM rule, consent configuration, browser extension, ad blocker, or analytics property accepted it. Confirm the event at the destination.
Troubleshooting
- Check that analytics tracking is enabled and the selected mode is correct.
- Validate the ID format and ensure the site does not load conflicting containers.
- Review consent-management behavior and Content Security Policy.
- Use GTM Preview or GA4 DebugView rather than waiting for standard reports.
- Remember that browser privacy tools can block client-side analytics without affecting Bot Guard’s local strikes.