What data do we really need to collect from our website? Cookies, pixels, fingerprinting and other tools are now considered under a single consideration in the latest ICO guidance. This means it is important to consider what data can be collected from users on a website, and to what extent. For most site owners, this means asking yourself: “What do we genuinely need, and under what conditions can we collect it?”

The GOV.UK’s service manual provides useful recommendations, suggesting that first and fore most tools should be used appropriately to reduce the collection of personal data. For example, IP addresses should be anonymised whenever possible, and cookies should be loaded in a compliant way according to the guidance.

Are we tracking too much?

Many sites have accumulated a lot of installed tools to collect data. These may include analytics, remarketing, heatmap, survey and social tools, or may be added in response to requests for “more insight”. Over time, this can cause a site to collect far more data than makes sense for the team to be collecting.

Instead, it is better to think about this in reverse. What decisions do you need to make? For example, do you need to know which pages are bringing traffic via search? Which forms are failing? Which landing pages in campaigns are converting? Or are many of these reports simply a long list of vanity metrics?

If you cannot link the data collected to a decision, it may not be worth collecting.

It is not necessarily the case that you should stop collecting any data. However, it may be helpful to consider:

  • Essential data to make basic decisions about your site and reporting
  • Data to make decisions on content, UX or marketing
  • Convenience, novelty or habitual data

Data in the first category will usually be easier to justify. Data in the second category requires more consideration. Data in the third category will often be easier to remove.

Collecting less but getting more from your data

Most sites do not need an extensive amount of tracking to make good decisions. However, they will need to ensure that if they do have tracking, it is set up correctly.

Many organisations will be able to set up their analytics to reduce personal data collection, and align with consent. GOV.UK provides a useful note to remind us that we do not want to be collecting as much data as possible, but rather enough to support the service (GOV.UK Service Manual).

While this seems obvious, it can make a big difference. If you need to add multiple tags, custom dimensions and third party scripts to provide a report, consider whether you will actually make decisions as a result of the data. If not, it is unlikely to be worth the increase in complexity.

Things that it is worth considering at this point include:

  • Are we using this data to help improve our pages, journeys or campaigns?
  • Can we clearly explain it in our cookie and privacy policies?
  • Does it still function for users who have not given consent to optional tracking?

If you answer “no” to all three questions above then you should probably reconsider the current data collection setup as there isn’t a clear enough justification for retaining it.

GDPR compliance – GA4, Tag Manager and consent

Although GA4, GTM and CMPs can all work together well, they should be considered separately. Just because they are in place, doesn’t mean that they are set correctly.

Google Analytics 4 (GA4) is used for reporting how users are arriving at the site and navigating the content. Google Tag Manager (GTM) is used to implement the tracking tools on the site. The Consent Management Platform (CMPs such as Civic UK, Cookiebot, and CookieYes) should allow users to control which categories of cookies they accept. If these 3 tools don’t work well together, cookies may be loaded without consent, and data may be collected in a way that does not match with what your cookie banner tooling states, making your site non-GDPR compliant.

This is an area where many teams struggle. Having a banner does not mean you’re compliant.

Using server-side tagging can help to reduce a sites reliance on third party cookies, and should provie more control to site owners over where and how data is sent. However, it’s still important to understand and make clear decisions on what data you are sending. As a site owner you must consider what types of data to allow through, what should be blocked, and ensure you have given due attention to what users have consented to. This is not a method for avoiding having to ask for consent but it is an improvment in data routing.

Some useful things to check are:

  • Are tags paused until consent is given where appropriate?
  • Have we limited analytics to essential data?
  • Are marketing tags being treated differently to essential data?
  • Are reports still meaningful for users that have not given tracking consent?

If not, there may be an issue with how your tags are set up.

Search metrics and website analytics

Documentation for search has also changed. With the latest updates to Google Search Console, it is clear that search reporting, AI visibility and on site analytics are now very different considerations (Google Search Central Updates). This means that “traffic” is no longer a single number to consider.

Search Console will show you how your site appears in Google search results. Analytics will show you user behaviour on site, depending on how tracking is set up. AI visibility adds yet another layer, meaning the data may not always match up well.

If your team require a single answer, be clear with the limitations of each tool, providing your team members with context for each tools outputs. For example, receiving more recorded impressions in Search Console does not necessarily mean that the site is getting more actual visits just that it is appearing in more search results. Similarly, if you’re seeing fewer user sessions in GA4 it could well be because your users not not consenting to cookies rather than that your site is receiving less traffic. Also, new AI search tools may provide reports that show visibility of your content that is not trackable in your standard search engine focussed reporting, meaning your site and brand may be more visible than it appears.

To avoid confusion, be clear with where the data is coming from. If you do not, you may find people getting into arguments about the method of measurement.

Forms, logins and other website journeys

Only if journeys are usable will measurement be useful. This applies to forms, logins, bookings, donations and any other interaction where the user must perform an action to gain value.

W3C provides some good guidance on making forms more accessible, which includes ensuring you’ve added clear labelling, optimised the form layout for users, provided clear user focussed instructions, ensured that form validation is timely and clear, and that you provide a feedback mechanism (W3C Forms Tutorial). For multi-step forms the guidance recommends breaking long pages of fields into logical steps and providing a clear progress status (W3C Multi-step Forms). The GOV.UK site’s basic accessibility checklist also includes some practical guidance for forms including labelling, confirmation codes and logins (GOV.UK Accessibility Check).

This is important to consider as analytics may simply show you where users drop off, but not necessarily why. If a donation form is poorly validated, unclear or difficult to complete in multiple steps, analytics may just show you that users dropped off. It may not give you insight into why users dropped off, such as struggling to enter a postcode, or difficulty pasting the confirmation code, or not understanding why they need to create an account.

To get the most out of measurement, it is best to combine it with manual checks. Have a look at the journey, test on mobile devices, and see where users seem to struggle. If you only check analytics, you will be missing half of the story.

When should you review your tracking and analytics setup?

Making decisions around when cookies and analytics should be reviewed is a key site management task. They should be reviewed on a schedule rather than treated as a one time piece or work, preferrably at least once a year. There are also some events or situations that may also trigger you to want to review your setup:

  • You’ve updated or changed your consent banner
  • You’ve redesigned your site, or have migrated CMP provider
  • You’ve added a new tooling to the site that requires data collection, management and storage, for example changes to a booking, donation, or login process
  • Your GA4, Tag Manager or server side tagging setup has been updated

If you have added tracking tools or new features that store user data over time without having a clear review process in place, it is usually advisable to run a quick technical audit to help identify where they may be bloat and where your policies may not match your practices. This often highlights which tags are still providing value, which are no longer providing value, and where the consent set up does not match with the reality of the site.

If you would like assistance with GDPR and cookie compliance, or an audit of your analytics, we can help make this simpler!

If you enjoyed reading this article you may also like…