Overview
This check confirms your Consent Management Platform (CMP) script loads and initializes on every crawled page, comparing the pages where your CMP vendor's tag is detected against the complete page inventory to surface any gap in coverage.
Note: This guide is provided for informational purposes only and does not constitute legal advice. Consult qualified legal counsel regarding your organization's specific GDPR compliance obligations.
Why It Matters
If the CMP fails to load or execute properly on a subset of pages, downstream tracking tags on those pages fire without any compliance containment at all — there is no mechanism present to record consent, gate tags, or honor a rejection. Under GDPR's opt-in standard this is a more severe failure mode than in opt-out jurisdictions, since a missing CMP on a page means every non-essential tag on that page is, by definition, firing without a lawful basis. A flawless distribution score across every EU-facing directory is treated as non-negotiable for exactly this reason.
Implementation
Run a full-site Web Audit, or a representative crawl for very large sites.
Check the pre-built ObservePoint report Pages missing a 3rd Party CMP. It lists every crawled page where ObservePoint detects none of the CMPs in its tag database.
Review each page the report returns. It either has no consent management running on it, or it runs a CMP that ObservePoint doesn’t recognize.
Note: If you use a first-party (in-house) CMP, or one that isn’t in the ObservePoint tag database yet, contact us to have it added. Until then, pages running it will appear in the report even though consent management is working.
Remediation
Here are some steps you need to follow:
For each page missing the CMP, determine whether the gap is template-specific. CMP deployment gaps are almost always tied to a specific page type rather than being randomly distributed.
Add the CMP script/container to the missing template, or migrate the affected pages into the governed tag-management container so future coverage is automatic. Where a regional or acquired property runs its own CMS entirely, deploy the CMP independently there and add that property to the audit scope as its own tracked domain.
Re-run the full-site Audit after the fix and confirm 100% CMP coverage before considering the issue closed.
Conclusion
Every consent-behavior check downstream — prior-consent enforcement, GPC recognition, tag behavior under rejection — depends on the CMP actually being present, so closing CMP coverage gaps first is the single highest-leverage fix in the entire GDPR framework.