Sometimes you may want to turn off visitor cookies and not use them to collect data. It could be because you want to stay compliant with some privacy laws or for other reasons.
To turn off cookies, follow these steps:
- Go to Menu > Administration.
- Navigate to Sites & apps.
- On the left, pick a site or app you want to work with.
- Navigate to Privacy.
- Ask visitors for consent needs to be turned off.
- Turn off Use visitor cookies.
- Click Save.
Note: Some triggers in Tag Manager create cookies to work correctly. If you use one of the following conditions in triggers, we’ll set a cookie:
- Event condition > Traffic source
- Event condition > Returning visitor
- Event condition > Campaign
- Event condition > External referrer
- Multiplicity > Fire tag once per session
- Multiplicity > Fire tag multiple times per session, excluding first
- Multiplicity > Fire tag once per page view
If you don’t want to use these cookies, don’t set these conditions in the trigger. More about cookies
Now we’ll show you how your data can differ after turning off cookies. We’ll also compare other options used for collecting data so that you know how combining them can affect your data.
|Cookies & session ID||No cookies||No session ID||No cookies & session ID|
|Mechanisms used to collect data|
|Visitor’s IP address||Yes / No (3)||Yes / No (3)|
|Capture all traffic|
|New vs. returning visitors|
|Visitor’s location||Latitude, Longitude, Organization, Provider, City, Region, Country, Continent||Latitude, Longitude, Organization, Provider, City, Region, Country, Continent||Latitude, Longitude, Organization, Provider, City, Region, Country, Continent||Latitude, Longitude, Organization, Provider, City, Region, Country, Continent|
|Channel attribution||Last-click, position-based, first-click, last-non-direct-click, time-decay, linear and custom models||Last-click||Last-click, position-based, first-click, last-non-direct-click, time-decay, linear and custom models|
|Compliant with||Countries without privacy laws,
|Cookie laws||Cookie laws||GDPR, UK GDPR/PECR (6), TTDSG (6)|
- Some triggers in Tag Manager set cookies to work correctly.
- We create a session ID to recognize the visitor’s session. We use it only for 30 minutes since the last event.
- You can mask IP addresses for visitors under Administration > Sites & apps > Privacy > Mask IP addresses. The IP address informs about visitor’s location. This option removes the selected number of bytes from the address before saving it to the database. Nobody will ever see the full address. Masking it can enhance visitors privacy because you won’t recognize their full location.
- Each event is a new session.
- You need to add an opt-out form (“do not sell my personal data”).
- Assuming the product is set up not to store additional device-level information like screen resolution or browser plugins. Set it up in Administration > Sites & apps > Privacy > Don’t collect visitor’s device data (on).