As long as your Consent Management Platform (CMP) is correctly configured to work with Google® Consent Mode (all of them are), OneView will automatically respect the user’s consent.
This page is meant as a guide for OneView customers to understand what consent is required to use OneView to achieve both world-class data quality and regulatory compliance.
OneView uses the Google® Consent Mode framework to understand your users’ consent, which uses a series of properties to understand the user’s consent status.It is automatically set by your Consent Management Platform (CMP) or your own implementation.This guide will follow both ePrivacy and GDPR concerns, and help you understand what consent is required for each.
Property
Description
Effect when granted
Effect when denied
analytics_storage
User consents to store or access data for analytics purposes
✅ OneView processes event data
❌ OneView discards event data
ad_storage
User consents to store or access data for advertising purposes
✅ OneView will send Conversion API if the event is a Conversion Event
❌ OneView will not send Conversion API
ad_user_data
User consents to store or access personal data for advertising purposes
✅ OneView will add Personal Data (if available) to Conversion API
❌ OneView will not add Personal Data to Conversion API
ad_personalization
User consents to store or access data for ad personalization purposes
✅ OneView will flag ad personalization as true (if available for Media Partner)
❌ OneView will flag ad personalization as false
Based on the data received via OneView, your Media Partners will be able to re-identify your Data Subjects across to improve campaign performance on their platform.
Can OneView work without a cookie banner?
OneView can work without a cookie banner, but with special considerations:
In most countries, without any additional consideration.
In other countries, depending on their specific privacy laws.
EU considerations
There are many cookieless analytics services that claim to work without a cookie banner, regardless of the jurisdiction. They mostly work by either:
fingerprinting (which is both considered equivalent to cookie-based tracking under ePrivacy, and actively prevented by major browsers, including Safari)
tracking users with an overly indulgent interpretation of ePrivacy, built on non-legally binding opinions, listed below.
Unfortunately, based or article 5.3 of ePrivacy, which itself is implemented by each member state’s local Data Protection Authority, as a general rule, it is the very act of accessing browser data for non-strictly-necessary purposes, that requires consent.There are some notable exceptions (e.g. Italy), please refer to your Consent Management Platform (CMP) or Data Protection Officer (DPO) for guidance.
ePrivacy being a Directive, and not a Regulation (like GDPR), it is up to each country to implement it in their own laws. This means that the interpretation inevitably varies slightly from country to country.In fact, although:
Opinion 4/2012 on Cookie Consent Exemption states first party analytics cookies are not likely to create a privacy risk when they are strictly limited to first party aggregated statistical purposes, and calls for an exemption.
