Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
The audit of your website's home page reveals a few areas that need attention. Your Google Tag Manager (GTM) setup has two containers, but only one is loading correctly, which could affect tracking accuracy. While your Shopify-native analytics, including Trekkie and the Web Pixels API, are functioning well, your Google Analytics 4 (GA4) did not fire as expected, indicating a potential gap in data collection. There are no duplicate pixel risks detected, which is good for maintaining data integrity. Next, you should consider auditing your product, cart, and checkout pages to ensure comprehensive tracking across your site. Given the issues with GTM and GA4, I recommend connecting your store to PayHelm AI for more detailed insights and solutions.
GTM container installed and 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 v2 configured.
Tags load quickly.
No conflicting analytics IDs.
Consent Mode v2 is configured via Shopify Customer Privacy. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
Tags loaded quickly (GTM in 1.39s) — no performance concern.
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.
SEO fundamentals look solid across all checks.
Title is 47 characters — within the ideal 30–70 character range.
My Madd Kreations | Handcrafted Scented Candles (47 chars)Meta description is 139 characters — within the ideal 70–160 character range.
Shop handcrafted, one-of-a-kind scented candles at My Madd Kreations. Premium fragrances crafted for… (139 chars)One H1 heading found — the recommended structure for every page.
My Madd KreationsNo noindex directive — the page is eligible to be indexed.
No robots meta tag (defaults to index, follow).Canonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://my-madd-kreations.com/All core Open Graph tags found — links display richly when shared on social media.
og:title ✓ og:description ✓ og:image ✓Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).
JSON-LD script foundViewport meta tag found — the page is set up for mobile-friendly rendering.
viewport meta tag presentMarketing & analytics tags observed sending data while the page loaded.
Every dataLayer push observed during page load — with full payload and configuration analysis.
›GTM lifecycle events (3)— gtm.js, gtm.dom, gtm.load, etc.
Data points present in the dataLayer that your tags can read (the values pushed alongside each event).
The actual tracking requests your browser sent — the ground-truth proof that a tag fired.
Marketing & analytics tags observed sending data while the page loaded.
Every dataLayer push observed during page load — with full payload and configuration analysis.
›GTM lifecycle events (3)— gtm.js, gtm.dom, gtm.load, etc.
Data points present in the dataLayer that your tags can read (the values pushed alongside each event).
The actual tracking requests your browser sent — the ground-truth proof that a tag fired.
GTM-WWRD37Z2, GTM-WWRD3Z2
A Google Tag Manager container is installed on this page.
1/2 container(s) returned a successful gtm.js response.
Some containers loaded but at least one did not — check the container ID is published and not blocked.
Fix this issueFound <noscript> ns.html iframe.
The fallback for visitors with JavaScript disabled is in place.
GTM snippet appears inside <head>.
The container is loaded early, as Google recommends, so tags fire as soon as possible.
dataLayer was not clearly initialised before the container snippet.
If the container loads before dataLayer is ready, early values (like ecommerce data) can be lost.
Fix this issueG-DP2HT6H6XN — 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: jsciqg-j7.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.
default=true, update=true, signals=[ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage, security_storage], CMP=Shopify Customer Privacy
Consent Mode v2 is configured via Shopify Customer Privacy. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
GTM 1393ms, DOMContentLoaded 2654ms
Tags loaded quickly (GTM in 1.39s) — no performance concern.
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 firing, but 'view_item_list' was found configured in the site's JavaScript. It may fire only when users take specific actions or visit the relevant page type. 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.
Not 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.
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
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.