Opt-out is only a link
The user interface exists, but ad pixels and analytics vendors keep executing after the choice.
Run a Free SentinelScanUS Privacy
CCPA and CPRA compliance for opt-out and sharing controls
Technical review and implementation for opt-out workflows, sharing controls, sale signals, sensitive data concerns, and third-party advertising tags.
Implementation context
Start from observable behavior, then repair the consent contract.
US privacy compliance often depends on opt-out behavior, third-party sharing, sensitive data handling, and whether advertising or analytics systems continue collecting after a user exercises a choice.
For California visitors, the important evidence is not only that a link or preference center exists. The site has to show whether do-not-sell/share, limit-use, opt-out, and GPC states actually change pixels, audiences, cookies, and third-party requests.
ModeConsent reviews the runtime controls that determine whether opt-out, do-not-sell/share, and GPC choices are honored.
What breaks
The failure pattern usually starts before the dashboard can see it.
GPC is not connected
Global Privacy Control signals can be detected by the browser but ignored by CMP or tag logic.
Sharing controls are vague
Teams need to know which vendors receive data under each opt-out state.
Sensitive contexts use ordinary tags
Lead forms, account flows, healthcare journeys, financial pages, and other sensitive contexts may still run broad advertising or enrichment tools.
How ModeConsent fixes it
Repair the consent system where visitors and tags actually interact.
- 01
Test opt-out execution
We compare requests and storage before and after opt-out, including advertising and audience destinations.
- 02
Map vendors to purposes
Third-party tags are classified by analytics, advertising, personalization, sale/share, and operational purpose.
- 03
Validate state-specific rules
CMP region behavior and GPC handling are checked against the relevant visitor context.
- 04
Separate sale/share from measurement
Analytics, advertising, personalization, operational, and audience-building tags are reviewed separately so opt-out controls can be enforced by purpose.
Related work
Adjacent pages in the consent stack.
Compliance
Browser-Level Audits
Evidence-led audits that show what fires, what stores data, what changes by region, and whether consent choices are honored in production.
View pageComplianceConsent Evidence & Audit Trails
Browser-level proof artifacts that show consent defaults, user choices, tag behavior, storage writes, and network requests in a defensible record.
View pagePlatformsGA4 & Google Ads
Consent-aware implementation for GA4 events, Google Ads conversions, remarketing, enhanced conversions, and revenue reporting.
View pageIndustriesHealthcare
Technical consent review for appointment flows, condition pages, patient acquisition, analytics, advertising pixels, and sensitive user journeys.
View pageRequest auditNeed evidence for the live consent stack?
Request Compliance Audit