Can I Use Website Analytics Without Tracking Cookies?
Explore aggregate and server-side website measurement while understanding why cookieless analytics is not automatically anonymous or exempt from UK privacy rules.
Part of our guide: UK Website Compliance and Security: A Practical Guide for Small Businesses
You can measure useful website activity without conventional tracking cookies. Options include carefully configured aggregate analytics and analysis of server requests. However, “cookieless” does not automatically mean anonymous, consent-free or compliant.
Choose the questions you need to answer first. A small business may need to know which service pages attract useful enquiries, not follow every identifiable visitor across several websites.
Define the smallest useful measurement set
Start with page visits, broad acquisition sources and completed customer actions. Decide what business decision each measure supports.
Avoid collecting detailed behaviour simply because a dashboard offers it. More data can increase complexity without improving your decisions.
The guide to small-business website analytics helps separate useful measures from distracting totals.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Include analytics configuration and customer journeys in your post-launch website checks.
Understand the collection method
Ask whether the tool reads information from the visitor’s device, creates identifiers, uses fingerprinting, records full URLs or retains IP addresses.
A server-side product may still process personal information. A browser script can be cookieless while accessing device information covered by storage/access rules.
Compare the proposed configuration with the ICO’s explanation of storage and access technologies, rather than treating the absence of cookies as the conclusion.
Consider the statistical exception carefully
The ICO’s current exceptions guidance describes a limited route for aggregate service-improvement statistics.
It does not cover all analytics. Individual-level information should not be retained beyond necessary aggregation, and visitors need the required information and objection mechanism.
If your intended use includes advertising or decisions about particular people, do not stretch the exception to fit. Obtain advice on the actual setup.
Keep personal data out of event details
Do not put names, email addresses, message contents or sensitive form answers into analytics events or page addresses.
Check confirmation pages and query strings. A URL can accidentally carry information that then appears in analytics, logs and referrer data.
Use a generic event such as a completed enquiry, and verify successful server handling rather than counting every button click as a lead.
Accept measurement limits
Aggregate systems may not provide reliable returning-user counts or a complete cross-device journey. Browser restrictions, blocked scripts and consent choices can affect the sample.
Server requests also include bots, repeat loads and technical requests. They are not automatically a count of unique human visitors.
Treat reported numbers as measurements with a defined method, not a perfect record of every customer. Compare like-for-like periods and document configuration changes.
Review connected tools separately
A lightweight analytics setup does not make an embedded advertising pixel or call-tracking service exempt. Each integration needs its own assessment.
Keep your privacy notice accurate and use the cookie-banner guide to decide which controls the overall site needs.
The compliance guide provides a place to record the suppliers, purposes and responsible people.
Trial the system against real decisions
During a trial, check whether you can answer a practical question: which service page needs clearer information, or whether a form improvement reduced failed submissions.
Compare those findings with enquiry records and customer conversations. Do not collect invasive detail to resolve a question that a few direct enquiries could answer better.
If you would like a proportionate measurement plan for your website, contact AfterWorks. A qualified privacy adviser may be needed to confirm the legal basis for your chosen configuration.
