This guide summarises public regulator guidance for practitioners. It is not legal advice.
The short answer
Privacy rules decide who your analytics and testing tools can measure. That changes your data in ways that matter for CRO:
- In the EU, analytics cookies generally need opt-in consent.
- In the UK, a newer statistical purposes exception can allow some analytics without consent, with conditions.
- Everywhere, consent and ad blockers mean your tools see a sample, not everyone.
What the guidance says
EU (GDPR and ePrivacy)
Under GDPR, valid consent must be freely given, specific, informed and unambiguous. The European Data Protection Board’s guidance adds points that matter for banners (EDPB, 2020):
- Cookie walls (no access unless you accept) don’t produce valid consent.
- Scrolling or continuing to browse is not consent.
- Withdrawing consent must be as easy as giving it.
UK (PECR)
PECR requires consent to store or access information on a device unless an exception applies. Following the Data (Use and Access) Act 2025, the ICO’s guidance describes a “statistical purposes” exception, which can cover some analytics when people are given clear information and a simple means of objecting (ICO). The conditions matter, so read the guidance before relying on it.
Elsewhere
Many places, including most US states, allow analytics by default with an opt-out, though some state laws and sector rules add requirements. Check what applies to your audience.
What consent does to your data
- Totals undercount. If 60% of visitors accept, analytics sees roughly 60% of sessions. Your backend orders won’t match analytics purchases.
- Rates may be biased. People who accept cookies may behave differently from those who don’t. Conversion rates are estimates for consenting users.
- Trends can break. Changing your banner changes who you measure. Note the date in your tracking plan.
- Tests see consenting users only (if your testing tool needs consent). Results apply to that group; that’s usually fine, but say so.
Google Consent Mode
Consent Mode lets Google tags adjust to the consent state, using signals such as analytics_storage and ad_storage, and supports different defaults per region (Google for Developers). It’s a technical layer. It doesn’t make your setup compliant on its own: you still need a fair banner and records of choices.
An honest setup that keeps data useful
- Ask clearly. One short sentence, equal Accept and Reject buttons, a link to the privacy policy.
- Set defaults by region to match the rules that apply.
- Make changing your mind easy: a “Cookie settings” link in the footer.
- Measure the consent rate itself (in aggregate), so you know how big your sample is.
- Use first-party backend data (orders, sign-ups) as the source of truth for business totals.
- Treat the banner as a page element: it shouldn’t cover the main content or the buy button on mobile.
What to do next
Note your consent setup and its start date in your tracking plan, and see GA4 for CRO for reading the data you do have.