How to Exclude Cookiebot Traffic in GA4: A Step-by-Step Guide

Why You Should Filter Out Cookiebot Traffic in Google Analytics 4

If you’re using Cookiebot CMP, you might notice unexplained traffic spikes on the same day each month. These anomalies are caused by Cookiebot’s monthly domain scans, which can distort your Google Analytics 4 (GA4) reports. To maintain accurate data, you should exclude this scanner traffic from your analytics.

Step 1: Define the Cookiebot Scanner as Internal Traffic

The first step to filtering out Cookiebot traffic is identifying it as internal traffic by setting a traffic_type parameter.

How to Identify Cookiebot Traffic in GA4

1. In your GA4 Admin panel, navigate to Property Settings → Data Streams.
2. Select your web data stream.
3. Click Configure tag settings.
4. Expand the settings list by clicking Show more.
5. Click Define internal traffic and then Create.
6. Enter a descriptive name for the rule, such as Cookiebot Scanner.
7. Under traffic_type value, enter a unique identifier such as Cookiebot_scanner.
8. Under IP addresses, choose IP address matches regular expression.
9. Enter the following IP addresses used by the Cookiebot scanner:

^(20\.223\.9\.138|34\.(107\.102\.47|141\.10\.24|159\.(86\.126|168\.195|247\.222))|35\.(198\.(78\.207|137\.6|160\.49)|246\.(143\.2|191\.14)))$

Alternatively, you can manually add these IP addresses:

• 20.223.9.138
• 34.107.102.47
• 34.141.10.24
• 34.159.86.126
• 34.159.168.195
• 34.159.247.222
• 35.198.78.207
• 35.198.137.6
• 35.198.160.49
• 35.246.143.2
• 35.246.191.14

Step 2: Create a Data Filter to Exclude Cookiebot Traffic

Now that you’ve identified the scanner traffic, the next step is to exclude it from your GA4 reports.

How to Set Up a GA4 Data Filter

1. In the GA4 Admin panel, go to Data collection and modification → Data filters.
2. Click Create Filter.
3. Select Internal Traffic.
4. Enter a unique name for the filter, such as Exclude Cookiebot Scanner.
5. Choose Exclude to remove all events where traffic_type matches the identifier you created earlier.
6. Select Active as the filter state.
7. Click Create to save your filter.

Important Notes

• The data filter only applies to future traffic. It will not remove past Cookiebot scanner data.
• Regularly check your GA4 reports to confirm that scanner traffic is excluded.
• If you manage multiple domains, repeat this process for each one to ensure clean analytics.

Final Thoughts

Accurate data is the foundation of effective digital marketing. By filtering out Cookiebot scanner traffic in GA4, you can ensure that your analytics reflect real user behavior—not automated scans. If you need help optimizing your GA4 setup, Coby Agency specializes in advanced tracking, analytics, and MarTech solutions. Let’s talk about refining your data strategy today!