# What is Consent Mode for GA4? > What Consent Mode v2 does in GA4, how basic and advanced modes differ, what’s collected in each consent state and how modelling works. Source: https://www.measurelab.co.uk/insights/blog/consent-mode-ga4/ Author: Daniel Perry-Reed Published: 2022-06-16 Updated: 2026-10-13 *Updated October 2026 for Consent Mode v2.* ### **What is Consent Mode?** [Consent Mode](https://support.google.com/analytics/answer/9976101) is a feature that helps manage what tracking occurs when consent is and is not granted from the user. This feature applies for websites via Google’s global site tag (gtag.js) and Google Tag Manager (GTM), and for apps via the Firebase SDK. There are five default types of consent (you can add your own on top as well) that can be managed in Consent Mode: Consent Mode v2, introduced in November 2023, added two more: `ad_user_data`, which says whether user data can be sent to Google for advertising, and `ad_personalization`, which says whether it can be used for personalised ads. For users in the European Economic Area, Google has required both since March 2024 for its advertising measurement and personalisation features. ### **What isn’t Consent Mode?** **Consent Mode is not a consent management platform (CMP)**. That is, it doesn’t collect user consent on a website or app. Consent Mode is only the process of managing tracking based on the collected consent levels. You will need to implement a CMP to do the actual consent collection. GTM has some out-of-the-box [CMP integrations](https://support.google.com/tagmanager/answer/10718549#cmp-integrations) via templates that can be used with relative ease. However, you do not need to use one of these to use Consent Mode effectively. For example, the Measurelab website [www.measurelab.co.uk](https://www.measurelab.co.uk/insights/blog/) uses [CIVIC’s Cookie Control](https://www.civicuk.com/cookie-control) which is not on the list and it works absolutely fine with Consent Mode. ### Basic and advanced Consent Mode There are two ways to implement it. In basic mode, Google tags don’t load until someone has made a choice on the consent banner, so nothing reaches Google before then. In advanced mode, the tags load straight away and, while consent is denied, send cookieless pings without cookies or identifiers, which Google uses for modelling. Advanced mode recovers more measurement but sends some data before consent, so which one suits you is a decision for your privacy team. ### **How Consent Mode works with GA4** Generally speaking, each tracking tag will have some sort of consent dependency. For example, you will need *ad_storage* to be *true*to be able to fire the Facebook Pixel. However, Consent Mode works slightly differently when it comes to the Google tags (Google Analytics, Google Ads, Floodlights). In advanced mode, GA4 sends all the events **with or without consent**. There are a few variations of consent as GA4 utilises both the *analytics_storage* (for the core tracking) and *ad_storage* (for [Google Signals](https://support.google.com/analytics/answer/9445345)) consent. Depending on what the user consents to, depends on what is collected in GA4. The below table details what happens in each situation: ### **GA4 data modelling** The reason GA4 still tracks all events even without consent in advanced mode (called 'cookieless pings') is so that it can use machine learning models to estimate the number of unconsented users, sessions, etc. in the data. This process is called [behavioural modelling for Consent Mode](https://support.google.com/analytics/answer/11161109) and is available for all GA4 properties now. Assuming you have met the [prerequisites](https://support.google.com/analytics/answer/11161109#prerequisites) in data volume, then you will be able to use the ‘Blended’ reporting identity in GA4, which is set under *Admin > Reporting Identity*. ![Ga4 reporting identities](https://lh5.googleusercontent.com/8wWwUE24BPx35Gxh-W89o7aC_YntE6tAEhs7qZXLzoRKLOCrx7WKkaRPSZpxY4B5IVzAuo6cZO2pF-86_V9itMbX4_mgLJ5hMnO9cZ-mOChpN6rCOgERg57PM9ESk5sZq94yFDrKyUtwvV9P1w) You will then see the modelled data in all available reports when using GA4. You can see if any specific report is using modelled data by clicking on the report status icon: ![GA4 modelled data in reports](https://lh5.googleusercontent.com/jkh8ew-kbB-EktxpVuOZMNi-lXBDErPVVZCQQVT-rvh1gxOS8mjRYb47PAqfu3Mb6FuBlLiGY9dJccRzEfLIFeE7r9wFHJyxNt_fyx-2WU55PeoPJY5PHvxQqDjlkQvyZhny9asUBDEpxR0FNw) ### **Opting out of cookieless pings (GTM)** Some companies might not agree with Google’s cookieless pings and want to prevent them from happening altogether. In a sense, make sure that no consent means no track of any sort. In GTM this is relatively simple to do. First you may have to enable the consent overview in *Admin > Container Settings > Additional Settings*: ![GTM container setting for consent overview](https://lh5.googleusercontent.com/0ntCRiGr9EspHuHDRrKmR7AFe0aoCwbGvmJevdQ-UyLYhZXHhwZSgQ9yAQfR97UY9R3LDR2NcM95SaQxjoNTiFv6QG_jRIW0yVl0jyO520jM4EeeGeUWTaZxf709k9LJnbYbowZOdi7LkL5PBg) Then you should see a new ‘Consent Settings’ section under the ‘Advanced Settings’ in any tag configuration. In there, for the GA4 tags you have, you can select ‘Require additional consent for tag to fire’ and specify the consent type you want to ensure you have. For GA4, this is most likely to be the *analytics_storage* consent. ![GTM tag consent settings with additional consent set](https://lh4.googleusercontent.com/VbOUzjPvDZQjaJfgd2Q5j3qhgzQJR3Qkw5gPKmw6V0WAyMIl9ynfm0hEHGmWH8MEm5l0yy6VAz095vlJYsrmE3K5TzL0G8fpgAMsmh_xplYw7EnGUU8pDpkoaHf6_0eD5rldbxiQC_nzxJgZsA) Once saved and published, all the GA4 tags will now behave the same as the non-Google tags in that nothing will be tracked until you have the user’s consent. In effect, this is basic mode. **Note:** By doing this, you will never be able to use the behavioural modelling in GA4! ### **Do I need to use Consent Mode?** If you advertise with Google to users in the EEA, in practice yes: Google needs the v2 signals for its measurement and personalisation features there. Elsewhere it isn’t required, but it will save you all the time and effort of manually triggering tracking based on consent statuses from your CMP. In GTM, you *can*manage variables and triggers for each consent type by creating trigger groups to include consent and dynamically fire each tag. However, Consent Mode makes all of this much easier, and you can manage, change and update consent requirement in bulk without the need of trigger groups! If you are using a CMP (and who isn’t nowadays), then Consent Mode is a valuable tool and asset to making sure it is ‘plumbed in’ effectively to all your marketing and analytics tracking and data collection. If you want to know what your consent setup actually does in each consent state, that’s what a [Consent Mode audit](https://www.measurelab.co.uk/solutions/consent-audit/) checks. The [Free Collection & Consent check](https://solutions.measurelab.co.uk/collection-consent-check/) gives a quick first look.