Using Cookiebot on your website might cause a high amount of traffic to show up in your Google Analytics data. This is a normal behavior, as our scanner will visit every page on your website to determine which cookies/trackers are being used on the website.
Before you begin
You need the Editor role at the property level to identify internal traffic and create, edit, and delete data filters.
How to exclude Cookiebot traffic from showing up in your Google Analytics data.
1. Define Cookiebot traffic
- In Google Analytics, click Admin.
- Make sure you are in the correct account and property.
- In the Property column, click Data Streams.
- Select a Web data stream.
- In the web stream details, click Configure tag settings.
- Click Show all.
- Click Define internal traffic.
- Click Create.
- Enter a name for the rule.
- Enter
Cookiebot_traffic
for thetraffic_type
parameter. - In IP addresses > Match type, select
IP address equals
- in IP addresses > Value, enter one of the IP addresses from the list below.
- 13.74.44.241
- 40.91.211.73
- 52.232.29.198
- 23.100.63.22
- 40.118.23.197
- Click Add Condition and repeat step 12 for each additional IP.
- Click Create.
Create a data filter
- In Google Analytics, click Admin.
- Make sure you are in the correct account and property.
- In the Property column, click Data Settings > Data Filters.
- Click Create Filter.
- Choose Internal traffic.
- Enter a name for the data filter
- Choose Exclude to filter out events where the value of the
traffic_type
parameter matches the name you entered in step 10 above (Cookiebot_traffic
). - Choose from the following filter states:
- Testing: Analytics identifies matching data with the "Test data filter name" dimension
- Active: Analytics applies the data filter to incoming data and makes permanent changes
- Inactive: Analytics isn't evaluating the filter
Note: Your data that satisfies a test data filter is assigned to the "Test data filter name" dimension and given a value of the filter name. That data is available in Explore so you can validate your data filters before you activate them. Learn more - Click Create.
Testing a data filter
Testing a data filter ensures it's successfully filtering out traffic from the IP addresses. Traffic from filtered IP addresses is added to the "Test data filter name" dimension with the filter name as the value.
To find events triggered by a filtered IP address, you can build a free-form exploration with these settings:
- Technique: Free form
- Rows: Test data filter name, Event name
- Values: Event count
- Filter: "Test data filter name contains [the name of your data filter]"
A data filter can take between 24 - 36 hours to apply. Check back later if no value is assigned.
Comments
0 comments
Please sign in to leave a comment.