Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
The audit of your website's home page reveals a generally healthy tracking setup with a few areas needing attention. Your Google Tag Manager (GTM) is properly configured and functioning, and Google Analytics 4 (GA4) is successfully collecting data. However, there is a warning regarding the presence of a deprecated Universal Analytics tag, which should be removed to avoid any potential data conflicts. Additionally, there are conflicting GA4 IDs, which could lead to inaccurate data collection. Since your store is not on Shopify, there are no concerns about Shopify-native analytics or duplicate pixel risks. Next, it would be beneficial to audit other critical pages like product pages, cart, checkout, and order-confirmation to ensure comprehensive tracking across your site. Given the warnings identified, I recommend connecting your store to PayHelm AI for a more detailed analysis and guidance on resolving these issues.
GTM container installed and loading.
GA4 is installed and sending data.
Not an ecommerce store — scored on basic analytics coverage.
No data-quality issues found in tracked events.
Consent Mode present but incomplete (v2 signals missing).
Tags load quickly.
Conflicting or deprecated analytics IDs detected.
Consent Mode is set up, but the v2 signals (ad_user_data, ad_personalization) were not seen. Consent Mode v2 needs ad_user_data and ad_personalization for Google Ads remarketing and modeling to work.
Tags loaded quickly (GTM in 0.64s) — no performance concern.
No cross-domain (linker) tracking was detected. If your checkout or other steps live on a different domain, set up linker tracking so visits aren't split into separate sessions.
Google Ads Enhanced Conversions were not detected. They send hashed first-party data (email/phone) to recover conversions lost to cookie restrictions — worth enabling if you run Google Ads.
GA4 User-ID tracking was not detected. If you have logged-in users, setting a User-ID lets GA4 join their activity across devices and sessions.
Multiple GA4 measurement IDs were found (G-KJKN48V4GB, G-WW5RSQCEPF). Sending the same events to more than one GA4 property is sometimes intentional, but is often an accident that doubles event counts or splits data — confirm each ID is meant to be here.
Marketing & analytics tags observed sending data while the page loaded.
Every dataLayer push observed during page load — with full payload and configuration analysis.
›GTM lifecycle events (3)— gtm.js, gtm.dom, gtm.load, etc.
Data points present in the dataLayer that your tags can read (the values pushed alongside each event).
The actual tracking requests your browser sent — the ground-truth proof that a tag fired.
GTM-P3CFSWV
A Google Tag Manager container is installed on this page.
1/1 container(s) returned a successful gtm.js response.
The container's JavaScript downloaded successfully, so GTM can run.
Found <noscript> ns.html iframe.
The fallback for visitors with JavaScript disabled is in place.
GTM snippet appears inside <head>.
The container is loaded early, as Google recommends, so tags fire as soon as possible.
dataLayer is defined before the container snippet.
Data is available to tags from the very first event.
G-KJKN48V4GB, G-WW5RSQCEPF — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
Found UA tag.
Universal Analytics stopped processing data in 2023. These tags do nothing and should be removed.
Fix this issuedefault=false, update=false, signals=[ad_storage, analytics_storage]
Consent Mode is set up, but the v2 signals (ad_user_data, ad_personalization) were not seen. Consent Mode v2 needs ad_user_data and ad_personalization for Google Ads remarketing and modeling to work.
Fix this issueGTM 643ms, GA4 first hit 1403ms, DOMContentLoaded 1437ms
Tags loaded quickly (GTM in 0.64s) — no performance concern.
No linker configuration observed
No cross-domain (linker) tracking was detected. If your checkout or other steps live on a different domain, set up linker tracking so visits aren't split into separate sessions.
Not detected
Google Ads Enhanced Conversions were not detected. They send hashed first-party data (email/phone) to recover conversions lost to cookie restrictions — worth enabling if you run Google Ads.
Not detected
GA4 User-ID tracking was not detected. If you have logged-in users, setting a User-ID lets GA4 join their activity across devices and sessions.
G-KJKN48V4GB, G-WW5RSQCEPF
Multiple GA4 measurement IDs were found (G-KJKN48V4GB, G-WW5RSQCEPF). Sending the same events to more than one GA4 property is sometimes intentional, but is often an accident that doubles event counts or splits data — confirm each ID is meant to be here.
Fix this issueEcommerce Funnel — Not Applicable
This site doesn't appear to be an online store, so the ecommerce funnel report has been skipped. GTM tag coverage, triggers, variables, and on-page scripts are still audited above.
If this site does sell products, try re-running the audit on a product page URL — that will surface add-to-cart, checkout, and purchase event coverage.
These tracking scripts are hardcoded directly in your page HTML. Moving them into GTM makes them easier to update, pause, version, and conditionally fire — without touching your code.
GA4 gtag.js snippet installed directly in the page HTML (outside GTM).
Fix: Remove the hardcoded GA4 snippet and manage it via a GTM 'Google Analytics: GA4 Configuration' tag.
Risk: Running GA4 both directly and via GTM sends duplicate pageviews and inflates every metric in your reports.
Microsoft Clarity snippet hardcoded in the page HTML.
Fix: Use the GTM Microsoft Clarity template or a Custom HTML tag.
Risk: Centralising in GTM enables conditional firing and updates without a code deploy.
Your tracking has gaps — PayHelm can fix this.
Broken tags mean lost attribution and bad decisions. PayHelm unifies your ecommerce, ad, and analytics data so every number is trustworthy — no guesswork.