{ "meta": { "type": "insight_article", "language": "en-GB", "last_updated": "2026-10-16", "ai_endpoint": "/insights/google-analytics-cookie-consent-and-the-bit-many-websites-get-wrong/ai.json", "source_page": "/insights/google-analytics-cookie-consent-and-the-bit-many-websites-get-wrong/" }, "retrieval_summary": { "what": "The article explains that adding Google Analytics to a website is straightforward, but ensuring it respects cookie consent is more complex.", "who": { "organisation": "Feel Created" }, "relevant_for": [ "Website owners and managers", "Digital teams", "Marketing and communications teams", "Analytics and reporting teams" ], "problems_solved": [ "Default GA4 implementations may begin tracking or using analytics storage before the visitor has made a consent choice, creating a potential compliance issue", "Blocking analytics completely can reduce visibility into website usage", "Consent-aware analytics can produce less complete reporting than traditional GA4 setups", "Analytics may not respond immediately when a visitor accepts cookies, leading to missing page views", "Cookie banners can become disconnected from the scripts and tools actually running on the website", "New marketing and third-party tools can cause consent implementations to drift over time", "Organisations may treat cookie consent as a one-off task rather than an ongoing part of website management" ] }, "page": { "title": "Google Analytics, cookie consent, and the bit many websites get wrong", "slug": "google-analytics-cookie-consent-and-the-bit-many-websites-get-wrong", "url": "/insights/google-analytics-cookie-consent-and-the-bit-many-websites-get-wrong/", "canonical_url": "https://www.feelcreated.com/insights/google-analytics-cookie-consent-and-the-bit-many-websites-get-wrong/", "status": "published" }, "article": { "type": "Insight article", "primary_topic": "Cookie consent and analytics implementation best practices", "intent": "The article explains that adding Google Analytics to a website is straightforward, but ensuring it respects cookie consent is more complex.", "author": { "name": "Dan Clark", "organisation": "Feel Created", "bio": "Lead Developer at Feel Created, focusing on the development of high-performance WordPress websites and bespoke digital solutions." }, "audience": [ "Website owners and managers", "Digital teams", "Marketing and communications teams", "Analytics and reporting teams" ] }, "topics": [ "Cookie consent and analytics implementation best practices", "Google Analytics 4 default tracking behavior", "Cookie consent compliance", "Google Consent Mode v2", "Cookieless tracking", "Cookie banner design", "Consent management integration", "GA4 and consent mode", "Privacy-focused analytics tools" ], "content_focus": [ "Compliance risks of default GA4 setup", "Trade-offs between blocking analytics and losing data", "How Google Consent Mode v2 works", "Practical expectations for data completeness after consent controls", "Implementation guidance for consent-aware GA4", "Risks and limitations of cookieless tracking", "Best practices for cookie banner design", "Integration of analytics and consent management", "Implementation guidance", "Governance considerations" ], "canonical_claims": [ { "claim": "With an appropriately configured Consent Mode implementation, Google tags can operate with restricted storage before analytics consent is granted, providing more limited measurement than consented GA4 tracking.", "evidence_type": "implementation", "evidence_strength": "medium", "source_section": "how-consent-mode-typically-works", "id": "claim-001" }, { "claim": "By default, Google Analytics starts tracking as soon as it loads, which can mean the site starts using cookies before a visitor has accepted them.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "adding-analytics-is-easy-getting-consent-right-is-harder", "id": "claim-002" }, { "claim": "A fully consent-aware GA4 setup will usually report less data than a traditional implementation, even when nothing has changed about the number of people visiting the website.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "what-cookieless-tracking-can-and-cant-tell-you", "id": "claim-003" }, { "claim": "Cookie consent should be reviewed regularly, similar to performance, security, accessibility, and content quality.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "keeping-cookie-consent-under-control", "id": "claim-004" }, { "claim": "Consent Mode does not replace the depth or consistency of data collected when visitors accept analytics cookies.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "the-middle-ground-google-consent-mode-v2-and-cookieless-tracking", "id": "claim-005" }, { "claim": "Cookieless tracking data can be inconsistent and should be treated as indicative rather than complete.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "what-cookieless-tracking-can-and-cant-tell-you", "id": "claim-006" }, { "claim": "A well-managed cookie consent implementation should not make the website more complicated for users.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "cookie-consent-isnt-a-one-off-project", "id": "claim-007" }, { "claim": "Improving GA4 and cookie consent usually does not require a complete rebuild.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "a-more-practical-way-forward", "id": "claim-008" } ], "services": [ { "name": "Website architecture & integrations", "relationship": "primary", "url": "/services/website-architecture-integrations/" }, { "name": "Custom WordPress development", "relationship": "supporting", "url": "/services/custom-wordpress-development/" }, { "name": "Website maintenance & support", "relationship": "primary", "url": "/services/website-maintenance-support/" } ], "sections": [ { "id": "adding-analytics-is-easy-getting-consent-right-is-harder", "heading": "Adding analytics is easy. Getting consent right is harder", "type": "section", "key_points": [ "Adding Google Analytics to a website is straightforward.", "At that point, it can feel like the job is complete." ], "content": [ { "type": "paragraph", "text": "Adding Google Analytics to a website is straightforward. Making sure it respects cookie consent is where many websites get caught out. You copy the GA4 tracking code, add it to the site, check that visits are coming through and move on. At that point, it can feel like the job is complete. The problem is that adding Google Analytics and making it compliant are not quite the same thing. By default, Google Analytics starts tracking as soon as it loads. That can mean the site starts using cookies before a visitor has accepted them, or before they have had a clear choice at all. For most website owners, this is not deliberate. Most are simply using the default setup without looking too closely at what happens when someone lands on the site. That is often where problems begin." } ] }, { "id": "the-default-ga4-implementation-is-not-always-enough", "heading": "The default GA4 implementation is not always enough", "type": "solution", "items": [ "analytics cookies get set too early", "tracking starts before a user has made a choice", "consent settings not matching the actual behaviour of the website", "reporting tools are in use before they should be" ], "content": [ { "type": "paragraph", "text": "Google Analytics 4 provides teams with a lot of useful reporting, but simply adding it to a website does not automatically make that website compliant. If the script loads straight away, it may begin collecting data and setting cookies before the user has interacted with your cookie banner. That creates a mismatch between what the website is doing and what the visitor has agreed to. In real terms, this can mean: This is one of the reasons cookie compliance involves more than just adding a banner. A banner is only the visible part. The more important question is what happens behind it. This rarely happens because organisations deliberately ignore privacy requirements. More often, Google Analytics was installed years ago using Google’s standard implementation, a cookie banner was added later, and nobody revisited how the two worked together. As new marketing tools, plugins and third-party services are introduced, the overall tracking configuration gradually becomes more difficult to understand." } ] }, { "id": "blocking-everything-can-solve-one-problem-but-create-another", "heading": "Blocking everything can solve one problem, but create another", "type": "section", "key_points": [ "That can be a clean compliance route.", "It does not set analytics cookies or track the visit." ], "content": [ { "type": "paragraph", "text": "The simplest compliant approach is to block Google Analytics completely until someone accepts analytics cookies. That can be a clean compliance route. If the user does not consent, the site keeps GA4 switched off. It does not set analytics cookies or track the visit. For some organisations, that may be perfectly acceptable. The downside is that you also lose a lot of visibility. If a large percentage of visitors reject or ignore the cookie banner, your analytics data becomes much less complete. You may lose early page views, entry behaviour and useful information about how people move around the site. That matters because teams often use analytics to improve content, check whether key journeys are working, understand campaign performance and spot issues in the user experience. So the question becomes: can you respect consent properly without significantly reducing the insight your analytics provide? In many cases, yes." } ] }, { "id": "the-middle-ground-google-consent-mode-v2-and-cookieless-tracking", "heading": "The middle ground: Google Consent Mode v2 and cookieless tracking", "type": "section", "key_points": [ "There is a more balanced way to handle GA4.", "This approach is often described as cookieless tracking." ], "content": [ { "type": "paragraph", "text": "There is a more balanced way to handle GA4. Google’s consent mode allows analytics to run in a limited state before a user has accepted cookies. This approach is often described as cookieless tracking. In simple terms, GA4 can collect limited information without storing analytics cookies or building a persistent user profile. You can still see broad interactions and page views, but visitors are not tracked at the same level of detail as someone who has accepted analytics cookies. Once consent is given, GA4 switches to full tracking and begins using analytics cookies. This gives website owners a more practical balance. Visitors are not fully tracked before giving permission, and organisations can retain some visibility into how their website is being used without compromising consent. In practice, however, it is worth setting realistic expectations. Consent Mode does not replace the depth or consistency of data collected when visitors accept analytics cookies. Even with a well-implemented GA4 setup, organisations should generally expect to see less analytics data than they were used to before introducing proper consent controls. That does not mean website traffic has fallen. It simply means fewer visits can be analysed in the same level of detail because not every visitor consents to analytics tracking." } ] }, { "id": "how-consent-mode-typically-works", "heading": "How consent mode typically works", "type": "section", "content": [ { "type": "paragraph", "text": "A better GA4 implementation usually starts with a default consent state, typically managed through a Consent Management Platform (CMP) and applied through Google Tag Manager or an equivalent tag management solution. When the page first loads, the site tells Google Tag Manager or GA4 not to use analytics or advertising storage. At that point, it only allows essential storage. Then, when the user selects an option in the cookie banner, the consent state is updated. If they accept analytics, GA4 switches to full tracking and begins using analytics cookies from that point onwards. If they reject analytics, it remains in its more limited state. Rather than assuming consent, the website follows a clear set of rules based on the visitor’s choice." } ] }, { "id": "consent-should-respond-straight-away", "heading": "Consent should respond straight away", "type": "section", "content": [ { "type": "paragraph", "text": "Something that often gets missed is what happens after someone accepts analytics cookies. Some implementations only start tracking properly on the next page load. That means the visitor may accept analytics, but the current page view is still not recorded unless they refresh the page or move to another page. The important detail is what happens next. When someone accepts analytics cookies, GA4 can load immediately. A small JavaScript event can also record the page they are already on, so analytics does not have to wait for a refresh or a second page view to catch up." } ] }, { "id": "what-cookieless-tracking-can-and-cant-tell-you", "heading": "What cookieless tracking can and can’t tell you", "type": "section", "content": [ { "type": "paragraph", "text": "Cookieless tracking is not magic, and it should not be mistaken for a complete replacement for normal analytics. Google’s documentation describes Consent Mode as a way of retaining useful insight before consent is granted, and it can certainly provide additional visibility compared with blocking analytics completely. Our experience implementing it across real websites, however, is that the data can still be inconsistent and should be treated as indicative rather than complete. Before consent, you can still retain visibility over page views, basic events, broad traffic patterns and general interaction data. What you will not get is the richer insight that relies on analytics cookies, such as persistent user journeys, detailed attribution or behaviour across multiple sessions. Even overall traffic reporting can differ more than organisations expect when compared with previous GA4 implementations. The compromise is still worthwhile because it supports a compliant implementation while retaining some understanding of website activity. The important thing is to recognise that a fully consent-aware GA4 setup will usually report less data than a traditional implementation, even when nothing has changed about the number of people visiting the website. Some organisations also choose to supplement GA4 with privacy-focused analytics platforms to provide a broader comparison of overall traffic levels, rather than relying on GA4 alone." } ] }, { "id": "cookie-banners-need-to-do-more-than-appear", "heading": "Cookie banners need to do more than appear", "type": "section", "items": [ "clear categories, such as analytics, marketing and preferences", "plain explanations of what each category means", "obvious options to accept, reject or customise", "a design that feels part of the website, not bolted on" ], "content": [ { "type": "paragraph", "text": "Many cookie banners are technically present but not particularly helpful. They give users a choice, but the language can be vague. The categories are not always clear, and the interface can feel like an afterthought rather than part of the website. A more considered consent experience should be easy to understand and easy to use. That usually means: The better approach is to look at the tools running on the site and build the consent experience around those choices." } ] }, { "id": "it-is-rarely-just-google-analytics", "heading": "It is rarely just Google Analytics", "type": "section", "items": [ "Meta or LinkedIn pixels", "embedded videos", "Google Maps", "live chat tools", "marketing automation scripts", "personalisation tools", "social media embeds" ], "content": [ { "type": "paragraph", "text": "GA4 is often the first thing people think about, but it is rarely the only script on a modern website. A site may also use: Each of these can introduce its own tracking behaviour. Some may set cookies or send data to third-party platforms. Others may need to stay inactive until the user has given a specific type of consent. Consent only works if the tools follow the choices made by the user. If they say no to marketing cookies, marketing tools stay off. If they only accept analytics, the site loads only the tools related to analytics. Any new script that gets added needs the same treatment; otherwise the implementation soon starts to unravel. That is often where websites become messy over time." } ] }, { "id": "cookie-consent-isnt-a-one-off-project", "heading": "Cookie consent isn’t a one-off project", "type": "section", "items": [ "managing scripts centrally", "setting clear consent categories", "putting each script in the right place", "checking new tools do not slip around consent", "testing what happens when users accept, reject or customise cookies" ], "content": [ { "type": "paragraph", "text": "We generally recommend treating analytics and consent as part of the same implementation rather than separate tasks. When tracking, tag management and consent are planned together, websites are easier to maintain and less likely to fall out of compliance as new tools are introduced. Websites change. Marketing teams add new tools. Analytics platforms update. Embedded content gets introduced. Campaign tracking evolves. If scripts span templates, plugins, theme files, and third-party snippets, it becomes much harder to understand what the site is loading and when. A more maintainable approach usually means: A well-managed implementation should not make the website more complicated for users. The aim is the opposite: clear structure behind the scenes, and a simpler experience on the front end." } ] }, { "id": "keeping-cookie-consent-under-control", "heading": "Keeping cookie consent under control", "type": "section", "content": [ { "type": "paragraph", "text": "It is easy to sort the banner once and assume that is enough. For a while, it might be. Then someone adds a new tracking tool, embeds a third-party service or changes how analytics works. That is when cookie consent needs a bit of housekeeping. This should be reviewed in the same way you would check performance, security, accessibility or content quality. The questions are practical ones: What data are we collecting? Why are we collecting it? Which tools are active on the site? Do users have a clear choice? Does the website behave in line with that choice? It is worth revisiting those questions whenever the site introduces new analytics, advertising or third-party tools." } ] }, { "id": "a-more-practical-way-forward", "heading": "A more practical way forward", "type": "section", "content": [ { "type": "paragraph", "text": "For most organisations, improving GA4 and cookie consent doesn’t require a complete rebuild. It usually means establishing consent before analytics runs fully, using cookieless tracking where appropriate, and ensuring every additional script follows the same consent rules. That is usually where a more considered setup pays off. Not just in compliance terms, but in the day-to-day management of the website. Cookie consent shouldn’t be treated as a box to tick after a website launches. Like accessibility, security and performance, it’s part of how a well-built website behaves every day. When analytics, consent and implementation work together, organisations gain better insight while giving visitors genuine control over their data. For organisations that rely heavily on reporting, it can also be useful to complement GA4 with privacy-focused analytics tools such as Cloudflare Web Analytics. These tools are not a replacement for Google Analytics and provide a much simpler view of website activity, but they can offer a helpful comparison point when interpreting traffic trends alongside consent-aware GA4 reporting. Taken together, this can provide a more balanced picture of website performance. GA4 continues to deliver detailed analysis for visitors who consent, while supplementary analytics can help validate overall traffic levels without relying on the same tracking approach." } ] }, { "id": "measuring-website-success-beyond-traffic", "heading": "Measuring website success beyond traffic", "type": "section", "content": [ { "type": "paragraph", "text": "Traffic tells part of the story. Learn how to measure website success by choosing the... 13 minutes read Read the guide" } ] }, { "id": "performance-monitoring-building-faster-more-reliable-websites", "heading": "Performance & monitoring: building faster, more reliable websites", "type": "section", "content": [ { "type": "paragraph", "text": "Understand how website speed, reliability, accessibility and ongoing monitoring work together to support better digital... 8 minutes read Read the guide" } ] }, { "id": "understanding-core-web-vitals", "heading": "Understanding Core Web Vitals", "type": "section", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] } ], "entities": [ { "name": "Consent Management Platform", "type": "Technology" }, { "name": "Google Analytics 4 (GA4)", "type": "Technology" }, { "name": "Cloudflare Web Analytics", "type": "Technology" }, { "name": "Google Consent Mode v2", "type": "Technology" }, { "name": "Google Tag Manager", "type": "Technology" }, { "name": "Meta Pixel", "type": "Technology" } ], "concept_relationships": [ { "subject": "Consent-aware GA4 reporting", "predicate": "provides", "object": "detailed analysis for consenting visitors" }, { "subject": "GA4", "predicate": "can be complemented by", "object": "privacy-focused analytics tools" }, { "subject": "Google Analytics 4", "predicate": "requires", "object": "cookie consent compliance" }, { "subject": "Google Consent Mode v2", "predicate": "enables", "object": "cookieless tracking" }, { "subject": "Cookie banner", "predicate": "is part of", "object": "cookie consent compliance" }, { "subject": "Cookie consent", "predicate": "affects", "object": "tracking accuracy" }, { "subject": "Cookie consent", "predicate": "requires", "object": "regular review" } ], "practical_guidance": [ { "guidance": "Ensure GA4 loads immediately when consent is accepted and record the current page view via a JavaScript event.", "importance": "high" }, { "guidance": "Consider using Google Consent Mode v2 to balance consent compliance with retaining some analytics visibility.", "importance": "medium" }, { "guidance": "Design cookie banners with clear categories, plain explanations, and obvious accept/reject/customise options.", "importance": "medium" }, { "guidance": "Set realistic expectations that data will be less complete after implementing proper consent controls.", "importance": "medium" }, { "guidance": "Review the default GA4 implementation to ensure analytics cookies are not set before user consent.", "importance": "high" }, { "guidance": "Review cookie consent whenever new analytics, advertising, or third-party tools are introduced.", "importance": "medium" }, { "guidance": "Establish consent before analytics runs fully and use cookieless tracking where appropriate.", "importance": "high" }, { "guidance": "Treat analytics and consent as part of the same implementation, not separate tasks.", "importance": "high" } ], "risk_areas": [ { "risk": "Analytics may begin collecting data or using analytics storage before the visitor has made a consent choice.", "impact": "The website's tracking behaviour may not match the visitor's consent choice or the organisation's intended consent configuration." }, { "risk": "New tracking tools or third-party services may be added without proper consent management.", "impact": "Compliance issues and loss of user trust." }, { "risk": "Websites becoming messy over time as new scripts are added without consent integration", "impact": "Compliance issues and tracking inaccuracies" }, { "risk": "Blocking analytics entirely until consent reduces data completeness.", "impact": "Loss of visibility into early page views, entry behaviour, and user journeys, affecting content improvement and campaign performance analysis." }, { "risk": "Incomplete tracking if consent response is not immediate", "impact": "Current page view may not be recorded, leading to data gaps" }, { "risk": "Inconsistent data from cookieless tracking", "impact": "Traffic reports may differ from previous implementations, causing confusion" } ], "common_misconceptions": [ { "misconception": "Cookieless tracking is a complete replacement for normal analytics", "clarification": "It provides additional visibility but lacks richer insights like persistent user journeys and detailed attribution" }, { "misconception": "Cookie consent is a one-off task to complete after website launch.", "clarification": "It requires ongoing management and review, similar to accessibility and security." }, { "misconception": "Adding a cookie banner makes a website compliant.", "clarification": "A banner is only the visible part; the more important question is what happens behind it, such as whether analytics scripts load before consent." }, { "misconception": "Google Analytics 4 is compliant by default.", "clarification": "Simply adding GA4 to a website does not automatically make it compliant; the script may collect data and set cookies before user interaction." } ], "technical_context": { "tracking_behavior": "Default GA4 starts tracking as soon as it loads, potentially setting cookies before consent.", "consent_mode": "Google Consent Mode v2 allows retaining insight before consent, with limitations on persistent user journeys and detailed attribution.", "data_impact": "Consent Mode does not replace the depth of data from full consent; expect less detailed analytics data.", "cookieless_tracking": "Provides visibility over page views, basic events, broad traffic patterns, and general interaction data before consent.", "consent_response": "GA4 can load immediately upon consent acceptance, with a JavaScript event to record the current page view.", "tools": [ "GA4", "Cloudflare Web Analytics" ], "concepts": [ "Cookieless tracking", "Consent categories", "Script management" ] }, "reasoning_paths": [ { "user_problem": "Default GA4 implementations may begin tracking or using analytics storage before the visitor has made a consent choice, creating a potential compliance issue", "evidence_refs": [ "claim-001", "claim-002", "claim-003" ], "relevant_sections": [ "the-default-ga4-implementation-is-not-always-enough", "cookie-consent-isnt-a-one-off-project", "how-consent-mode-typically-works" ] }, { "user_problem": "Organisations may treat cookie consent as a one-off task rather than an ongoing part of website management", "evidence_refs": [ "claim-004", "claim-007", "claim-008" ], "relevant_sections": [ "cookie-consent-isnt-a-one-off-project", "how-consent-mode-typically-works", "a-more-practical-way-forward" ] }, { "user_problem": "Analytics may not respond immediately when a visitor accepts cookies, leading to missing page views", "evidence_refs": [ "claim-002", "claim-005", "claim-001" ], "relevant_sections": [ "consent-should-respond-straight-away", "blocking-everything-can-solve-one-problem-but-create-another", "the-middle-ground-google-consent-mode-v2-and-cookieless-tracking" ] }, { "user_problem": "Cookie banners can become disconnected from the scripts and tools actually running on the website", "evidence_refs": [ "claim-004", "claim-007", "claim-008" ], "relevant_sections": [ "the-default-ga4-implementation-is-not-always-enough", "cookie-consent-isnt-a-one-off-project", "how-consent-mode-typically-works" ] } ], "content_profile": { "content_type": "Insight article", "primary_topic": "Cookie consent and analytics implementation best practices", "supporting_topics": [ "Google Analytics 4 default tracking behavior", "Cookie consent compliance", "Google Consent Mode v2", "Cookieless tracking", "Cookie banner design", "Consent management integration" ], "primary_audience": [ "Website owners and managers", "Digital teams", "Marketing and communications teams", "Analytics and reporting teams" ] }, "retrieval_topics": [ "Cookie consent and analytics implementation best practices", "Google Analytics 4 default tracking behavior", "Cookie consent compliance", "Google Consent Mode v2", "Cookieless tracking", "Cookie banner design", "Consent management integration", "GA4 and consent mode", "Privacy-focused analytics tools", "Google Analytics 4 implementation", "Cookie consent management", "Consent-aware analytics configuration" ], "organisation": { "name": "Feel Created", "url": "https://www.feelcreated.com/", "type": "Digital partner specialising in websites and digital platforms", "specialisms": [ "Digital strategy and planning", "User experience (UX) design", "Accessibility and inclusive design", "WordPress design and development", "Content strategy and information architecture", "AI-ready structured content", "AI Features & Integrations", "Search optimisation and technical SEO", "Website performance optimisation", "Website security and technical governance", "Platform architecture and integrations", "Content management systems", "Digital audits and reviews", "Creative and marketing support", "Website maintenance and support" ], "service_model": "We work as an extension of our clients' teams, combining strategy, UX, accessibility, content design, WordPress development and ongoing support to create digital platforms that help organisations communicate more clearly, work more efficiently and grow sustainably." } }