Define the question before choosing the platform

Begin with the decisions you genuinely need to make. Are visitors finding the contact page? Which articles attract readers? Does an important form fail on mobile? These questions may be answered with less information than a detailed history of each visitor’s activity.

Write down the proposed report and who will use it. A simple list of necessary measures is a better procurement brief than asking for every available tracking feature. It also helps prevent gradual expansion: a team can see when a new request changes the original purpose rather than merely improving the same report.

The exception is conditional

The ICO describes a statistical-purpose exception for collecting information about use of a service with a view to improving it. It is directed at aggregate statistics, not identifying or monitoring particular people. Individual-level personal information used in producing those statistics must not be kept longer than necessary for that aggregation.

The conditions include clear information and a simple, free objection mechanism. Third-party use must remain within the permitted service-improvement purpose. This is not a general permission for advertising attribution, cross-site tracking or individual decisions. Whether a proposed setup qualifies depends on the whole implementation, not merely the name of the dashboard.

Ask specific questions about the data flow

Our recommended supplier questionnaire starts with the event itself. What leaves the browser? Are full page addresses or query strings included? Could those contain an email address, an account reference or details entered into a form? Is a persistent identifier created? Can staff drill down to a particular visitor or export an individual activity record?

Then ask what happens after collection. When are records aggregated or discarded? Does the provider use information for its own products or combine it with other customers’ data? Which settings are optional, and which cannot be switched off? A short written answer tied to your configuration is more useful than a general statement that the product respects privacy.

Cookieless is a technical description, not the conclusion

PECR concerns device storage and access, not only files labelled cookies. A mechanism may avoid traditional cookies but still need assessment under those rules. Conversely, the question is not settled by assuming every measurement necessarily needs consent. Identify what actually happens.

If personal data is processed, UK GDPR remains relevant even where PECR consent is not required. Consider the lawful basis, transparency, minimisation, security and relevant supplier arrangements. Removing a consent popup does not remove the need to understand the information being processed or to explain it accurately.

Design an objection route that works

Do not hide the visitor’s choice in a page that only a developer can understand. We recommend a plain-language analytics section explaining what is measured and a clearly labelled control where an objection mechanism is required. Test it on the same devices and journeys as the measurement itself.

A local browser preference is not necessarily an account-wide preference. If that is how the mechanism works, explain its scope and what happens if browser storage is cleared. Do not imply that a business recognises a visitor across every phone and computer merely because one browser is excluded. Test the resulting network activity rather than relying only on a success message.

Keep a measurement plan, not just a script

Record the selected settings, purpose, supplier commitments and test results. Limit access to the dashboard. Review new features before enabling them, especially those linking website activity to named contacts, advertising audiences or sales records. Such features can materially change the assessment.

Finally, accept the limits of the figures. Browser restrictions, objections and other technical factors can affect counts; a dashboard is not a perfect census of attention. For many smaller businesses, a consistent, proportionate picture of trends is more useful than invasive precision. Choose the lightest setup that answers a worthwhile question and verify it against the applicable rules.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.