Universal Analytics: why it is dead and safe to remove

If Tag Explorer has put a red badge on a card starting with UA-, this article is what that badge points at. Universal Analytics was the previous generation of Google Analytics, and unlike most things in a scan result it is not a judgement call. It stopped collecting data years ago. Paste your page into Tag Explorer to see this tag on your own site.

The tag is still on your page. It still loads a script, still costs a request on every page view, and records nothing whatsoever. There is no configuration that revives it and no report that still reads from it. The whole of this guide is therefore a removal guide: what it was, how to recognise it, how to take it out, and what you lose by doing so.

What it actually did

Universal Analytics measured your site in hits: a page view hit when someone opened a page, an event hit when they clicked something you had wired up, and a set of session rules layered on top to group those hits into visits. Reports were built around pages, sessions and bounce rate.

That model is the reason it was replaced rather than upgraded. Google Analytics 4 records everything as an event instead, with parameters attached, which is a different enough shape that the two could not report on the same data. There was no in-place migration and no merged history. GA4 started from zero on the day you installed it.

If your GA4 property has a suspiciously recent start date, this is usually why.

What the ID means

A Universal Analytics tracking ID looks like UA-1234567-1: the letters UA, a hyphen, your Analytics account number, another hyphen, then the property index inside that account.

So UA-1234567-1 and UA-1234567-2 are two properties belonging to the same account, often a main site and a second site, or a site and a test property nobody decommissioned. The account number is the part that identifies the business. The suffix identifies which of its properties the tag was reporting to.

You may still see the ID printed in a theme options field or a plugin settings screen, which makes it look current. It is not. The ID format is the giveaway: anything beginning UA- is dead by definition. Compare it with the live formats:

• G-XXXXXXXXXX is a GA4 data stream, which is current.
• GT-XXXXXXX is a Google tag destination, which is current.
• GTM-XXXXXXX is a Tag Manager container, which is not analytics at all.
• UA-XXXXXXX-N is Universal Analytics, which is dead.

The dates, precisely

Standard Universal Analytics properties stopped processing new data on 1 July 2023. Analytics 360 properties, the paid enterprise tier, ran a year longer and stopped on 1 July 2024. After each cut-off Google removed the reporting interfaces and the APIs, and the historical data went with them. Google’s own shutdown notice is the source of record for both dates.

That last part is the one worth repeating to anyone hoping to compare this year against the old numbers. There was an export window, it closed, and if nobody used it the history is not recoverable from Google.

Why it is still on so many sites

A dead tag survives because nothing visibly breaks when it stops working. Reports simply go quiet, and by the time anyone notices, GA4 has been installed somewhere else and the old snippet has been forgotten.

It usually hides in one of a small number of places:

• A hard-coded snippet in the site template or a theme header file.
• A Google Analytics ID field in a theme options panel or a plugin settings screen.
• A Universal Analytics tag inside Google Tag Manager whose trigger nobody disabled.
• A Custom HTML tag containing the old analytics.js snippet, often pasted in years ago to add one specific measurement.

What this looks like in Tag Explorer

Tag Explorer draws your page as a tree. Each Tag Manager container is a branch, the tags inside it are leaves underneath it, and anything hard coded into the page HTML sits under DIRECT ON PAGE.

Universal Analytics appears as an Analytics card with the UA- tracking ID as the card title and the tag type as the subtitle. Because the tool treats it as confidently dead, the card gets the red attention treatment and carries a removal note, the same styling used for a genuine duplicate. The insights panel below the tree raises it again as an advisory, so you will see it twice on purpose.

The info icon on the card opens the short definition and the Learn more link that brought you here.

Two limits of the scan are worth knowing while you go looking for the tag. The public container file never contains the human names you gave your tags, only the tag type and the tracking ID, so the tool cannot tell you the tag is called something like “UA legacy, do not delete”. And it reads the published container only, so if somebody has already deleted the tag in a Tag Manager workspace but never published that change, the scan will still find it live on the page. That is correct behaviour: the page really is still loading it.

Where the tag sits in the tree tells you who has to remove it, which is the practical question.

What to do when you find one

The answer is always remove it. There is no version of this where keeping it helps. What changes is only the method, which depends on where the scan found it.

If it sits under a Tag Manager container. Open the container, find the Universal Analytics tag, delete the tag and its trigger, and publish a new version. Publishing is the step that matters: an unpublished deletion changes nothing on the live site. Also delete any Google Analytics Settings variable holding the UA- ID, otherwise it lingers as an unused variable that confuses the next person.

If it sits under DIRECT ON PAGE. It is hard coded, so it comes out of the site itself. Check the theme options panel first, since a settings field is a two-second fix and needs no developer. If it is a snippet in a template file, that is a small developer task: remove the block, deploy, then rescan to confirm.

If it is inside a plugin or a page builder field. Clear the field rather than deleting the plugin, unless the plugin exists only to inject that one tag.

What you lose by removing it. Nothing you still have. No report, no audience, no conversion, no historical data, because none of that exists any more. What you gain is one fewer script on every page load, a container that matches reality, and a scan result you can actually read.

Before you remove it, confirm GA4 is there. Run the scan again and look for a G-XXXXXXXXXX card. If Universal Analytics is the only analytics tag on the site, you are currently measuring nothing at all, and installing GA4 is the urgent job. Removing the dead tag is the tidy-up that follows.

Related guides

• Google Analytics 4 explained: the G- measurement ID
• The Google tag (gtag.js) explained
• GTM containers explained
• Custom HTML tags explained
• Google Ads conversion tracking explained

If you are not sure whether the UA- card on your scan is the only analytics you have, run the page through Tag Explorer again and read the card titles: one dead ID and no live one is a very different situation from a harmless leftover. Inherited setups full of tags nobody can explain are exactly what our rebuilds and rescues work is for, and clearing the dead ones is usually the first hour of it.