How We’re Improving Our Google Analytics Configuration

Over the past few weeks we have been reviewing the set-up of our Google Analytics tracking.

We had to update the tracking code embedded on all pages of the website. While we were doing this it seemed sensible to look at the whole set-up to make sure we are getting the most reliable data. We’ve been working with the digital agency, iProspect, on this project.

Account structure

The biggest change you’ll notice when you log in to analytics is the structure of our account. Everything has been consolidated into two properties:

  • internal.ncl.ac.uk
  • www.ncl.ac.uk – cross site tracking

The majority of our editors will be interested in data from external sites, so I’ll focus on what can be found in the www.ncl.ac.uk property. Within this property you will see a number of views. These allow you to access data for specific sub-domains, eg research.ncl.ac.uk, or applications, eg Hobsons.

There are also two views that allow you to look at data across all of the services, and see movement between them. They are:

  • 1. MAIN // incl. Microsites, Research, Conferences & Webstore – this gives access to filtered and de-duplicated data and should be used to report on activity from July 2016 onwards
  • 9. RAW – this gives access to unfiltered data and should be used only to report on activity before July 2016

Access to analytics

As part of this review we’re also looking at who has access to our account. This will include revoking access for anyone signed up with a personal email address. If you still need access to analytics we’ll ask you to re-register with a Google Account connected to your Newcastle email address.

Service development

Over the summer we’ll be taking some time to develop the analytics service we offer. This will give us time to collate 2-3 months of data in the new configuration.

We’ll be looking at access, reporting and analysis, as well as how we feed any recommendations back into content and template development.

Related posts

Share this post:
Share