Do you need it if you only serve the valley?
Strictly, Google asks for consent signals when you collect data from visitors in the European Economic Area or the United Kingdom, and it can limit audience and measurement features without them. If your customers are all in Abbotsford, Mission and Chilliwack, that rule rarely applies. Many local sites still get a few overseas visitors, though, and an online shop that ships abroad certainly does.
The bigger reasons are closer to home. Quebec’s Law 25 sets stricter expectations for tracking, BC’s privacy law for private organizations expects you to be open about what you collect and why, and visitors increasingly expect a real choice. Rules change and every site is different, so ask a privacy lawyer about yours. On the marketing side, consent mode is a tidy way to honour whatever a visitor decides.
Basic or advanced: choose before you touch a tag
Basic mode holds Google tags back until the visitor answers the banner. If they decline, nothing is sent and Google has nothing to model from. Advanced mode loads the tags straight away in a restricted state, and when a visitor declines, they send cookieless pings with no identifiers stored. Google uses those pings to estimate the conversions it cannot see.
Basic is simpler to explain to a cautious client, and your lawyer may prefer it. Advanced recovers more of the picture, but the modelling only switches on once there is enough traffic and conversions, and a small local site may never reach that volume. Neither choice is wrong. Decide, write it down, and make the banner match.
The setup, in order
Follow the steps in this order, because tags that fire before your defaults load will ignore the visitor’s choice. On WordPress, much of this is a plugin setting. On a hand-built site, your developer or our team adds the defaults to the page head.
Make a note of every tag the site runs: analytics, ads, the Meta Pixel, chat widgets, map embeds. Anything outside Google’s tags needs its own consent handling, and the banner must be able to block or allow each one.
- Choose a banner or consent platform that supports Google Consent Mode and lists its Google certification
- Set all four signals (ad_storage, analytics_storage, ad_user_data and ad_personalization) to denied wherever consent is required
- Load those defaults before GA4, Google Ads and every other tag
- Have the banner send an update when the visitor accepts or rejects
- Add a footer link so visitors can change their mind later
Test it before you trust it
Open Tag Manager’s preview mode or Tag Assistant, load your site in a fresh private window and watch the consent state. Before you click anything, all four signals should read denied. Accept the banner and they should flip to granted. On a second visit, reject, and confirm that no advertising cookies appear in your browser’s storage panel.
Finish by sending a real test enquiry and making a test call from your phone, then look for both in GA4’s realtime view and your Google Ads conversions a day later. Plenty of sites have a banner that looks right while the signals underneath never change, and this step separates a working setup from a decorative one.
What your reports look like afterwards
Expect a dip in directly observed conversions, because some visitors will say no. Where modelling is active, Google fills part of the gap with estimates and labels them as modelled. Do not read the totals as exact. Treat them as a trend line and compare them with sources you control: your phone log, your enquiry inbox and your booking system.
Clinics and other health providers should add one more rule: keep event names and the data sent to ad platforms generic. ‘Booking request’ is fine. The treatment someone asked about is not. If you use hashed email addresses to improve matching, do it only with clear consent, and check with your privacy officer first.
Where measurement is heading
Measurement is moving away from following individuals and toward estimates built from consented, combined data. That makes your own records more valuable every year. A tidy customer list, a CRM that notes the source of each lead and a habit of asking people how they found you will outlast any particular cookie rule.
- 01More modelled conversions appearing in Google and Meta reports
- 02Server-side tagging and conversions APIs that send consented data from your own server
- 03Browser privacy changes that shrink what plain cookies can see
Questions & answers
A banner asks the visitor for a choice. Consent mode is the wiring that tells Google’s tags what that choice was so they behave accordingly. You need both working together: a banner without the wiring is decoration, and the wiring without a banner has nothing to read.
Your reported numbers may fall, because declined visitors cannot be tracked the usual way. Your actual leads do not fall for that reason. Advanced mode and modelling recover some of the gap, and comparing reports with your own call and enquiry records shows what is really happening.
Often, yes, if your site uses a common platform and a banner plugin that supports Google Consent Mode. The danger is silent failure, such as defaults that load too late. If you run paid ads, have someone test it properly. Our team does this as part of conversion tracking work.
Meta has its own controls for how its pixel and Conversions API handle consent, and your banner needs to block or allow the pixel accordingly. Consent mode itself is a Google feature. Set up both, then test each one separately.
