Google Consent Mode v2 for US businesses: what you actually need

01What Consent Mode does

Consent Mode is a way for your website to tell Google tags which kinds of storage and data use the visitor allowed. Tags then adjust: with consent they work normally, without it they send limited, cookieless signals that Google uses for modeling.

Version 2 added two parameters to the original ones: ad_user_data, whether data can be sent to Google for advertising, and ad_personalization, whether it can be used for personalized ads and remarketing.

02Does a US business need it

Google requires Consent Mode v2 signals for advertising measurement and personalization of users in the European Economic Area. If none of your traffic or campaigns involve the EEA, you are not bound by that requirement.

In practice, many US businesses still implement it. Some traffic comes from abroad regardless of targeting, and a consent banner with Consent Mode is the cleanest way to honor state opt-out rights with the same setup.

03US state privacy laws in one paragraph

US comprehensive privacy laws, starting with California, generally use an opt-out model: you may collect data by default, but must let people opt out of the sale or sharing of personal information and of targeted advertising. California regulators have taken the position that sharing data with ad platforms for cross-context advertising can count as sharing. Several states, including California and Colorado, require honoring Global Privacy Control, a browser setting that sends an opt-out signal automatically.

The details differ by state and change often. The design principle does not: give visitors a real choice, honor it technically, and document what each tag does.

A banner that changes nothing when someone clicks "reject" is worse than no banner.

04How to set it up correctly

The order of operations matters more than the tool you use.

• Set default consent states before any Google tag loads, in a script at the top of the page.
• Decide defaults by region: denied where opt-in is required, and granted or denied elsewhere depending on your legal advice.
• When the visitor makes a choice in the banner, send a consent update to the tags.
• Read the Global Privacy Control signal and treat it as an opt-out of advertising.
• Keep strictly necessary cookies, such as the one that remembers the consent choice, separate from marketing ones.

05Mistakes that break tracking

These are the problems we find most often in audits, usually months after launch.

• The default is set after the tags load, so the first page view is sent before consent is known.
• The banner updates its own cookie but never sends the consent update to Google tags.
• Two consent tools are installed at once, one by the developer and one by a plugin.
• Conversions are marked as not firing because testing was done with consent denied.
• Server-side and client-side tags disagree about what the visitor allowed.

06How to check your site

Open the site in a private window with Google Tag Assistant connected. Before touching the banner, the consent state should already show the defaults. Accept, and it should update. Reject in a fresh window, and advertising storage should stay denied.

Then submit a test form and confirm the conversion is recorded in both cases, as an observed conversion with consent and as a cookieless ping without it.