Edit
Contact us
Salocin Group Leaders in data and AI-enabled connected customer experiences
Edit Engineers of connected customer experiences
Join the Dots Independent, data-led media thinking for sustainable growth
Wood for Trees Optimisers of future fundraising performance
  • Home
  • Our services
    • Cloud solutions
    • Data science
    • Modern Data Platform
    • Privacy and AI compliance
  • Our partners
    • Apteco
    • Creatio
    • Microsoft
    • Salesforce
  • Our insights
    • Blog
    • Case studies
    • Reports
    • Webinars
    • Whitepapers
  • About Salocin Group
    • Careers
  • Contact Salocin Group
  • Home
  • Who we are
    • B Corp
    • Careers
  • Our work
  • What we do
    • Intelligent data
    • Marketing technology
    • Transformational CRM
    • Our technology partners
    • Privacy review
  • Our insights
    • Blog
    • Case studies
    • Reports
    • Webinars
    • Whitepapers
  • Contact Edit
  • Home
  • Broadcast media
  • Digital media
  • Print
    • Direct mail
  • Data
    • Our work with Herdify
    • EPiC
  • Media agency
  • Our insights
    • Blog
    • Case studies
    • Reports
    • Webinars
    • Whitepapers
  • About Join the Dots
    • Careers
  • Contact Join the Dots
  • Home
  • Services
    • Actionable insight
    • Data discovery
    • Data engineering
    • Data hygiene
    • Privacy review
  • Products
    • InsightHub
    • Apteco
    • Microsoft
    • Data management
    • Consent and preference management
  • Our insights
    • Blog
    • Case studies
    • Reports
    • Webinars
    • Whitepapers
  • About Wood for Trees
    • Operating principles
    • Careers
  • Contact Wood for Trees
Blog

Website migration guide: a Google Analytics & Tag Manager checklist

By Edit | 4 Jan 2016

We published this a long time ago…

Some of the content in this post might be out of date, and some images and links may no longer work.

Discover who we are and how we may be able to help you today:

Learn more

Hopping on the bandwagon started by Stephen Kenwright’s blog post on website migration for SEO. From that you know that if a site migration is done carelessly, there is the potential to lose traffic and trust. This article is about making sure you don’t lose or pollute your data along the way.

What are the risks of incorrectly migrating analytics?

Image from Optimise or Die on Slideshare

The most fundamental risk is data not being correct. If this is the case, then reports are not accurate and decisions are made based on incorrect information – and are therefore probably the wrong decisions to make. You don’t want to cause a nuclear blast because you didn’t consider migrating your Google Analytics data, now do you?

Some of the more likely things that might happen are:

  • Sessions do not record for newly launched pages
  • The number of self referrals increases
  • Conversion rates drop to zero
  • Events track incorrectly
  • Remarketing tags do not get fired
  • Content Groupings do not pull in correct data
  • Traffic is incorrectly filtered

OK, it might not lead to a nuclear winter but it’s worth not running the risk.

Google Analytics site migration checklist

Below is your checklist. Feel free to copy/paste into an Excel Doc and add two columns: “responsibility” and “done?”.

  • Ensure Google Analytics/Tag Manager code is placed on all pages of the new website
    • Include sub/cross domain tracking as required
    • Include eCommerce tracking as required
  • Review Event Tracking
    • Which old events need migrating?
    • Which events need changing?
    • Which new events need adding?
    • Keep the naming convention as consistent as can be
    • Update event triggers on site as required
    • Update event triggers and tags on Google Tag Manager as required
  • Review and update goals
    • Goal URLs may need updating
    • Goals funnels may need updating
    • Goal events may need updating
  • Disable old goals
  • Review and update filters
    • URL inclusion/exclusion filters may need updating
    • Re-write filters may not apply, or need changing
  • Review and update content groupings
    • Update any code that relates to content groupings
    • Update any URL/page title rules or extract details
    • Read my post on Content Groupings for further information
  • Review any triggers in Tag Manager
    • Triggers may relate to changed URLs, DOM elements or events
  • Check tags in Tag Manager are associated with the correct triggers
  • Review any variables in Tag Manager are updated as required
  • Review any code for custom variables

And now you’re ready to go!

And that’s pretty much it. If I’ve missed any, please message me and I’ll add it to the list.

We published this a long time ago…

Some of the content in this post might be out of date, and some images and links may no longer work.

Discover who we are and how we may be able to help you today:

Learn more

Share this

  • Email
  • WhatsApp
  • LinkedIn
  • Facebook
  • X (Twitter)

More insights

AI isn’t going to take your job (unless you really want it to) 
Blog

AI isn’t going to take your job (unless you really want it to) 

By Edit | 18 Jun 2024
Customer relationship marketing: How generative AI is revolutionising engagement  
Blog

Customer relationship marketing: How generative AI is revolutionising engagement  

By Edit | 4 Apr 2024
Personalisation as a process
Blog

Personalisation as a process

By Edit | 8 Mar 2024
  • Privacy policy
  • Cookie policy
  • Ts&Cs
  • Report a concern

© 2025 Edit, part of Salocin Group Ltd. All rights reserved. Company no.: 0362​4881. VAT no.: 4208​34911.

Salocin Group Certified B Corporation | Cyber Essentials Certified | British Assessment Bureau, ISO 27001 Information Security Management
Salocin Group
Your cookie preferences

We use cookies to ensure this website functions properly, to analyse website traffic and for marketing purposes.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}