Skip to content
Digital Marketing

Google Consent Mode Explained for Small Business Sites

Consent mode passes your visitors' cookie choices to Google's tags. Here is what it does, the two ways to set it up, and why your numbers drop afterwards.

7 sections · 6 min read
In this article · 7 sections

You added a cookie banner because visitors from Europe found your site, or because a developer said you should. Since then, GA4 shows fewer visitors, Google Ads reports fewer conversions, and somebody mentioned that you also need “consent mode”, as if it were a separate thing. It is, and it explains a lot of what changed in your numbers.

This is Google consent mode explained in practical terms for a small business: what it does, the difference between its two set-ups, how it connects to your banner and what it does to your data. It is a technical overview, not legal advice. Whether you need consent for tracking, and in what form, depends on where your visitors are and is a question for someone qualified in that law.

A cookie banner asks visitors what they agree to. Consent mode is how that answer is passed to Google’s tags, so GA4, Google Ads and other Google tags can behave accordingly.

Without it, a banner can only do one of two blunt things with Google tags: block them entirely, or let them run. With it, the tags receive a set of consent signals and adjust how they work, such as whether they may set cookies and whether data can be used for ads.

Consent mode does not ask for consent itself, and it does not make a site compliant on its own. It is the wiring between the banner and the tags.

Google’s tags read a small set of named signals, each either granted or denied:

Signal What it controls
analytics_storage Whether analytics cookies may be stored, such as those GA4 uses to recognise returning visitors
ad_storage Whether advertising cookies may be stored, used for things such as matching ad clicks to conversions
ad_user_data Whether the visitor’s data may be sent to Google for advertising purposes
ad_personalization Whether data may be used for personalised advertising, such as remarketing lists

There are also signals for functional and personalisation storage used by other kinds of tools, but the four above are the ones that matter for GA4 and Google Ads.

Two moments matter. First, a default state is set as the page loads, before the visitor has chosen anything. Then, when they click accept, reject or save preferences, an update is sent with their choice. On later visits, the banner reads the stored choice and sends the update straight away.

Google describes two ways of implementing consent mode. The difference is what happens before, and without, consent.

Basic Advanced
Before the visitor chooses Google tags do not load at all Google tags load with signals set to denied
If the visitor declines Nothing is sent to Google Tags send limited signals without cookies
If the visitor accepts Tags load and work normally Tags switch to normal behaviour
Modelling of missing data More limited Google can use the limited signals to estimate some missing conversions and behaviour

Advanced gives Google more to work with and usually leaves fewer gaps in reporting. Basic is more conservative, since nothing reaches Google until a visitor agrees. Which is appropriate depends on your legal advice and your own comfort with sending limited data before consent. Google’s developer documentation on how consent mode works describes both in more detail.

For most WordPress sites, the practical set-up looks like this:

  1. Choose a banner that supports consent mode. Many consent management plugins and services can send Google’s signals for you. Check that it supports the advertising signals as well as the storage ones.
  2. Set defaults before any Google tag loads. The banner, or a consent setup in Google Tag Manager, must set the default state first. If a tag loads before the default is set, it behaves as though consent was granted.
  3. Decide defaults by region if your audience is mixed. Consent mode allows different defaults for different regions, for example denied for visitors from Europe and granted elsewhere, if your legal advice supports that.
  4. Map banner categories to signals. “Statistics” or “analytics” usually maps to analytics_storage. “Marketing” usually maps to the three advertising signals.
  5. Configure non-Google tags separately. The Meta Pixel and other tools do not read Google’s signals. In Tag Manager, give them their own consent requirement so they only fire after the right category is accepted.

Choosing and configuring the banner itself is covered in our post on what a good cookie banner does, and the WordPress steps are in adding a cookie banner in WordPress.

Consent mode fails quietly. The banner looks fine while the signals never reach the tags. To check it:

  • Use Tag Manager’s preview mode in a private browser window. The consent view shows the default and updated state for each signal. Our post on GTM preview and debugging explains the screen.
  • Decline, then look. With everything declined, analytics and ad tags should either not fire (basic) or fire with denied signals (advanced). The Meta Pixel should not fire at all.
  • Accept, then look again. Signals should update to granted and tags should fire normally.
  • Check Google’s own status screens. Both GA4 and Google Ads show, in their admin or diagnostics areas, whether they are receiving consent signals. A warning there usually means a missing signal or a default set too late.

What happens to your numbers

When consent is handled properly, reports change. That is expected, not a fault.

  • Fewer recorded users and sessions from regions where many visitors decline.
  • Fewer observed conversions in Google Ads and GA4, because declined visitors cannot be matched in the usual way.
  • Some modelled figures, where Google estimates part of the gap. Modelling has eligibility requirements, including enough traffic, so a small site may see little or none.
  • Smaller remarketing audiences, since only visitors who allowed ad personalisation can be added.

Modelled figures are estimates. Treat them as a better guess than a gap, not as a list of real enquiries. Your own records of forms, calls and orders stay the most reliable count, and comparing those with GA4 over a few months shows how much consent is hiding. If GA4 stops recording almost everything after a banner goes live, that is a set-up problem rather than consent, and our checklist for GA4 showing no data covers it.

Frequently asked questions

Google’s requirements for consent signals focus on visitors from Europe and some other regions, so a business with a purely local audience elsewhere may not need it for that reason. Privacy laws such as India’s data protection law still matter for personal data. Ask someone qualified, since this is not legal advice.

No. Consent mode is Google’s system, and Meta’s pixel does not read its signals. Hold the pixel back through your banner or through a consent requirement in Google Tag Manager, so it only fires after the visitor accepts the marketing category.

Yes. The change is mainly in how Google tags load before consent, so it is made in your banner’s settings or in Tag Manager. Retest afterwards with consent declined and accepted, and note the date, because the change will alter how your numbers compare with earlier months.

That usually means no default state is being set, or it is set after the Google tags have already loaded. Check that the banner’s consent mode option is switched on and that its script, or your Tag Manager consent initialisation, runs before any Google tag fires.

Consent mode is fiddly mainly because it sits between three moving parts: the banner, Tag Manager and Google’s tags. If you would like it set up and tested with the rest of your tracking, our tracking and consent setup includes that work, and our digital marketing guide shows how measurement supports the rest. For the broader measurement picture, read our introduction to marketing analytics.

Next in this series: Cookie Banner for Your Website: What a Good One Does

Is Your Website Working Properly?

Get a free website health check from WebMaintor. We'll review your website's speed, security, forms, and technical health — and tell you exactly what needs attention.

No obligation. No automated reports. A real review by our team.