Many businesses notice it the same way: GA4 reports fewer users and sales than the store or the CRM. Ad blockers explain part of the gap, and consent explains much of the rest. When visitors decline analytics cookies, what GA4 sees depends on how consent mode v2 is set up, or whether it is set up at all. This guide explains what Google's consent mode does, when you need it, the difference between the basic and advanced versions, and how to set it up in Google Tag Manager. It is technical guidance, not legal advice; what your banner must ask, and how, depends on the laws that apply to your visitors.
What consent mode v2 does
Google consent mode is the way your cookie banner tells Google's tags what each visitor agreed to. The tags then adjust their behavior instead of simply running or not running. Version 2 uses four main signals, described in Google's consent mode documentation:
- analytics_storage: whether analytics cookies may be stored.
- ad_storage: whether advertising cookies may be stored.
- ad_user_data: whether user data may be sent to Google for advertising purposes.
- ad_personalization: whether data may be used for personalized advertising, such as remarketing.
The last two were added in version 2. Consent mode does not create a banner and does not decide what is lawful; it only carries the visitor's choice to the tags.
Who needs Google consent mode
Since March 2024 Google has required consent mode signals for visitors from the European Economic Area and the United Kingdom, and its policy also covers Switzerland, if you want to keep using advertising features such as remarketing and ads measurement for that traffic. A business that sells only in the United States is not bound by that policy in the same way, but US state privacy laws still matter. California, for example, gives consumers the right to opt out of the sale or sharing of their personal information and requires businesses to treat the browser's Global Privacy Control signal as a valid opt-out request. A Los Angeles store that ships to Europe, or simply receives European visitors, brings the EEA requirement into play for that traffic. If your site runs advertising pixels, ask a privacy professional how those rules apply to you.
Basic vs advanced consent mode
| Question | Basic | Advanced |
|---|---|---|
| Before a choice is made | Google tags do not load | Tags load with consent set to denied by default |
| When a visitor declines | Nothing is sent to Google | Cookieless pings without identifiers are sent |
| Modeling | Only Google's general model for ads | Advertiser-specific modeling, plus behavioral modeling in GA4 if thresholds are met |
| Main trade-off | Simplest to explain; the largest data gap | More complete reports; some legal teams object to any ping before consent |
The choice between basic vs advanced consent mode is partly technical and partly a policy decision, so make it together with whoever is responsible for privacy in your business.
Behavioral modeling has thresholds
GA4's behavioral modeling estimates the activity of visitors who declined, based on similar visitors who accepted. Google's behavioral modeling requirements set minimums: at least 1,000 events per day from visitors who declined analytics, for at least seven days, and at least 1,000 daily users who accepted, on at least seven of the previous 28 days. Many small business sites never reach those numbers, so on a small site advanced mode may not fill any gaps in GA4 reports. Check whether your property actually shows modeled data before counting on it.
Setting it up in Google Tag Manager
- Choose a cookie banner that supports consent mode. Many consent management platforms send the signals for you through a Tag Manager template. A home-made cookie banner can do the same with a few lines of code, but someone has to maintain it.
- Set defaults before anything fires. The default consent state belongs on the Consent Initialization trigger, before any tag runs. Defaults can differ by region, such as denied for the EEA and the UK.
- Update on choice. When the visitor accepts, rejects or saves preferences, the banner sends an update, and the choice is remembered on later pages.
- Handle tags that are not Google's. Google tags read consent mode on their own. Other vendors' pixels usually do not, so in Tag Manager they need their own consent settings or triggers that wait for the right choice.
- Check the result. Tag Assistant shows the consent state attached to each event, and the GA4 consent settings in the property's admin area show whether consent signals for analytics and ads are being received.
A clean GA4 tracking setup also means a banner that works on mobile, does not cover the checkout button and, where the law requires it, makes rejecting as easy as accepting. This is the setup our GA4 and Google Tag Manager service delivers, together with event tracking and e-commerce data.
Reading GA4 data after consent
- Expect a gap. Compare a week of GA4 purchases or leads with the real numbers from your store or CRM. A modest, stable gap is normal; a sudden change after a banner update points to a setup fault.
- Mark the right GA4 key events. In 2024 Google renamed GA4 "conversions" to key events, and "conversions" now refers to what Google Ads counts. Form submissions, calls and purchases should be key events, not just page views.
- Raise GA4 data retention. The default keeps event-level data for two months. Standard reports are not affected, but explorations and funnels are, so most businesses set retention to the 14-month maximum of a standard property.
- Keep a change log with the date of every banner or tag change, so a dip in a chart can be matched to its cause.
Frequently asked questions: consent mode v2
Does consent mode make my website compliant?
No. It passes choices to Google's tags. Compliance depends on what your banner asks, what your privacy policy says, which tags you run and which laws apply; ask a privacy professional for that part.
Do I need consent mode if I only sell in the United States?
Google's requirement targets EEA, UK and Swiss traffic. If you show a banner or honor opt-outs anyway, consent mode is still useful, because it keeps Google's tags consistent with what each visitor chose.
Does server-side tagging get around consent?
No. Moving tags to a server changes where data is processed, not whether the visitor agreed. Consent choices still apply.
Not sure what your banner is telling Google? Our GA4 and Google Tag Manager setup service covers consent settings, key events, e-commerce tracking and fixing GA4 data that does not match real orders. Once the numbers can be trusted, conversion rate optimization can put them to work. Contact us with access to your GA4 property and Tag Manager container, and we can review the setup.
