Every business wants to understand its website visitors.
Which pages attract attention? Where do people lose interest? Which marketing channels generate enquiries? Google Analytics 4 can help answer these questions, but only when data is collected responsibly.
Visitors increasingly expect to know when a website is tracking their behaviour. They also expect their choices to be respected. A cookie banner that looks correct but does not actually control Google Analytics creates a false sense of privacy.
Responsible analytics is not about choosing between useful data and visitor trust. It is about creating a setup that supports both.
GA4 uses cookies and related technologies to recognise browsers, distinguish users and understand activity across multiple pages or visits.
This allows reports to show information such as user engagement, traffic sources, returning visitors and conversion journeys.
The problem is that analytics cookies are not normally essential for the website to function. A visitor can still read a page, use the navigation or complete a contact form without being tracked by Google Analytics.
For UK websites, the Privacy and Electronic Communications Regulations generally require businesses to provide clear information and receive valid consent before setting non essential cookies. Other regions may have different requirements, so businesses should consider where their visitors are located and obtain appropriate legal guidance.
Adding a cookie banner does not automatically make an analytics setup responsible.
The banner is simply the interface through which visitors communicate their choices. Those choices must then control what happens behind the website.
Imagine that a visitor opens a website and selects “Reject all”. The banner closes, but the GA4 tag has already loaded and created analytics cookies. From the visitor’s perspective, they declined tracking. From the website’s perspective, tracking has already started.
This is a common implementation problem.
A correctly configured consent system should connect the banner with Google Analytics, Google Tag Manager and any other tracking tools used by the website.
Consent should be clear, informed and based on a positive action.
The banner should explain that analytics cookies are used to understand how people interact with the website. Visitors should be able to accept or reject them without searching through several screens.
Avoid designs that make the accept button bright and prominent while hiding the reject option in small or low contrast text. This may increase the acceptance rate, but it does not create a transparent experience.
A good banner normally allows visitors to understand the main choices quickly and access more detailed information when needed.
The website should also provide a way to change those preferences later. A visitor who accepts analytics today may decide to withdraw consent in the future.
Google Consent Mode allows Google tags to adjust their behaviour according to the consent choice made by a visitor.
The website communicates whether permission has been granted or denied for different types of storage and data use. For analytics, the relevant setting is analytics_storage.
When analytics storage is granted, GA4 can operate normally. When it is denied, the behaviour depends on whether the website uses basic or advanced consent mode.
With basic consent mode, Google tags are blocked until the visitor grants consent. If consent is not provided, no data is sent to Google.
With advanced consent mode, Google tags can load with consent denied and send limited measurements without analytics cookies. Google may use these signals for modelling, subject to eligibility requirements.
The appropriate approach depends on the organisation’s legal requirements, privacy policy and measurement needs. Consent Mode helps tags respond to visitor choices, but it does not provide a cookie banner or obtain consent by itself.
Timing is one of the most important parts of the setup.
The default consent state should be established before GA4 sends measurement data. If the analytics tag loads first and the consent tool updates the setting afterwards, tracking may already have occurred.
When a visitor makes a choice, the consent state should update immediately on the same page. Their preference should also be remembered so that the correct setting applies during future visits.
This often requires coordination between the cookie platform, Google Tag Manager and the website itself. Installing each tool separately without checking how they communicate can create gaps in the process.
Responsible analytics is not limited to cookie consent. It also means avoiding unnecessary data collection.
A business website does not need to record every click simply because it is technically possible.
Start with interactions that answer meaningful questions. These might include successful form submissions, consultation bookings, important downloads and engagement with key service pages.
Never send personally identifiable information such as names, email addresses or telephone numbers to Google Analytics. Form events should confirm that a submission occurred without including the personal information entered into the form.
Event parameters should also be reviewed carefully. Page URLs, form names and button labels can sometimes contain information that was never intended for analytics reports.
A smaller, well planned data set is often more useful than hundreds of events without a clear purpose.
A banner should be tested as carefully as a contact form or checkout.
Open the website in a private browser window and observe what happens before making a choice. Then test accepting analytics, rejecting analytics and changing the preference later.
Check whether analytics cookies appear and whether GA4 events are sent in each state. Google Tag Manager Preview mode and Tag Assistant can help confirm how tags respond to the selected consent settings.
Testing should cover multiple pages because the homepage may behave correctly while a blog template, embedded form or landing page loads a separate tracking script.
It is also worth checking mobile devices and browsers with stronger privacy settings.
A cookie policy should reflect what the website currently uses, not what it used when the policy was first written.
Website tools change over time. A new video player, booking platform, chatbot or advertising pixel may introduce additional cookies or tracking technologies.
Review the website regularly and update the consent categories and cookie information when tools change.
The explanation does not need to overwhelm visitors with technical language. It should clearly describe what each category does, why the data is collected and whether information is shared with another provider.
Transparency becomes more valuable when people can actually understand it.
At first, consent may appear to reduce the amount of information available in GA4. Some visitors will reject analytics, which means reports may not represent every website visit.
However, collecting more data does not automatically create better decisions.
A responsible setup produces data with clearer boundaries. The business understands how the information was collected, which visitors may not be represented and what limitations should be considered when reading reports.
This is more useful than a larger data set created through an unclear or incorrectly configured consent process.
Trust also matters beyond analytics. Visitors who feel that a website respects their choices may be more comfortable completing a form, creating an account or returning in the future.
Google Analytics and cookie consent should be designed as one connected system.
The banner should clearly explain the choices available. The consent decision should control how GA4 behaves. Analytics should collect only useful information, avoid personal data and be tested across the complete website.
Most importantly, a business should understand what happens after a visitor selects accept or reject.
Responsible data collection does not make analytics less valuable. It creates a stronger foundation for understanding website performance while respecting the people behind the numbers.
Add to Preferred Sources