Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup has some areas that need attention. Currently, Google Tag Manager (GTM) and Google Analytics 4 (GA4) are not set up on your product pages, which is a significant gap since these tools are essential for comprehensive tracking and analytics. However, Shopify's native analytics, including Trekkie and the Web Pixels API, are functioning correctly, which is good news as they provide some level of tracking. There are also JavaScript errors and a warning about Google Consent Mode, which might affect data collection. Next, you should audit other key pages like the cart, checkout, and order-confirmation pages to ensure tracking is consistent across your site. Given the current gaps, I recommend connecting your store to PayHelm AI for a more in-depth analysis and guidance on improving your tracking setup.
No GTM container or gtag.js detected.
No GA4 measurement detected.
3 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag load timing not measured.
No conflicting analytics IDs.
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.
We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.
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.
4 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.
Shop: tkkhqw-ra.myshopify.com
This is a Shopify store. Pixels can fire from three sources: GTM tags, hardcoded theme code, and Shopify Customer Events (Web Pixels API sandbox). All three are audited here.
Trekkie beacon fired (monorail)
Shopify's built-in Trekkie analytics library is active and sending data to Shopify's own reporting.
Web Pixels API / Shopify.analytics detected — pixels run in a sandboxed iframe
Shopify's Web Pixels API is active. Pixels installed via Shopify Admin → Settings → Customer Events run in a sandboxed iframe, independently of GTM — they cannot interfere with each other, but duplicates are still possible if the same vendor is also in GTM or theme code.
cdn.shopify.com / window.Shopify
This site runs on Shopify. Tracking setup and common pitfalls differ by platform, which is factored into this audit.
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 1508ms
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=false
We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.
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 observable on product pages — 'view_item_list' only fires on collection/category/search pages. Audit that page type to verify coverage.
Not observable on product pages — 'select_item' only fires on collection/category pages. Audit that page type to verify coverage.
Consideration
Not observed firing as a GA4 event, but Shopify's native 'product_viewed' event was found in the site's JavaScript. The Shopify Customer Events / Web Pixels handler exists but the GA4 mapping may not be set up. Verify in Shopify Admin → Settings → Customer Events. No ecommerce tracking detected on this page. Add a 'view_item' dataLayer push on your product detail pages. On Shopify, events may fire via Customer Events (Shopify Web Pixels sandbox) and may not be visible in the dataLayer — verify in Shopify Admin → Settings → Customer Events.
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. On Shopify, events may fire via Customer Events (Shopify Web Pixels sandbox) and may not be visible in the dataLayer — verify in Shopify Admin → Settings → Customer Events.
Not observable on product pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.
Not observable on product pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.
Checkout Funnel
Not observable on product pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.
Not observable on product pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.
Not observable on product pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.
Not observable on product pages — 'purchase' only fires on order confirmation / thank-you page. Audit that page type to verify coverage.
Post-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.
Multiple import maps are not yet supported. https://crbug.com/927119
Multiple import maps are not yet supported. https://crbug.com/927119
Failed to load resource: the server responded with a status of 404 ()
Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the request from completing. Error: TypeError: Failed to fetch. Schemas: shopify_pay_page_load/2.7
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.