Google Analytics, cookie consent, and the bit many websites get wrong
Source page: https://www.feelcreated.com/insights/google-analytics-cookie-consent-and-the-bit-many-websites-get-wrong/
Structured JSON: https://www.feelcreated.com/insights/google-analytics-cookie-consent-and-the-bit-many-websites-get-wrong/ai.json
This page is generated automatically from the same reviewed FC AI data as the JSON version.
Meta
Type: insight_article
Language: en-GB
Last updated: 2026-10-16
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
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
Item 1
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
Item 2
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
Item 3
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
Item 4
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
Item 5
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
Item 6
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
Item 7
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
Item 8
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
Services
Website architecture & integrations
Relationship: primary
Url: /services/website-architecture-integrations/
Custom WordPress development
Relationship: supporting
Url: /services/custom-wordpress-development/
Website maintenance & support
Relationship: primary
Url: /services/website-maintenance-support/
Sections
Adding analytics is easy. Getting consent right is harder
Key points
- Adding Google Analytics to a website is straightforward.
- At that point, it can feel like the job is complete.
Content
Item 1
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.
The default GA4 implementation is not always enough
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
Item 1
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.
Blocking everything can solve one problem, but create another
Key points
- That can be a clean compliance route.
- It does not set analytics cookies or track the visit.
Content
Item 1
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.
How consent mode typically works
Content
Item 1
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.
Consent should respond straight away
Content
Item 1
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.
It is rarely just Google Analytics
Items
- Meta or LinkedIn pixels
- embedded videos
- Google Maps
- live chat tools
- marketing automation scripts
- personalisation tools
- social media embeds
Content
Item 1
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.
A more practical way forward
Content
Item 1
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.
Measuring website success beyond traffic
Content
Item 1
Text: Traffic tells part of the story. Learn how to measure website success by choosing the... 13 minutes read Read the guide
Performance & monitoring: building faster, more reliable websites
Content
Item 1
Text: Understand how website speed, reliability, accessibility and ongoing monitoring work together to support better digital... 8 minutes read Read the guide
Understanding Core Web Vitals
Content
Item 1
Text: More information coming soon Coming soon
Entities
Consent Management Platform
Google Analytics 4 (GA4)
Cloudflare Web Analytics
Google Consent Mode v2
Google Tag Manager
Meta Pixel
Concept relationships
Item 1
Subject: Consent-aware GA4 reporting
Predicate: provides
Object: detailed analysis for consenting visitors
Item 2
Subject: GA4
Predicate: can be complemented by
Object: privacy-focused analytics tools
Item 3
Subject: Google Analytics 4
Predicate: requires
Object: cookie consent compliance
Item 4
Subject: Google Consent Mode v2
Predicate: enables
Object: cookieless tracking
Item 5
Subject: Cookie banner
Predicate: is part of
Object: cookie consent compliance
Item 6
Subject: Cookie consent
Predicate: affects
Object: tracking accuracy
Item 7
Subject: Cookie consent
Predicate: requires
Object: regular review
Practical guidance
Item 1
Guidance: Ensure GA4 loads immediately when consent is accepted and record the current page view via a JavaScript event.
Importance: high
Item 2
Guidance: Consider using Google Consent Mode v2 to balance consent compliance with retaining some analytics visibility.
Importance: medium
Item 3
Guidance: Design cookie banners with clear categories, plain explanations, and obvious accept/reject/customise options.
Importance: medium
Item 4
Guidance: Set realistic expectations that data will be less complete after implementing proper consent controls.
Importance: medium
Item 5
Guidance: Review the default GA4 implementation to ensure analytics cookies are not set before user consent.
Importance: high
Item 6
Guidance: Review cookie consent whenever new analytics, advertising, or third-party tools are introduced.
Importance: medium
Item 7
Guidance: Establish consent before analytics runs fully and use cookieless tracking where appropriate.
Importance: high
Item 8
Guidance: Treat analytics and consent as part of the same implementation, not separate tasks.
Importance: high
Risk areas
Item 1
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.
Item 2
Risk: New tracking tools or third-party services may be added without proper consent management.
Impact: Compliance issues and loss of user trust.
Item 3
Risk: Websites becoming messy over time as new scripts are added without consent integration
Impact: Compliance issues and tracking inaccuracies
Item 4
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.
Item 5
Risk: Incomplete tracking if consent response is not immediate
Impact: Current page view may not be recorded, leading to data gaps
Item 6
Risk: Inconsistent data from cookieless tracking
Impact: Traffic reports may differ from previous implementations, causing confusion
Common misconceptions
Item 1
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
Item 2
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.
Item 3
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.
Item 4
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
Item 1
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
Item 2
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
Item 3
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
Item 4
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
Type: Digital partner specialising in websites and digital platforms
Url: https://www.feelcreated.com/
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.