Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
The audit of your website's tracking setup revealed several critical issues that need attention. Firstly, there is no Google Tag Manager (GTM) container found, which is essential for managing your tracking tags efficiently. Additionally, your site is still using Universal Analytics, which is outdated and should be replaced with GA4 for better data insights. The Google Consent Mode is also not implemented, which can affect compliance with privacy regulations. On this specific page, only the Google Ads tag fired, and there were no Shopify-native analytics detected, which could lead to incomplete data collection. For a Shopify store, the absence of Trekkie and the Web Pixels API means you might be missing out on important tracking capabilities, and there's no risk of duplicate pixels since none were detected. Next, you should focus on auditing product pages, cart, checkout, and order-confirmation pages to ensure all critical events are firing correctly. Given the issues found, I recommend connecting your store to PayHelm AI for a comprehensive analytics solution.
No GTM container or gtag.js detected.
No GA4 measurement detected.
1 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag load timing not measured.
Conflicting or deprecated analytics IDs detected.
No Google Consent Mode was detected. Since March 2024 Google requires Consent Mode v2 for sites with EEA/UK traffic running Google Ads — without it, conversion and remarketing data is lost for users who haven't consented.
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
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.
Neither checkout nor purchase tracking was observed. These are the events that matter most for revenue reporting — confirm begin_checkout and purchase fire end-to-end.
No GTM container found.
No Google Tag Manager container was found on this page. If you rely on GTM for analytics and ads tags, nothing will fire.
Fix this issueNo GA4 measurement detected.
No Google Analytics 4 tag was detected on this page.
Found UA-47471975-1.
Universal Analytics stopped processing data in 2023. These tags do nothing and should be removed.
Fix this issue1 error(s) logged.
JavaScript errors were logged during page load. These don't necessarily affect tracking — only errors that directly interrupt pixel execution matter. See any vendor-specific errors below for actionable issues.
No consent API calls observed
No Google Consent Mode was detected. Since March 2024 Google requires Consent Mode v2 for sites with EEA/UK traffic running Google Ads — without it, conversion and remarketing data is lost for users who haven't consented.
Fix this issueDOMContentLoaded 1265ms
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
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.
purchase observed=false, checkout page audited=true
Neither checkout nor purchase tracking was observed. These are the events that matter most for revenue reporting — confirm begin_checkout and purchase fire end-to-end.
Fix this issueFunnel events are page-specific: purchase only fires on order confirmation, add_to_cart requires a user click. Events shown as are not observable on this page type — audit each page separately for full coverage.
Discovery
Not observed on this page. Set up 'view_item_list' on your collection/category/search pages for funnel visibility.
Fix this gapNot observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page.
Consideration
No ecommerce tracking detected on this page. Add a 'view_item' dataLayer push on your product detail pages.
Fix this gapCart Activity
Not observed during this load — 'add_to_cart' requires user interaction on product pages and cart. Verify by manually testing the action on that page.
Not observed during this load — 'remove_from_cart' requires user interaction on cart page. Verify by manually testing the action on that page.
Not observed on this page. Set up 'view_cart' on your cart page for funnel visibility.
Fix this gapCheckout Funnel
No ecommerce tracking detected on this page. Add a 'begin_checkout' dataLayer push on your checkout entry page.
Fix this gapNot observed during this load — 'add_shipping_info' requires user interaction on checkout shipping step. Verify by manually testing the action on that page.
Not observed during this load — 'add_payment_info' requires user interaction on checkout payment step. Verify by manually testing the action on that page.
No ecommerce tracking detected on this page. Add a 'purchase' dataLayer push on your order confirmation / thank-you page.
Fix this gapPost-Purchase
This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.
The audit automatically visited additional page types discovered on the site to verify tags fire across the full funnel, not just on the entry page.
$(...).prettyPhoto is not a function
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.