Cookie Compliance in Canada, the US and EU: Does Your Website Stop Tracking When Visitors Say No?

A practitioner's view on cookie and tracking compliance for Canadian organizations

Most organizations believe their cookie compliance is handled. There is a banner, a privacy policy and a consent tool that someone configured during the last website refresh. Then we test the site. A visitor clicks "Reject All" and the Meta pixel fires anyway. A California visitor's browser sends a Global Privacy Control signal and the remarketing cookie still loads. Analytics runs before the banner has finished loading.

This gap between what the banner says and what the site actually does is where nearly all of today's regulatory and litigation risk sits. This article walks through what we see in audits, why it matters and where to focus first.

What Is a Cookie Exactly, and How Does It Work?

Cookies are small pieces of data that websites store in your browser to remember information about your visit. They help websites keep you logged in, save your preferences or remember items in your shopping cart. While some cookies are essential for a website to function, others are used for analytics, advertising and tracking activity across websites. This is where privacy concerns arise, particularly when visitors aren't aware of what's being collected or how their information is being used.

Why does cookie compliance matter now?

Regulators and plaintiffs have stopped asking whether you have a banner. They now ask whether tracking stops when someone says no. That makes cookie compliance one of the most provable privacy failures an organization can have. Answering that takes coordinated organizational effort.

Canadian organizations are exposed on several fronts at once. If you sell into the United States, your website is already operating under California law. If you have European customers, EU rules apply too. Canadian law has its own expectations, and Quebec's are the strictest of all.

What counts as a tracking technology?

Cookies are only one part of it. The tracking stack on a typical website includes:

  • First and third-party cookies for sessions, preferences, analytics and advertising

  • Pixels and tags from Meta, Google, TikTok and LinkedIn, which send event data to the platform

  • Session replay tools that record clicks, scrolls and sometimes what visitors type into forms

  • Chat widgets and AI chatbots, often run by vendors who can see the full conversation

  • Mobile SDKs that collect advertising identifiers and attribution data

  • Fingerprinting and local storage, which identify a device without using a cookie at all

  • Server side tracking, where data goes from your server to a vendor without ever touching the browser

The legal analysis follows the data, not the technology. If something identifies, profiles or follows a person, it is in scope, whatever the vendor calls it.

What is the privacy impact?

On their own, a single page view or an IP address can look trivial. Combined across sites and over time, they build a detailed picture of a person: what they browse, what they buy, what they worry about. The risk is highest when browsing reveals something sensitive. A visit to a health condition page, a mental health booking flow, a financial hardship form or a children's product category can turn routine tracking into the disclosure of sensitive information to an ad platform. Many of the largest US settlements came out of exactly this situation in healthcare.

How do CMPs, GTM and server side tracking work together?

Think of it as a chain where every link has to hold.

The consent management platform (CMP) records the visitor's choice and publishes it as a consent state. Google Tag Manager reads that state and decides which tags may fire. Google Consent Mode passes the choice to Google tags. In basic mode, Google tags stay blocked until consent is given. In advanced mode, tags load and send cookieless pings even when consent is denied. That may be acceptable for some jurisdictions, but it is a decision legal should make knowingly, not a default someone accepted during setup. On Shopify, the Customer Privacy API carries the same choice to apps and the native pixels, and it has to agree with the CMP.

The weak points are where these pieces hand off to each other: the consent default has to load before any tag, every tag needs a consent requirement, every vendor needs the correct category, and regional rules need to map to the correct default. A CMP on its own does not block anything. It only works if the tags are wired to it.

Server-side tracking deserves particular attention. A server container improves performance and data quality, and it gives you real control. Moving tags to a server container improves performance and data quality, and it gives you real control over what each vendor receives. It also moves data out of the browser, where neither the visitor nor a standard cookie scanner can see it. That is not a compliance workaround. Consent obligations follow the data. If the server forwards events to Meta or Google after a visitor has opted out, the violation is the same, only harder to detect. Done properly, server-side tracking is one of the strongest controls available. You can remove identifiers, filter fields and make each vendor forward depend on consent. Done carelessly, it hides the very problem regulators are looking for.

What does the law require?

Canada

PIPEDA requires meaningful consent. Under the OPC's policy position on online behavioural advertising, opt-out consent can be acceptable, but only if people are clearly informed, the opt-out is easy and takes effect immediately, and sensitive information is avoided. Technologies people cannot turn off, such as zombie cookies, do not meet that standard. Quebec's Law 25 goes further: technology that identifies, locates or profiles a person must be off by default. In practice, that means opt-in for non-essential tracking in Quebec.

Under PIPEDA, organizations need meaningful consent. Under the OPC's policy position on online behavioural advertising, opt-out consent can be acceptable for behavioural advertising, but only under conditions: people must be told clearly, the opt-out must be easy and take effect immediately, and the tracking must avoid sensitive information. The policy covers cookies, web beacons and device fingerprinting. Technologies that cannot be switched off, such as zombie cookies, do not meet that standard. Quebec raises the bar. Under Law 25, any technology that identifies, locates or profiles a person must be off by default, and people must be told about it. In practice, that means an opt-in model for non-essential tracking in Quebec. A setup that satisfies California will not automatically satisfy Quebec.

United States

The CCPA treats many advertising pixels as "selling" or "sharing" personal information, so opt-outs must actually work, and browser signals such as Global Privacy Control must be honoured. Separately, wiretap laws, led by California's Invasion of Privacy Act (CIPA), carry statutory damages of $5,000 per violation without any proof of harm

EU

European Union. The ePrivacy rules require prior consent before storing or reading non-essential information on a device, and the GDPR sets the standard for valid consent. Rejecting must be as easy as accepting. For multinationals, the EU model is often the simplest one to design around.

What does SB 690 change, and what doesn't it?

CIPA

CIPA is a 1967 wiretapping statute. Plaintiffs' firms have used it to send tens of thousands of demand letters and file class actions against ordinary websites. Two theories drive most of these claims. Under section 631, the wiretapping provision, the argument is that a third party vendor (a pixel, a session replay tool or a chat provider) "intercepts" a visitor's communications. Under section 638.51, the pen register provision, the argument is that trackers capturing IP addresses and device data work like the old devices that recorded the numbers a phone dialled.

SB690

SB 690 was signed on September 30, 2026 and takes effect January 1, 2027. From that date, only the California Attorney General can bring section 638.51 claims based on websites and apps. Private plaintiffs can no longer initiate such claims. The change also applies to pending claims in actions filed since January 1, 2025.

It removes the cheapest claim plaintiffs had against any site that collects an IP address. As introduced, the bill would have created a broad "commercial business purpose" exemption across CIPA. That version was dropped. The wiretapping claims under section 631, which target pixels, session replay and chatbots, still stand, along with claims under section 632.7 and the federal Wiretap Act. Plaintiffs are also expected to move to other theories and other states. The Governor asked the Legislature to look at CIPA's other provisions in 2027, so more reform may come, but it is not law yet.

Our view is that SB 690 changes which claims you are likely to receive. It does not remove the need to show that your tracking respects consent. If anything, the risk is now concentrated in the technologies that matter most, which are third party pixels, session replay and chat.

Cookie Consent: What are regulators looking for?

California enforcement has kept coming back to the same root causes: opt-outs that didn't work, consent designs that made rejecting harder than accepting, and Global Privacy Control signals that were ignored. Disney, Healthline, Tractor Supply and Honda were among those penalized. Regulators test websites themselves rather than reading policies.

In Canada, the OPC continues to describe third party cookies as tracking that happens largely without people's knowledge. Its most recent guidance has focused on children's privacy, age assurance and assessing third party service providers. Each of these bears directly on which vendors you allow onto your site and how you oversee them

Where do things go wrong?

These are the failures we find again and again:

1.     Pre-consent firing. Tags load on the first page view, before the visitor makes any choice. This is the most common and most provable failure.

2.     "Reject All" is recorded but not enforced. The CMP saves the choice, but tags were never set up to require consent.

3.     Global Privacy Control is detected but ignored. The CMP shows that it received the signal, but advertising cookies are still set.

4.     Hardcoded scripts. Scripts in the site theme, a Shopify app or a plugin load outside the tag manager and bypass the consent tool completely.

5.     Miscategorized cookies. Marketing cookies sit in "Strictly Necessary" because the auto-scan guessed wrong and nobody checked.

6.     Drift. A campaign, an app install or a site migration adds trackers that nobody reviews. Most sites we retest after a migration have regressed.

7.     One banner for everyone. The same consent model is used for Quebec, Ontario, California and the EU.

 

What do internal teams need to watch?

  • Marketing owns most of the trackers. Every new pixel, campaign tool or attribution platform should go through a quick review before launch, not after. Tracking on sensitive pages needs a deliberate decision.

  • Web and digital teams own implementation. Default consent states, tag triggers and hardcoded scripts are their responsibility, and the site should be retested after every release and migration.

  • Legal and privacy own the consent model by jurisdiction, the accuracy of the notice and vendor contracts. Vendor terms should limit how data is used and should address CCPA service provider requirements where they apply.

 

The usual failure is not that one team gets it wrong. It is that no single team owns the whole chain.

What should organizations prioritize?

1.     Fix pre-consent firing and rejections that don't stop tracking.

2.     Make Global Privacy Control work the same way as a manual opt-out.

3.     Review pixels, session replay and chat on sensitive pages.

4.     Make sure your CMP inventory matches what actually loads, and correct the categories.

5.     Document your server side flows and the consent state each vendor receives.

6.     Retest every quarter and after every release.

Case Studies and How Bamboo Can Help Section

Case study: Responding to a cookie compliance complaint

A privacy complaint can quickly become a legal issue, but fixing the underlying problem often requires much more than legal advice. When our client faced allegations that website trackers were collecting data before users had provided consent, we helped them determine what was actually happening and what needed to change. We performed technical testing to identify trackers firing prematurely, mapped third-party data flows, and worked with the client's teams to inventory and classify approximately 480 cookies and trackers. From there, we helped strengthen the consent-management configuration, review tag-management and consent signals, and establish ongoing testing to reduce the risk of the problem recurring. We also worked alongside external counsel, providing the technical and privacy analysis needed to support the client's response. What began as a complaint became an opportunity to address the immediate risk while building stronger, more defensible cookie governance for the future.

How Bamboo can help:

When a cookie, tracking or privacy complaint lands, Bamboo can help investigate what happened, assess the compliance risk, work with your technical teams to fix the problem, and provide the evidence and privacy expertise needed to support legal counsel and your response.

Case study: Making cookie consent work across four jurisdictions

For another client, the challenge wasn't responding to a complaint. It was proactively building a consent experience that could work across the EU, UK, US and Canada. We audited the client's existing cookie and tag environment, documenting what each technology did, when it fired, and how the website responded to consent and Global Privacy Control (GPC) signals. We then helped the client implement a new consent management platform, categorize its cookies, configure consent and opt-out signals, and make sure those choices flowed properly to downstream tags and vendors. Once configured, we tested the entire experience end to end, created a detailed cookie inventory documenting purpose and session information, updated the cookie policy, and developed preference-centre language tailored to each market. The result was not simply a better cookie banner. It was a scalable consent framework designed to support the retailer as it operates across four different privacy regimes.

How Bamboo can help:

Bamboo can design and operationalize your cookie consent program from the ground up, including cookie and tag audits, CMP selection and implementation, GPC configuration, consent testing, cookie inventories, policies and jurisdiction-specific preference centres for organizations operating across Canada, the US, UK and EU.

Cookie Audits and A Path Forward

Organizations that fail a cookie audit never set out to track people without consent. Someone added a pixel to hit a campaign deadline, a migration broke a trigger, or a default setting was never questioned. The fix is rarely dramatic. It comes down to knowing what fires, when and why, and checking it again after things change.

Start with one simple test: open your site in a fresh browser, click "Reject All" and watch the network log. If anything still goes to an ad platform, you have found where to begin.

Bamboo Data Consulting audits, remediates and monitors cookie and tracking compliance for organizations across Canada, the United States, and Europe. If you'd like a second set of eyes on what your website actually does when a visitor says no, reach out to our team.

Next
Next

Privacy Budget Planning: How to Make Your Case to Finance