Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
No GTM container, but gtag.js is present (tags managed directly, not via Tag Manager). GA4 is installed and sending data. 9 JavaScript error(s) were logged during load.
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.
GA4 — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
9 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: middleton-farms.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.
Funnel 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.
Access to fetch at 'https://wt.omnisendlink.com/REST/inShop/v1/getSettings?shopHostname=middletonfarms.com&shopType=shopify&shopID=55341613263&responseType=json' from origin 'https://middletonfarms.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the reques
Failed to load resource: net::ERR_FAILED
Failed to fetch
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 404 ()
is
Failed to load resource: the server responded with a status of 404 ()
is
Failed to load resource: the server responded with a status of 404 ()
Want all your channels' data in one place?
PayHelm unifies your ecommerce, ad, and analytics data so you can trust your numbers — no broken tags, no guesswork.