Topics Tools Books & Guides Talk to Securafy

Knowledge Hub / Compliance

Compliance

Your Website's Tracking Pixels Are Now a Compliance Problem, Not Just a Marketing Tool

SB 690 narrows some CIPA suits, but regulators still fine sites whose pixels ignore consent. Learn who owns tracking pixel compliance and how to prove it.

Rodney Hall By Rodney Hall Updated Nov 2026 11 min read Share

Who in our company actually knows what the tracking pixels on our website are sending, and to whom? When a demand letter citing California's wiretap law lands, that is the first question a business owner asks, and it is usually the one nobody can answer. Website tracking pixels compliance has quietly become an infrastructure problem: the Meta Pixel, the analytics tag, the chat widget, and the consent banner that is supposed to govern all of them are pieces of your technology stack, and they need the same ownership, change control, and evidence as anything else that touches customer data.

Most SMBs still treat these scripts as marketing's business. That made sense when the worst outcome of a misconfigured tag was bad attribution data. It no longer holds when the same misconfiguration can support a privacy lawsuit or a regulator's fine.

Does California's new CIPA law end website tracking lawsuits?

No. California's SB 690 narrows one type of claim but leaves the most common wiretap theory intact. Governor Newsom signed the bill on September 30, 2026, and starting January 1, 2027, only the California Attorney General may bring a pen-register or trap-and-trace claim under CIPA Section 638.51 against a private business for conduct on a website or app. Private plaintiffs lose that route, and the change reaches qualifying pending cases filed since January 1, 2025.

What SB 690 does not touch is just as important. As Fenwick's analysis of the enacted bill explains, private claims under CIPA Section 631, the wiretapping provision, and Section 632, the eavesdropping and recording provision, remain available and unaffected. Those are the provisions commonly invoked against session replay tools, chat widgets, and pixels that transmit what a visitor types or clicks. Defense counsel also expect plaintiffs to repackage pen-register theories as wiretap claims.

Federal courts have raised the bar in a different way. In Popa v. Microsoft, decided in August 2025, the Ninth Circuit held that a plaintiff alleging only routine, non-sensitive web tracking needs more than a bare statutory violation to have standing, and California federal courts have applied that ruling to dismiss claims built on IP addresses, device data, and cookie IDs. That helps a business whose tags collect ordinary browsing metadata. It helps much less when tags capture health, financial, or other sensitive context.

Why regulators, not lawsuits, now set the bar for tracking pixel compliance

Here is the point most coverage misses. Private litigation is volatile; courts split, legislatures intervene, and the plaintiff bar moves on to new theories. Regulatory enforcement is steadier and far more predictable, and regulators are asking a simple technical question: does your website do what your privacy notice and consent banner say it does?

California's privacy regulator answered that question bluntly in May 2025. The California Privacy Protection Agency fined retailer Todd Snyder $345,178 after it found the company failed to properly oversee and configure the technical infrastructure of its privacy portal, so consumer opt-out requests went unprocessed for 40 days. The agency's enforcement head put it this way: "Using a consent management platform doesn't get you off the hook for compliance."

Two months later, the California Attorney General announced a $1.55 million settlement with Healthline Media. According to the Attorney General, Healthline's consent banner purported to disable tracking when a visitor unchecked a box but did not actually disable the tracking cookies, opt-out requests including Global Privacy Control signals were not fully honored, and the company had assumed rather than verified that its advertising partners had signed the required contract terms. Neither case involved a hacker. Both involved tags that behaved differently from what the business believed.

Enforcement has continued in 2026. In March, the agency now branded CalPrivacy fined PlayOn Sports $1.10 million, alleging the company required users to agree to tracking technologies without a sufficient way to opt out and failed to recognize opt-out preference signals. The lesson across all three: a banner is a user interface, not a control. The control is the behavior of the scripts behind it.

Who is accountable when a tracking tool misbehaves?

The business that operates the website is accountable, even when an agency, developer, or platform vendor configured the tag. Regulators have been explicit that responsibility stays with the company using the tool. In practice, though, the knowledge of what was installed, when, and why is scattered across several parties, and that is where SMBs get hurt.

PartyWhat they usually controlWhat they usually cannot seeEvidence you should get from them
Marketing agencyAd pixels, conversion tags, tag manager containersWhether tags fire before consent on every page templateA current tag inventory with purpose and data sent
Web developerSite code, plugins, consent banner integrationWhich tags marketing added later through a tag managerChange log for consent and script deployments
Consent platform vendorBanner logic, cookie categories, signal handlingScripts loaded outside its controlConfiguration export and Global Privacy Control test results
IT provider or MSPHosting, DNS, security monitoringBusiness purpose of marketing scriptsScript change alerts and access records for site admin accounts
Your businessPrivacy notice, contracts, final decisionsAnything nobody reported to youOne owner who signs off on all of the above

That last row is the one most SMBs are missing. Without a named owner, the agency assumes the developer handled consent, the developer assumes marketing reviewed the tags, and the MSP was never asked. We see the same gap in broader vendor oversight, and it is why IT providers increasingly help manage third-party risk rather than leaving it to procurement. Pixels are a third-party data flow in the most literal sense, and the downstream recipients have their own partners; our AI Lab's piece on why your vendor's vendor is the real attack surface applies directly to ad-tech chains.

What does a defensible tracking setup look like?

A defensible setup is one where you can show, on demand, which scripts run on your site, what each one sends, what consent governs it, and proof that the consent actually works. This is closer to configuration management than to legal drafting, and it rewards the same discipline you already apply to servers and endpoints. The core of it fits in six steps.

  1. Inventory every script. Scan production pages, including checkout, forms, and logged-in areas, and list every third-party domain receiving data. Compare it with what marketing believes is installed. The two lists rarely match.
  2. Classify by sensitivity. Flag pages where URLs, form fields, or page titles reveal health, financial, or other sensitive context. Healthline's exposure came from pairing identifiers with article titles, so treat page context as data.
  3. Test consent behavior, not settings. Load the site with consent declined and with Global Privacy Control enabled, then confirm in browser developer tools that blocked tags do not fire. Repeat after every site or tag change.
  4. Remove what nobody owns. Old pixels from past campaigns, abandoned chat tools, and duplicate analytics tags add risk with no return. Deleting them is the cheapest fix available.
  5. Put contracts behind the data flows. Confirm that every advertising and analytics recipient is covered by terms that meet your state privacy obligations, and keep the signed copies.
  6. Control and log changes. Restrict who can publish to the tag manager and website, require a review for new scripts, and keep a dated record of each change and each consent test.

None of this requires removing your marketing tools. It requires treating them like production systems. Our earlier look at the risks of third-party cookies for businesses covers the underlying mechanics, and the broader case for aligning growth and protection is in how marketing automation and cybersecurity can work together. If you are adding AI-driven personalization on top of your tracking stack, our AI Lab's guide to what to automate and what to review in AI marketing is a useful next read.

The evidence trail matters as much as the fixes. When a demand letter or regulator inquiry arrives, the business that can produce a dated tag inventory, consent test results, and change records is negotiating from facts. The business that cannot is negotiating from assumptions, which is exactly where Todd Snyder and Healthline found themselves. Auditors and insurers increasingly expect the same kind of proof, as we explain in what cyber insurers and auditors actually want to see from your security program.

How Securafy helps you take ownership of the tag stack

When we take on a website tracking review, we start where the security team has an advantage: we scan the live site the way a browser sees it, map every script and data destination, and compare that against the agency's tag list and the consent platform's configuration. We test declined-consent and Global Privacy Control scenarios on your key page templates and document what actually fires. Then we work with your marketing team, developer, and counsel to remove orphaned tags, fix consent gaps, and decide which flows need contract coverage.

After the cleanup, we put the site under the same change control we apply to the rest of your environment: restricted publishing rights, alerts when new third-party scripts appear, and a recurring consent test with results stored as evidence. Your marketing team keeps its tools. You gain one accountable owner and a record you can defend.

Where To Go From Here

SB 690 changes who can sue over one CIPA theory, but it does not change what regulators are checking: whether your site behaves the way you told visitors it would. The fastest way to reduce your exposure is to find out what your scripts are doing before someone else does.

If you need a documented, repeatable way to prove your website tracking and consent controls work, Securafy's Comply-CARE compliance and vCISO program builds that evidence into your ongoing operations.

If you would rather talk through your specific environment first, book a strategy call with Securafy and we will walk through your current tag stack, consent setup, and the fastest path to a defensible position.

Tagged Under Compliance

Join The Conversation

Have a question or perspective on this topic? Add it below.

Rodney Hall

About The Author

Rodney Hall · President & COO

Rodney Hall is the President and COO of Securafy, with 2 decades of experience in IT service management and operations.

He writes about the less glamorous but essential side of IT: support systems, documentation, business continuity, recurring issues, downtime, and the processes that keep client environments running well. His perspective comes from years spent improving how service is delivered, how teams respond, and how small problems are prevented from becoming much larger ones.

Outside of work, Rodney enjoys home improvement projects, woodworking, and dirt bike riding. His personal mission mirrors Securafy’s: helping businesses stay secure, compliant, and ready for whatever comes next.

Writes about: Managed IT, IT operations, service delivery, business continuity, downtime prevention, support processes, operational risk

More From This Author →

Get Practical Cybersecurity Field Notes

Monthly cybersecurity, compliance, and IT strategy updates from Securafy, written for business owners who need clear next steps.

  • Practical security tips from our Cyber Security Drip series
  • The Securafy Times, our monthly roundup on compliance and IT strategy
  • Occasional updates on new tools, guides, and research
  • No spam — unsubscribe anytime