The current central University of Edinburgh (UoE) solution for web analytics uses a single Universal Google Analytics property to collect all data. This allows for visibility of user engagement across the wider web estate however also introduces heavy sampling to the data provided. This property is used widely across the university web estate, Website and […]
When it comes to deciding on your site’s analytics installation, you should consider the main objectives of your site, and the reporting capacity you have.
Separating internal and external audience data is essential to our understanding of usage in our web estate.
The marketing technology landscape is changing, and we need to think about our analytics and tag management solutions.
If there was an issue with the analytics on your site, how would you learn about it? Would it be when you went to create a report, and found out you’d lost a few weeks/months/years worth of data? I’m glad to say, there’s a better way.
This week, Google announced that new analytics properties would by default use “Google Analytics 4” (formerly, App + Web). What does that mean for The University of Edinburgh?
On Thursday 7 November 2109, I was asked to speak at the Squiz Summit on how we promote the work we do with our search engine, and how we analyse the performance of search. I realised I hadn’t blogged it previously, so thought I’d summarise here.
I’ve been thinking about the ways in which we align our digital products with wider strategic direction, and how we can measure whether the changes we make are working for our users and customers. In particular, I’ve been considering how we can make data-informed decisions about the University’s search service.
I recently ran a one-day workshop for IS web editors focused on teaching them how to iteratively improve their digital content so users are able to self-serve on their site. The event was a great success, with attendees leaving with an appreciation for what it takes to create user-focused content.
We’re hosting a one-day workshop for IS web editors to learn how to iteratively improve your webpages as a means to promote self-service and reduce support calls. Book a place to attend the event on 29 March.