Key takeaways
- Google Consent Mode doesn’t collect consent. It passes the choice your cookie banner collected to Google tags so they behave accordingly.
- Basic mode blocks Google tags until someone chooses. Advanced mode loads them with consent denied and sends cookieless pings, which allows more detailed conversion modelling.
- For Canadian sites, the reason to use it is PIPEDA and Quebec’s Law 25, not Google’s EU policy, which covers visitors in the EEA, the UK and Switzerland.
- A banner that looks right can still be broken. Check it in Tag Assistant and in the Google Ads diagnostics tab, not by eye.
You added a cookie banner, and your Google Ads conversions dropped. Or a client in Quebec asked whether their tracking respects Law 25, and you’re not sure whether the “consent mode” box in the banner plugin is actually doing anything. Smart Bidding needs conversion data, and you need to know how much of it you’re losing and why.
This article explains what Google Consent Mode does in Canada, how basic and advanced modes differ, what Google can model, how to set regional defaults for Quebec, and how to verify the setup step by step. It’s a practical summary, not legal advice. For the wider picture of Canadian tracking rules, start with our guide to conversion tracking in Canada.
What does Google Consent Mode actually do?
Consent Mode is an API that tells Google tags whether a visitor has agreed to advertising and analytics storage. It doesn’t show a banner or record consent. Your banner or consent management platform (CMP) collects the choice. Consent Mode then adjusts what Google Analytics and Google Ads tags store and send, and lets Google model some of the conversions you can’t observe.
Google’s consent mode overview lists the signals. Four matter most for advertisers:
| Signal | Controls | When denied |
|---|---|---|
| ad_storage | Advertising cookies and identifiers | No ad cookies are read or written; IP addresses are truncated |
| ad_user_data | Sending user data to Google for advertising | No user ID or enhanced conversions data is sent |
| ad_personalization | Remarketing and personalized ads | Remarketing features receive no data |
| analytics_storage | Analytics cookies | No analytics cookies; cookieless measurement only |
“Consent Mode v2” is the common name for the version that added ad_user_data and ad_personalization. If your CMP only sends ad_storage and analytics_storage, it’s out of date.
What’s the difference between basic and advanced Consent Mode?
Basic mode keeps Google tags blocked until the visitor responds to the banner. If they refuse, nothing goes to Google. Advanced mode loads tags right away with consent set to denied, then sends cookieless pings until consent is granted. Advanced gives Google more to model from, so you recover more measurement. Basic is the more conservative privacy choice.
| Basic | Advanced | |
|---|---|---|
| Before a choice | Google tags blocked | Tags load with denied defaults |
| If consent is refused | No data sent, not even the consent status | Cookieless pings sent |
| Conversion modelling | General model | Advertiser-specific model, which Google describes as more detailed |
What gets modelled, and when?
Google uses cookieless pings and consented data to estimate conversions and behaviour it can’t observe. Modelling only starts when your site meets Google’s data thresholds. Many small Canadian advertisers won’t reach them, so don’t count on modelled data to fill the gap from a strict banner.
- Google Ads conversion modelling: Google’s consent troubleshooting page says the Ads diagnostic shows modelling as active once you reach 700 ad clicks over 7 days per domain and country grouping.
- GA4 behavioural modelling: According to Google Analytics Help, a property needs at least 1,000 events per day with analytics_storage denied for at least 7 days, and at least 1,000 daily users with analytics_storage granted on at least 7 of the previous 28 days. Google tags must load on every page, before the banner. To see modelled data, set Reporting identity to Blended in Admin.
Modelled GA4 data isn’t used in audiences, retention reports, predictive metrics or BigQuery exports. That’s one more reason GA4 and Google Ads numbers don’t match.
Is Google Consent Mode required in Canada?
Google’s EU user consent policy requires advertisers to send consent signals for users in the EEA, the UK and Switzerland. It doesn’t cover Canadian visitors. But Canadian privacy law still expects meaningful consent for ad tracking, and Consent Mode is how your banner’s choices reach Google tags.
Two Canadian rules drive the setup:
- PIPEDA. The Office of the Privacy Commissioner’s guidelines on online behavioural advertising say opt-out consent can be reasonable only if purposes are clear and not buried, people are told at or before collection, opting out is easy and takes effect immediately, and the information is non-sensitive. Health, financial and other sensitive categories call for opt-in.
- Quebec’s private sector privacy act, as amended by Law 25. Section 8.1 says that if you use technology that can identify, locate or profile someone, you must first tell them and explain how to activate those functions. Many practitioners read this as advertising cookies off until the visitor opts in.
Consent Mode doesn’t make a non-compliant banner compliant. It only makes Google tags respect whatever the banner says.
How do you set regional defaults for Quebec?
Set a default consent state for all visitors, then add a more specific default for Quebec using its ISO 3166-2 region code, CA-QC. Google’s consent setup guide says the more specific region wins, and the default must be set before any Google tag fires.
A typical setup for a national advertiser:
- Decide your policy first. For example: opt-in (all four signals denied by default) for Quebec and for any site handling sensitive information; your chosen approach elsewhere in Canada, based on legal advice. Many advertisers simply use opt-in everywhere to keep one setup.
- Configure it in your CMP. Most CMPs with a Google Tag Manager template set the default and update calls for you. Set the region rules there rather than hand-coding them.
- Cover every signal in every region. A regional default that sets ad_storage but forgets ad_user_data is a common error.
- Give a slow banner time. The wait_for_update setting (in milliseconds) lets the banner send its update before tags fire.
- Decide on url_passthrough and ads_data_redaction. Passthrough carries click IDs such as gclid in URLs when cookies are denied, which helps measurement. Redaction strips ad-click identifiers when ad_storage is denied. Make sure your privacy notice matches what you choose.
- Persist the choice. The update must reapply on every page, and visitors need a footer link to change their mind.
Your banner, choices and privacy notice also need to be in French for Quebec visitors.
How do you check that Consent Mode works?
Use Google Tag Assistant to confirm two things: a default consent state is set before any tag fires, and an update is sent after the visitor clicks the banner. Then check the Diagnostics tab on a Google Ads conversion action. If either check fails, fix it before trusting your conversion numbers.
Step by step in Tag Assistant
- Open tagassistant.google.com in Chrome, enter your site’s URL and connect. Use a fresh session so no earlier consent is stored.
- In the Summary, select the earliest Consent event. In the API Call section, confirm ad_storage, ad_user_data, ad_personalization and analytics_storage are all set.
- Open a Google tag, select the Consent tab, and check the On-page Default column. For an opt-in setup, it should show Denied.
- Click Reject on your banner. Confirm a new Consent event and that the tags behave as denied.
- Start again and click Accept. The most recent Consent event should show the update, and the On-page Update column should show Granted.
- In Chrome, change your simulated location to test Quebec and another province if you use regional defaults.
Check the Google Ads diagnostics
In Google Ads, go to Goals, then Conversions, then Summary. Open a website conversion action and select the Diagnostics tab. “Consent mode is implemented” means it works but modelling thresholds aren’t met yet. “Consent mode is implemented and modeling is active” means modelling is running. Google says the status can take 48 hours to appear, and sometimes up to two weeks.
Common mistakes
- Turning on the CMP’s “Google Consent Mode” toggle and never testing it. Tag Assistant flags a default set too late as an error; move the default above other tag code.
- Hard-coding Google tags outside Tag Manager so they fire before the CMP loads.
- Using advanced mode without updating the privacy notice to mention that limited data is sent before consent.
- Forgetting other vendors. Consent Mode only controls Google tags. Meta, LinkedIn and Microsoft tags need their own consent handling in your CMP or Tag Manager.
- Enhanced conversions without ad_user_data. If that signal is denied, enhanced conversions data isn’t sent. Check this before blaming the feature. The same consent thinking applies to Customer Match uploads.
- Cutting budgets after the drop. Lower reported conversions after a banner usually means lost visibility, not lost sales. Compare with your CRM first, and give Smart Bidding time before changing targets.
Frequently asked questions
Does Consent Mode replace a cookie banner?
No. Google states that Consent Mode doesn’t provide a banner or widget. You still need a banner or CMP to explain your purposes and record each visitor’s choice. Consent Mode only carries that choice to Google tags. Without a banner sending updates, tags stay at whatever default you set, which usually means denied and very little data.
Should a Canadian site use basic or advanced Consent Mode?
It depends on your legal advice and privacy notice. Advanced recovers more measurement because Google can build an advertiser-specific model from cookieless pings. Basic sends nothing before consent, which some advisers prefer for Quebec visitors. If you choose advanced, describe the cookieless pings in your privacy notice and record the decision and the date.
How long until modelled conversions appear in Google Ads?
Google says the Consent Mode status can take 48 hours to appear in the Diagnostics tab, and up to two weeks in some cases. Modelling itself needs enough traffic: the diagnostic cites 700 ad clicks over 7 days per domain and country grouping. Smaller accounts may never see modelled conversions, so focus on improving consent rates and first-party data.
Next step: run the Tag Assistant check on your own site this week. It takes about 15 minutes and tells you whether the banner is actually controlling your Google tags. If it isn’t, fix the default order first.
Sources: Consent mode overview, Google for Developers · Set up consent mode on websites, Google for Developers · Troubleshoot consent mode with Tag Assistant, Google for Developers · About consent mode, Google Ads Help · Behavioral modeling for consent mode, Google Analytics Help · Fix issues with your EU User Consent Policy consent audit, Google Ads Help · Guidelines on privacy and online behavioural advertising, Office of the Privacy Commissioner of Canada · Act respecting the protection of personal information in the private sector, LégisQuébec
Platform details as of November 2026.
