Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup shows some areas that need attention. The Google Analytics 4 (GA4) tag is present but did not fire on your homepage, which is a concern as it means visitor data might not be recorded correctly. Additionally, there is no Google Tag Manager (GTM) container detected, and Shopify's native analytics tools like Trekkie and the Web Pixels API are not active, which could limit your ability to track customer interactions effectively. No duplicate pixel risks were found, but the lack of GA4 firing and missing consent API calls are critical issues to address. Next, it would be wise to audit your product pages, cart, checkout, and order-confirmation pages to ensure all necessary tracking is in place. Given these gaps, I recommend connecting your store to PayHelm AI for a more comprehensive analysis and support.
Tag setup present but not confirmed loading.
GA4 configured but no hits observed (may be consent-gated).
4 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-XXXX container; gtag.js present instead.
No GTM container detected. This store relies on Shopify Web Pixels and direct gtag.js — a perfectly valid architecture for Shopify. GTM may improve centralised management but is not required.
G-EG63LDSMJJ — no /g/collect hit observed.
GA4 is configured but we did not see it send data on this page — it may be gated behind cookie consent or misconfigured.
Fix this issue2 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: bys-store-3218338-340610.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 not detected
Shopify's native Trekkie analytics was not detected. This library powers Shopify's own analytics dashboard and is normally present on all standard storefronts.
Web Pixels API not observed
Shopify's Web Pixels API was not detected on this page. Pixels managed via Shopify Admin → Settings → Customer Events use this API and run in a sandboxed environment separate from GTM.
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 543ms
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 observed on this page. Set up 'view_item_list' on your collection/category/search pages for funnel visibility. 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 gapNot observed during this load — 'select_item' requires user interaction on collection/category pages. 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.
Consideration
Not observable on home pages — 'view_item' only fires on product detail pages. Audit that page type to verify coverage.
Cart Activity
Not observable on home pages — 'add_to_cart' only fires on product pages and cart. Audit that page type to verify coverage.
Not observable on home pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.
Not observable on home pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.
Checkout Funnel
Not observable on home pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.
Not observable on home pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.
Not observable on home pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.
Not observable on home 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.
Failed to load resource: the server responded with a status of 429 ()
Failed to load resource: the server responded with a status of 404 ()
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.