Found Universal Analytics code on your store?
Universal Analytics code on your store no longer collects anything useful: Google stopped processing standard UA data on 1 July 2023. The code is usually harmless but untidy. The real question is whether Google Analytics 4 (GA4) is installed separately and working, because some stores only ever had UA.
Symptom
A tag checker reports a UA- ID, analytics.js or a Universal Analytics tag in Google Tag Manager. Or you find an old Google Analytics account with a property that stopped showing new data in mid-2023.
Possible causes
- Cause A: a leftover snippet. The theme still contains an
analytics.jssnippet withga('create', 'UA-...'), or agtag.jssnippet that configures a UA ID. - Cause B: a shared gtag snippet. One
gtag.jsblock configures both the old UA ID and the newer GA4 ID. Delete the block and you delete GA4 too. - Cause C: a live UA tag in Google Tag Manager (GTM). The container still has a Universal Analytics tag that fires, even though nothing processes the data.
- Cause D: legacy order status scripts on Shopify. Older Shopify stores often put UA purchase code in the order status page's additional scripts. Shopify's help on upgrading the Thank you and Order status pages explains that this method is replaced by customer events and pixels; the upgrade deadline for non-Plus stores was 26 August 2026.
- Cause E: UA only. The store never moved to GA4, so the UA code is the only analytics on the site and nothing is being measured.
How to check
- Search the theme. Look for
UA-,analytics.js,ga('create'andgtag('config'. Note whether a GA4G-ID sits in the same block. - Check GTM. Open the live container version and look for tags of type Universal Analytics, and for variables holding a
UA-ID. Note whether each tag is paused or active. - Check Shopify order status scripts. In Settings, Checkout, look for any remaining additional scripts, and check whether your Thank you and Order status pages have been upgraded. Then look in Settings, Customer events for the pixels that now handle checkout.
- Watch the network. In DevTools, Network, filter on
collect. UA requests use/collectwithv=1and atid=UA-...; GA4 requests use/g/collectwithv=2andtid=G-.... - Confirm GA4 exists separately. Find a GA4 request with your own
G-ID, and check that it arrives in GA4 Realtime. If there is no GA4 request, you are dealing with cause E.
Illustrative example of cause B, with invented IDs:
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-1234567-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-1234567-1');
gtag('config', 'G-AB12CD34EF');
</script>
Here the right fix is to remove only the UA config line and point the loader at the GA4 ID, not to delete the whole block.
What the result means
- UA code plus a working GA4 setup: clean-up only. Low risk, low urgency, worth doing so the setup is understandable.
- UA and GA4 in the same snippet: clean up carefully, as shown above.
- Live UA tag in GTM: it sends requests nobody processes. Pause it.
- UA only, no GA4 request: the store has no working analytics. This is the urgent case.
False positive. A UA ID can sit in a settings variable or a comment with no tag that uses it. A text search finds it, but nothing is sent. Our public check counts UA only when a loader or a live UA tag is present, after we found exactly this case while building it. Paused GTM tags don't count either.
Our public research. On 14 November 2026, 46 of the 975 Shopify stores we checked still had a Universal Analytics setup detected. That shows migration hygiene, not lost sales: a public-page check can't confirm whether purchase tracking works.
How to fix it
- Make sure GA4 is installed and receiving data before removing anything.
- Remove UA snippets from the theme, keeping any GA4 config they share.
- Pause UA tags in GTM, publish, and delete them later once nothing has broken.
- On Shopify, move any purchase tracking still in legacy order status scripts to the current customer events approach. See Shopify GTM and checkout coverage.
- Update your cookie notice and privacy information so they no longer list a tool you don't use.
What not to do
- Don't delete a whole
gtag.jsblock because it contains a UA ID. Check for GA4 inside it first. - Don't expect old UA data to be available in GA4. They were separate products with separate data.
- Don't treat removing UA as a fix for missing GA4 data. If GA4 isn't receiving data, see GA4 not tracking.
When to request help
If UA and GA4 are tangled together, or you aren't sure GA4 is collecting purchases, a GA4 and GTM audit separates the legacy code from what is live and documents a safe clean-up.
Related guides:
- GA4 not tracking? Start with these checks.
- Multiple GA4 IDs on one store
- Shopify GTM is in the theme. Is checkout covered?
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.
Sources and updated date
- Google Analytics Help: Google Analytics 4 has replaced Universal Analytics
- Google Analytics Help: Send events to both your UA and GA4 properties (legacy)
- Shopify Help Center: Upgrading the Thank you and Order status pages
- Google Tag Manager Help: Google Tag Manager vs. gtag.js
Last checked against official documentation: 18 November 2026.