Tuesday, February 18, 2025

Can Google Analytics give an early warning of going viral?

Some years ago I found myself in the middle of a viral moment. It was a wild ride, involving a lion, Jimmy Kimmel and a world-famous university.

I worked for the University of Oxford at the time. My department, the central fundraising office, ran a central donation platform. Most of the colleges and departments had pages on the website to accept gifts. 

I happened to share an office with the staff who did the admin that accompanied donations. One afternoon, by pure chance, I happened to overhear two of them discussing how busy things were that day. My week rapidly unravelled.

It turns out that the illegal hunting of a lion had made the news around the globe. But this lion, known as Cecil, had long been monitored by the Conservation Unit at the University of Oxford. The head of their department somehow got invited onto the Jimmy Kimmel show to talk about the event. 

Lots of viewers were moved by the segment and wanted to give. And our donation platform was their destination. That day we had a 7,000% increase in the number of donations. It was a wild time, as we tried to keep the website up and make the most of the viral moment.

As I reflect, I often think - how could I get an early warning of this sort of event? Time is so critical when you have a large traffic surge. You might only have minutes before your website goes under. In this case I knew quickly because I happened to share an office with some staff from finance.

Could Google Analytics help me with this?

The best way I have found is to use Custom Insights. Sadly, there isn't enough space to provide a full guide to the feature here. Here is Google's guide to Custom insights.

For this particular purpose, the key was to set the evaluation frequency to Hourly. My tests have found that there's a sizeable delay for Daily frequency: email notifications come through 11-28 hours after the end of the day. That's far too long for this sort of situation.

By contrast, a Custom Insight based on Hourly frequency usually delivers results an hour after the time period concerned. For example, an insight from the period 9-10am on a particular day gets delivered by email at 11am that day. 

What metric do you use for the insight? In a viral situation I'm most concerned about the amount of work for the server. Will it fail? I think the best metric for this situation is Views. If you are cloud hosted, and are confident in your host's ability to scale up, then you may pick a metric based on maximising impact.

Hourly traffic is unusual: it currently doesn't show up anywhere in Google Analytics. So I had to experiment to set this up. To begin with I wanted to trigger the insight frequently, so I picked a low value for my test-site: 50 views an hour. Then I waited for the first notification. That came, so I was comfortable the mechanism was working. 

Over a period of a week I then boosted the trigger value to: 100, 200, 300 views. I kept going until I got to a level that wasn't reached with typical traffic fluctuations.

The currently value should give me a useful early warning for a viral surge. What would I do then? Probably all of these things:

  • Go to the Realtime reports to identify some details: Where is the traffic going? Which part of the world is it coming from? 
  • Warn my hosting provider and ask if they can increase the resources to the server.
  • Prepare my outage pages for the worst. Can I point to an alternative location, such as a social media post, that will help the users complete their task if the website fails?

If you're paying close attention, you'll notice that I said 'usually'. Why was that? Well, my experiments have found that Hourly Custom Insights aren't triggered in a portion of cases - about 7%. I guess one has to see this approach as a helpful aid rather than a fool proof system.

Can you see a better way to do this in Google Analytics, or another package? Do let me know via Blue Sky or Threads.




Tuesday, January 14, 2025

What does 'Email' mean in Google Analytics, and why are those numbers so small?

Email traffic is confusing in Google Analytics.

I suspect it's because there are both a variety of email providers and a variety of mechanisms for accessing that email. Whatever the reason, it's normal to be confused by the way email traffic is presented, or by the fact that said traffic is missing from a report.

Let's start with the Acquisition -> Overview screen in Google Analytics. Acquisition is all about how people come to your website (or app). On this page there may be rows labelled Email

Here's an example:

Google Analytics Acquisition Report

This screen should be simple. But no. [sigh]

These tables show channels in a particular grouping, designed for ease-of-use. The people (or sessions- there are two tables) in the Email channels are those that Google Analytics (GA) knows come via email. And it transpires that GA understands little about the people on that journey.


The quick answer

The Email Channel relates to people who come to your website via an email sent via email marketing software that has been set up correctly.

That's a narrow definition, which is why the numbers in this row are sometimes disappointing and occasionally absent.



The detailed answer

There are a few different situations to consider. All of these scenarios use email. Most do not provide data in the Email Channel by default. 

Let's imagine a fictional university called the University of Berkshire. Unsurprisingly, the University of Berkshire have a website. They've installed GA to track its usage.

Scenario 1 - people email a link to other people

Monica is thinking about going to an open day at the University of Berkshire. She thinks her friend Simon will also be interested. She emails him a link to the open day info on the University's website.

Simon opens the link in Monica's email and visits the University of Berkshire website.

In the GA account of the University, where was Simon's visit listed?

Not in the Email Channel of the Acquisition Overview, sadly. In this case Simon's visit was listed in the Direct Channel.


Scenario 2 - organisation emails a link to people

The University of Berkshire employ a communications officer called Fatema. Fatema emailed everyone who has registered for the open day. She used Mailchimp, the University's email marketing software, for the task.

Rebecca received the email Fatema sent in her Gmail account. She read it on the App on her phone and clicked on the link about accessibility considerations. How was Rebecca's visit recorded in GA?

In this case her visit was counted in the Direct Channel in the Acquisition Overview.

Note: this is usually the case, but not always. Unfortunately, the factors in email journeys throw up some quirks from time-to-time.


Scenario 3 - organisation emails a link to people - and have configured things correctly in advance

A few months later Fatema has learned more about connecting Mailchimp to GA. She set up Mailchimp to connect to the University of Berkshire's GA account.

She has just sent out an email asking for feedback about the open days. The email she sent linked to a feedback form on the University's website.

Rebecca opened the email and clicked through to the feedback form. How was Rebecca's visit recorded in GA?

In this case Rebecca's visit was counted in the Email Channel on the Acquisition Report. Hurray!

Also, in GA's Explorations section, Email was stored in any medium dimensions, for example the Session Medium Dimension. That means Fatema could set up an exploration to track the impact of her emails.


Scenario 4 - a different org emails a link to people - and have configured things correctly in advance

Erick is a business consultant. He runs a Substack email newsletter about marketing. He was impressed with a study from the University of Berkshire's Business School. He included a link to it in the latest issue of his newsletter.

Robert is a subscriber to Erick's newsletter. He read the latest issue and clicked through to learn about the study.

How was Robert's visit to the University website recorded in GA?

The answer: it appears in the Email Channel. The reason is that Substack connects with GA, even when the two accounts don't have the same owner. Not all email marketing tools do that, but Substack do.


In conclusion

This is why many people have a low number of acquisitions via email in GA: because their email marketing package isn't connected up. You can have a healthy email marketing campaign that converts well, and gives a low number in the Email channel.

It's not a disaster - email marketing software will give you analytics data, after all. But it does make it more difficult to compare the performance of the different channels you use for promotion.

We should also remember that some of our audience are emailing each other about our website/app. That positive activity currently goes untracked in GA.


More Google Analytics posts

So, what does Organic Search mean?

Should I care about average engagement time?


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