The first thing many websites say to a new visitor is not the proposition, the proof or the reason to care. It is a request for data.
That request is usually delivered through a generic pop-up written by a plugin, styled as an afterthought and designed to make one choice much easier than every other choice.
Businesses spend months refining their positioning, then open the relationship with an interface that feels evasive. That is not only a compliance problem. It is a brand problem.
The measurement environment changed again
In April 2026, the UK Information Commissioner's Office published final guidance covering cookies, tracking pixels, device fingerprinting, scripts, tags and other storage and access technologies. The guidance reflects changes introduced by the Data (Use and Access) Act and includes updated material on exceptions, consent and online advertising.
Then, from 15 June 2026, Google Analytics changed how some data controls work. Google says Consent Mode within Google Ads now acts as the single control governing how advertising cookies and identifiers are collected and used for linked advertising purposes.
The practical message for leadership teams is simple. Consent design, analytics configuration and marketing measurement can no longer live in separate boxes owned by separate suppliers.
This article is not legal advice. Your requirements depend on your data, technologies, purposes and markets. The current ICO guidance and advice specific to your organisation should lead the compliance decision.
A banner is a trust interaction
Visitors notice when a business says one thing and designs another.
A brand may claim to be transparent while hiding "reject" behind a second screen. It may claim to be customer-first while using a bright primary button for "accept all" and a low-contrast text link for everything else. It may claim to value simplicity while presenting a wall of legal language before the page can be used.
These are dark patterns, even when they arrive inside a respectable consent platform. They use visual hierarchy to push a decision rather than support one.
Good consent design makes the choices understandable and balanced. It tells people what will happen, why it matters, and how they can change their mind. It does not punish the answer the business would prefer not to receive.
What a well-designed consent experience needs
Plain language
"We use analytics to understand which pages help people and where they get stuck" is more useful than "We and our partners process identifiers for legitimate business purposes". The detailed legal information can still exist, but the first layer should help a normal person make a real choice.
Honest visual hierarchy
Accept, reject and manage options should be easy to find and use. Button weight, colour, placement and contrast should not manipulate the outcome. If one choice is prominent and the alternative is designed to disappear, the interface is not neutral.
Purpose before vendor
Most people do not know or care which tag vendor supplies a script. They care what the script does. Group choices around understandable purposes such as essential operation, audience measurement, personalisation and advertising.
A persistent route back
Consent is not meaningful if preferences disappear after the first visit. Include a clear, permanent way to review or withdraw choices, normally through the footer or privacy area.
Correct behaviour behind the design
A beautiful banner is useless if tags fire before the visitor has made a choice or if the website ignores the preference. Design and implementation have to be tested together.
First-party data is not a permission slip
Marketers increasingly describe first-party data as the answer to disappearing identifiers and incomplete attribution. It is important, but the phrase is often used too loosely.
First-party data is information collected through a direct relationship, such as an enquiry, purchase, account, event registration or email subscription. Its real value is not that it bypasses privacy. Its value is that it comes from an intentional relationship with context.
Google Analytics supports consented user-provided data, including information that is hashed before transmission, to improve measurement and features such as enhanced conversions. That is a technical option, not a strategy in itself.
A sound first-party approach starts with value exchange:
- What is the customer choosing to receive?
- Why is the requested information necessary?
- How will it improve the service or communication?
- How long will it remain useful?
- Can the customer easily change their preference?
Measure fewer things better
The response to weaker tracking should not be more tracking. It should be better measurement design.
Define the decisions the business needs to make. Identify the small number of events that provide useful evidence. Connect real outcomes from the CRM or sales process where appropriate. Stop collecting behavioural detail simply because a platform makes it possible.
A focused measurement plan is easier to explain, easier to govern and more likely to be used. It can also make the consent request shorter because the business has made a deliberate choice about what it actually needs.
A practical review for this quarter
- List every cookie, pixel, tag, script and storage technology currently in use.
- Record the purpose, provider, duration, legal basis or exception relied upon, and the pages where it operates.
- Check what happens before consent, after rejection and after preferences are changed.
- Review Google Analytics and Google Ads consent settings together.
- Rewrite the banner in plain language and test whether the visual choices are genuinely balanced.
- Remove data collection that nobody can connect to a business decision.
The cookie banner is not a temporary obstruction between the visitor and the real brand experience. It is already part of the real brand experience.
If your website needs clearer journeys, stronger trust and measurement designed around useful decisions, talk to Ayuda.
Sources and further reading
- ICO: Guidance on storage and access technologies
- Google Analytics: Updates to data controls
- Google Analytics: User-provided data collection
Frequently Asked Questions
Can a website set analytics cookies before consent?
It depends on the technology, purpose, applicable exceptions and current law. Follow current ICO guidance and obtain advice for your specific setup.
Is first-party data automatically compliant?
No. The term describes the collection relationship. It does not remove the need for transparency, governance and an appropriate legal basis.
What makes a good cookie banner?
Plain language, balanced choices, clear purposes, correct tag behaviour and an easy route to change preferences.