Consent Management Platform (CMP)
Software that displays cookie consent banners and manages user preferences. Required under GDPR and ePrivacy Directive for websites that use cookies or collect personal data through analytics.
The analytics cost of consent
CMPs are legally necessary for cookie-based analytics, but they create a fundamental measurement problem: visitors who reject cookies become invisible to analytics. In the EU, consent-based analytics loses 15–60% of visitors, depending on sector, brand strength and traffic mix.
This creates a systematic bias in your data. Your analytics over-represent the cookie-accepting segment and entirely miss the privacy-conscious segment, which often includes higher-value visitors.
The alternative
Cookieless analytics does not require a CMP for its operation because it does not use cookies or collect personal data. This eliminates the consent rejection data loss vector entirely while maintaining full GDPR compliance.
Related concepts
- GDPR Analytics ComplianceMeeting GDPR requirements for web analytics: lawful basis for processing, data minimization, purpose limitation, and — if using cookies — valid consent collection before tracking.
- Cookieless AnalyticsWeb analytics that captures visitor data without using browser cookies, enabling traffic measurement that doesn't depend on consent status or cookie restrictions.
- Data Loss in AnalyticsThe gap between actual website traffic and what analytics tools report. Caused by consent rejection, ad blockers, browser restrictions, and data sampling. Measured at 29% of visits on a real Shopify store; up to 87% in the EU worst-case model.
- Analytics Data ResidencyThe geographic location where analytics data is processed and stored. Under GDPR, data residency determines which legal frameworks apply and whether cross-border data transfer mechanisms (like SCCs) are required.