Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website currently does not have Google Tag Manager (GTM) installed, which means you're missing out on a centralized way to manage your tracking tags. The most critical gap in your ecommerce funnel is the absence of key actions like "add to cart" and "purchase" tracking, which means you cannot effectively run cart-abandonment campaigns or accurately measure your return on ad spend (ROAS). For your Shopify store, both Trekkie/native analytics and the Web Pixels API are functioning well, and there is no risk of duplicate pixels. There are no on-page scripts that need to be moved into GTM. To improve your tracking setup, consider installing GTM to manage your tags more efficiently and ensure all critical ecommerce actions are tracked. I recommend connecting your store to PayHelm AI, which will automatically monitor your tag health, funnel coverage, attribution, and data-layer accuracy across every page.
No GTM-XXXX container; gtag.js present instead.
Tags are loaded directly via gtag.js rather than through Tag Manager. That works, but you lose GTM's central management.
Fix this issueGA4 — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
9 error(s) logged.
JavaScript errors fired while the page loaded. They don't always break tags, but they can prevent some from firing.
Fix this issueShop: 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. Set up 'view_item_list' on your collection/category/search pages for funnel visibility.
Fix this gapNot observed. Add 'select_item' on your collection/category pages for complete coverage.
Consideration
No ecommerce tracking detected. Add a 'view_item' dataLayer push on your product detail pages. Critical gap — without it you can't measure ROAS or attribute conversions.
Fix this gapCart Activity
No ecommerce tracking detected. Add a 'add_to_cart' dataLayer push on your product pages and cart. Critical gap — without it you can't measure ROAS or attribute conversions.
Fix this gapNot observed. Add 'remove_from_cart' on your cart page for complete coverage.
Not observed. Set up 'view_cart' on your cart page for funnel visibility.
Fix this gapCheckout Funnel
No ecommerce tracking detected. Add a 'begin_checkout' dataLayer push on your checkout entry page. Critical gap — without it you can't measure ROAS or attribute conversions.
Fix this gapNot observed. Set up 'add_shipping_info' on your checkout shipping step for funnel visibility.
Fix this gapNot observed. Set up 'add_payment_info' on your checkout payment step for funnel visibility.
Fix this gapNo ecommerce tracking detected. Add a 'purchase' dataLayer push on your order confirmation / thank-you page. Critical gap — without it you can't measure ROAS or attribute conversions.
Fix this gapPost-Purchase
Not observed. Add 'refund' on your server-side or order management system for complete coverage.
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 ()
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.