Showing posts with label privacy. Show all posts
Showing posts with label privacy. Show all posts

Monday, May 11, 2026

Four cookie consent tools you could use with Google Analytics

If you're in a country with privacy laws about cookies, then you may worry about Google Analytics. I'm based in the UK, and I was worried about Google Analytics.

One way to address Google Analytics' (GA's) use of cookies is to install a consent tool on your website (the grander offerings are often labelled 'cookie management platforms'). The idea is that the user says 'yes' or 'no' to the cookies used for GA. 

Here's an example from the University of Plymouth in the UK:

University of Plymouth consent tool

A number of companies offer consent tools. Here are four I've seen in use on UK websites, with examples of them installed. 

Inclusion isn't a recommendation. These four have different offerings and prices. You should test a consent tool works before you put it live.


Cookie Control

CIVIC's Cookie Control is used by the ICO (the UK privacy regulator). When I first installed a cookie consent tool, that provided extra reassurance to me. I'd be less cautious these days.

Some examples of Cookie Control:


Cookiebot

I like the design of Usercentrics' Cookiebot. Maybe that's just me. 

Some examples of Cookiebot in the wild:


CookieYes

I've seen CookieYes less than the others on this list. Perhaps it's a newer contender? 

Some examples of CookieYes in action:


OneTrust

OneTrust are the most common example I've seen for medium-sized and large organisations. 

At the time of writing, the digital agency Torchbox have said that a number of their clients have been hit with a big increase in charging. You may want to check their blog post before considering OneTrust.

Some examples of this consent tool:


There you have it: four cookie consent tools you could use to deploy Google Analytics. There are numerous others, but these are the most common that I've seen.


More Google Analytics posts

Privacy part 1 - where the data goes in Google Analytics 4

Can Google Analytics help us measure user satisfaction?



Tuesday, May 20, 2025

Privacy part 2 - what personal data is stored in Google Analytics?

How does Google Analytics affect the privacy of your audience? That's a good question to ask, not least because there may be legal implications to the answer.

In the first part of this series I looked at where the data on audience members goes. In this part I look at something more basic: what the data is.

As before there is a distinction between what Google know about a member of your audience, and what they let you know about that person. In this case I'm focusing on the latter, because it's hard to know the former (that is true of many companies, not just Google). 

Audience privacy all depends on how Google Analytics is set up.


Google Signals

You know the most about website visitors if you've enabled Google Signals in your Google Analytics (GA) settings. In that case GA will pull info about the audience from the Google accounts they use for their Android phones, their Gmail, their Google Docs, etc. But this only happens if they are logged in at the time of visiting your website, and using the same device.

Of course, a website visitor may use an iPhone, or a Yahoo email address or Microsoft Word. They may not even have a Google account. In that case, turning on Google Signals will not reveal any more information about them. 

When Google Signals is turned on, you see this information about your audience:

  • Age 
  • Gender
  • Interests - for example: 'Food & Dining/Cooking Enthusiasts/Aspiring Chefs'

For quieter websites, thresholding may hide this data about some audience members. I haven't done any testing around that functionality, so I'm unclear how effective it is. 

If you don't enable Google Signals, you'll find the fields listed above are empty in GA:

No data available

Granular location

Have you enabled Granular location and device data collection in the GA property? If so, then GA will store the city of website visitors. They label this 'city', and it can be that. But, it can also be a much smaller entity. For example, I've seen a UK village listed which has a population of 6,000. 

So, where a user lives affects how much privacy they are afforded by Google Analytics. Or does it? I say that because city seems to correspond to the location given by the Internet Service Provider (ISP) of the audience member. I've seen ISPs describe location accurately. I've also seen them give a location 30 miles away from the actual location of the user.


Data stored as standard

If neither of the above settings is enabled, then Google will show this information about visitors to your website:

  • Region (for example Florida )
  • Country 
  • Language


Data inferred from user actions

It might be possible to learn about a website visitor from their actions. A website visitor who visits a page designed for gambling addicts may be a gambling addict. Or they might just be interested in the subject.

You might have shared a page address with only a small group of people, and it may not be possible to get there without having the page address. In that case you would know that website visitors are one of that small group. 



Can you identify a website visitor?

In most cases it's not possible for you to identify an audience member. However, if a website has a low level of traffic it is possible to make an educated guess in combination with other information. 

Here's an example: imagine Murali is someone you met at an event last month. He said he was from Market Harborough in Leicestershire, UK. You check your stats this month and you see that you've had a visitor from Market Harborough. Is that the same person? 

If your website is quiet - say you get 100 visitors a month and only 5 are from the UK - then it's very likely to be the same person. But if you get 10,000 visitors a month from the UK, then you couldn't say that. 

Either way you could never prove it was Murali who visited.   


More Google Analytics posts

Privacy part 1 - where the data goes in Google Analytics 4

Can Google Analytics give an early warning of going viral?


Monday, November 11, 2024

Privacy part 1 - where the data goes in Google Analytics 4


Google Analytics collects data. That's the point, right?  We're in the data collection business, like pollsters, like scientists, like governments.

What does it collect? And where does that data end up?

I'm going to have a stab at explaining this. That will help you make informed decisions when setting up your Google Analytics account. Remember, there are laws about some forms of data.

To keep things manageable I'm only going to look at where data goes in this post. I'll talk about the nature of the data, the way it's used, and how long it's kept in future posts. You can follow me on Bluesky or Threads to learn about new posts as soon as they're published.

Let's begin. When you install Google Analytics (GA) on your website or app, data gets sent to four different places.

1. The data that goes to Google

When you install GA you begin passing information to Google about your website or app users. 

That's no surprise: GA needs to see that information in order to serve you. This approach is followed by most other website analytics packages, such as Matomo and Plausible. It's hard to imagine an approach to analytics that didn't do this.

Google is a large organisation which does many things. It's possible that data gets shared with other parts of the company as well as the GA team. For example, SEO experts sometimes say that the popularity of websites influences which of them are listed first in Google searches. How would Google know which websites are popular? Maybe they use data the comes into their organisation via GA.

There's one aspect of this that may surprise you: you're letting Google see more data than you can see yourself. For instance, GA sees the IP address of a user. It then filters that so you can't see the IP address of that user. 

Google's view of the user data can be blocked by the setup of the device. For example, use of a private window in the Firefox browser blocks tracking by GA.

2. The data that goes to you

The second place data ends up is, erm, you. When you login to GA you're seeing information about your users' behaviour. The data may end up on stored on your device if you have email alerts set up, or if you download it.

Remember that others with account access can see the data. Sometimes this access isn't appropriate. For example, it may be a Google Analytics Consultant who did some work for you in the past. 

3. The data that goes to them

When a user visits your website they are doing so virtually. That is, they're always using a device. That device could be a desktop, a laptop, a tablet, a phone, a console, a TV, etc

Data is stored on that machine. Not much, admittedly, but a small amount of data is stored by GA in the form of cookies. That information can be used to connect together other data and create a fuller picture.

4. The data that goes to other companies   

Lastly, let's talk about other companies. Did you connect your GA property to other systems?

For example, Zapier lets you trigger actions based on data in Google Analytics. In this case conversion data gets passed to Zapier.

(Disclosure: I use Zapier for my back office systems. It's not connected to the GA property installed on this website)


More Google Analytics posts