Skip to main content

How to Exclude CookieYes from Google Analytics Data

Last updated on July 5, 2024

Integrating CookieYes on your website might lead to an increase in traffic within your Google Analytics [GA4] data. CookieYes scanner visits each page on your website to identify the cookies and trackers being utilised. By excluding CookieYes-related traffic, you ensure that your Google Analytics reflect genuine user interactions, providing a more accurate picture of website traffic and performance.

This involves identifying and removing specific traffic segments associated with CookieYes’s consent management, thus ensuring your analytics truly represent user interactions.

Before you proceed with the steps, enable static IP scanning for your domain.

Note: Static IP scanning will be available only for users on the Ultimate plan.

How to Exclude CookieYes from Google Analytics Data

To exclude CookieYes traffic from your Google Analytics data, you first need to identify the sources of that traffic and then create a filter to remove it. Follow the below steps to exclude CookieYes-related data from Google Analytics Reports of your website.

To identify internal traffic and create, edit, or delete data filters, you must have the Editor role assigned to you at the property level in Google Analytics.

Step 1: Create CookieYes Traffic

1. Log into Google Analytics [GA4] and navigate to Admin from the left sidebar.

2. In case you have multiple accounts, verify you are in the correct Google Analytics account and property before proceeding.
3. In Admin, under Data collection and modification, click Data streams.

4. Click the web data stream.

The Web stream details modal appears.
5. In Web stream details, click Configure tag settings.

6. In the Google Tag Configuration modal, click Show More and select Define internal traffic.

7. Click the Create button to create internal traffic.

8. In the Create internal traffic rule modal, enter the following fields:

a. Enter a name for the rule. Here we’ve named it CookieYes Filter.

b. Enter traffic_type value, e.g. CookieYes_traffic.

c. In IP addresses > Match type, select IP address equals from the drop-down.

d. In IP addresses > Value, enter one of the IP addresses from below

  • 3.248.28.214
  • 54.77.122.154

e. Click Add condition, and add the other IP address. All IP addresses that match the conditions will be marked as internal traffic.

9. Click Create.

The preview should look like this:

Step 2: Create Data Filter

1. Navigate to the Admin Page.
2. In Admin, under Data collection and modification, click Data filters.

3. Click Create Filter.
This creates a new data filter to exclude the required data from reports.

4. Choose Filter Type as Internal traffic.

5. In the ‘Create data filter’ modal, enter the following fields:

a. Enter a Data filter name. Here we’ve named it CookieYes Data Filter.
b. Choose Exclude under Filter Operation to filter out events.
c. For the Parameter value, the value of the traffic_type parameter should match the name you entered while creating the internal traffic rule, e.g. CookieYes_traffic.
d. 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.

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. You can view this test data in Explore to validate that the filter is working correctly before activating it.

6. Click Create.
The preview should be similar to this:

Step 3: Testing the 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]”

Note: A data filter can take between 24 – 36 hours to apply. Check back later if no value is assigned.

Have more questions?

Reach out to us and we'll answer them.

Contact us