Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup is mostly healthy, with Google Tag Manager (GTM) and Google Analytics 4 (GA4) successfully firing on your homepage. The Google Ads tag also fired correctly, indicating that your basic tracking infrastructure is functioning as expected. However, there are a couple of areas that need attention: Google Consent Mode is not fully optimized, and the tag load performance is slower than ideal, which could affect data accuracy and user experience. Since your store is not on Shopify, there are no concerns about Trekkie or Web Pixels API. For a more comprehensive audit, I recommend checking the tracking on your product pages, cart, checkout, and order-confirmation pages to ensure all relevant events are captured accurately. If you want to address the current issues and optimize your tracking setup, consider connecting your store to PayHelm AI for expert guidance.
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).
Tag loading is slower than ideal.
No conflicting analytics IDs.
Consent Mode is set up, but the v2 signals (ad_personalization) were not seen. Consent Mode v2 needs ad_user_data and ad_personalization for Google Ads remarketing and modeling to work.
Google Tag Manager loaded in 1.7s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.
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.
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 (4)— 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-5S93CNDG
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-F6JCDWSQB5 — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
default=false, update=false, signals=[ad_storage, ad_user_data]
Consent Mode is set up, but the v2 signals (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 1696ms, GA4 first hit 1222ms, DOMContentLoaded 2884ms
Google Tag Manager loaded in 1.7s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.
Fix this issueNo 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.
Ecommerce 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.
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.