What to do next
We’ve explained these in more detail below but if you need a quick action plan, use these.
Google is ramping up the warnings and there’s only just over a month to go until Universal Analytics is sunset in July 2023.
If you have logged into you Universal Analytics account recently, you were probably greeted with this alarming display.
At the start of May, Google has ramped up the GA4 migration urgency with a few visual indicators on legacy Universal Analytics properties to alert users to the impending July 2023 switchover. Yes, it’s a very off-putting and scary flipping banner.
For our clients, we have taken the following steps so far:
So we have a GA4 account, installed on site, receiving useful data. Perfect!
Not perfect. Throughout April, we saw this warning:
And now, in May, we have a full set of angry messages everywhere we click.
What on earth is going on? Haven’t we already setup GA4?
Google knows not every client is technical and migrating from one analytics platform to another can be a daunting task for anyone (even the digital marketing veterans).
Google communicated to every Google Analytics user in February 2023 about ‘Jumpstart’, the automatic, forced migration from UA to GA4. ‘We’ll soon configure Google Analytics 4 for you’.
Although Google strongly advises manual migration (i.e. the steps outlined at the start of this article), auto-migration remains the default behaviour unless you opt out. Google will ‘Jumpstart’ GA4 using the UA gtag.js or analytics.js tag installed on your site or GTM for every tracking property in your account, even if you have created an equivalent GA4 property. This could lead to multiple, poorly-configured GA4 trackers on your site collecting bloated, rubbish data.
Not all ‘Jumpstarts’ are created equal:
Google Analytics 4 is replacing Universal Analytics. On July 1, 2023, your Universal Analytics properties will stop collecting data. Only GA4 properties will collect data after July 1. To help you with this transition, beginning in March 2023,
So, from March 2023, Google has been rolling out automatically configured GA4 properties to all UA users.
For users with no GA4 linked to their UA, these GA4 properties have been created automatically and configured to mirror UA settings as well as the automated migration will allow.
For users who have created a GA4 and linked it to their UA, Google will still be copying over measurement configurations for UA even if they don’t fit the GA4 data being manually sent to the property.
… That last point has probably caught a few people off guard. It was a shock to some of our clients who had, up to this point, creating and linking a GA4 property would satiate ‘Jumpstart’ and Google would leave their data alone.
We’ve explained these in more detail below but if you need a quick action plan, use these.
Disable auto-migration in your UA admin area for every UA property you want to prevent from generating an automatic GA4 property on your site.
In either your GA4 or UA admin area, tell Google which legacy UA property is being replaced by GA4.
A more gramular checklist for GA4 measurements. You can find this in your GA4 admin area. Complete each action and mark it off to indicate to Google that the property is measuring data.
The main take away from this article: if you do not want your existing UA tag to start tracking GA4 for you (either creating a GA4 property from scratch or pushing UA data into your nice, new, clean GA4 property) then you must opt out of auto-migration.
Directly from Google:
To opt out, you need the Editor role on your Universal Analytics property.
If you have multiple UA properties (for example, multiple trackers on one site, or testing/staging properties) make sure to opt out of ‘Jumpstart’ on every single tracking property if you don’t want the auto-migration to take place.
This is important for a few reasons:
If you aren’t immediately greeted by the linking pop-up window when you open up GA4, you can find the setting in your UA property.
You can find the GA4 migration checklist in your GA4 property.
More of a checklist than an action but if you ever reach out to Google Technical Support, the first thing they’ll do is check your setup assistant progress.
These don’t complete automatically as you configure the property and marking things as done doesn’t seem to ward off the migration warnings on your account. Checking items off this list will halt the auto-migration process for that particular item.
In case anyone is reading after July 2023… Though Google did start creating properties from March 2023.
If you didn’t opt out in time and Google has created your automatically configured Google Analytics 4 property (and you don’t want it), you can disconnect and remove the property.
One of the most frustrating aspects of the GA4 movement is the drip-fed documentation from Google. We’re finally at a stage, in May 2023, where the GA4 docs feel nice and bulky but we are still discovering new features (and bugs) in GA4 even with a month to go for the hard UA sunset deadline.
In short, for mitigating risk to your analytics data during the final ‘sunset’ countdown, as long as you:
Then you’re in a good position for July 2023.
Inevitably, there will be another thing to check in a few months time. An update here, a process there. For now, completing the actions outlined in this article will keep your analytics data in the best condition, ready for Google’s next manoeuvre.