Website Tracking & Analytics Audit

my-madd-kreations.com Tracking & SEO Audit — Grade A

A saved report based on tracking and pages observed during this scan.

Works, with issueshttps://my-madd-kreations.com/

Read the full audit summary

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.

AI discovery review not included

What to look at first

Priorities below are taken directly from findings in this report.

SEO Review

100out of 100Grade AExcellent

SEO fundamentals look solid across all checks.

Title tagPass

Title is 47 characters — within the ideal 30–70 character range.

My Madd Kreations | Handcrafted Scented Candles (47 chars)

Meta descriptionPass

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)

H1 headingPass

One H1 heading found — the recommended structure for every page.

My Madd Kreations

Robots / indexabilityPass

No noindex directive — the page is eligible to be indexed.

No robots meta tag (defaults to index, follow).

Canonical URLPass

Canonical tag points to the page itself — no duplicate-content signals sent to search engines.

https://my-madd-kreations.com/

Open Graph tagsPass

All core Open Graph tags found — links display richly when shared on social media.

og:title ✓ og:description ✓ og:image ✓

Structured data (Schema.org)Pass

Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).

JSON-LD script found

Mobile viewportPass

Viewport meta tag found — the page is set up for mobile-friendly rendering.

viewport meta tag present

AI discovery review was not included with this saved report.

Shopify Store Detectedjsciqg-j7.myshopify.com

Trekkie / Native Analytics

Firing (monorail beacon observed)

Web Pixels API

Active (Customer Events sandbox)

Shopify Analytics

Present

On Shopify, pixels can fire from three independent sources: GTM tags, hardcoded theme code, and Shopify Customer Events. Duplicate fires inflate conversion counts and corrupt ROAS — see the checks below for details.

GTM-WWRD37Z2head

Loaded

Tags(1)

Marketing & analytics tags observed sending data while the page loaded.

Shopify Analytics (Trekkie)Analytics

5 hits

Triggers(5)

Every dataLayer push observed during page load — with full payload and configuration analysis.

›GTM lifecycle events (3)— gtm.js, gtm.dom, gtm.load, etc.

Variables(9)

Data points present in the dataLayer that your tags can read (the values pushed alongside each event).

gtm.starteventgtm.uniqueEventIdtimestampstatusconsentmoStatuscategoriescmdtarget

Network hits(6)

The actual tracking requests your browser sent — the ground-truth proof that a tag fired.

200gtm.jshttps://www.googletagmanager.com/gtm.js?id=GTM-WWRD37Z2

200analyticshttps://monorail-edge.shopifysvc.com/v1/produce

GTM-WWRD3Z2head

Not loaded

Tags(1)

Marketing & analytics tags observed sending data while the page loaded.

Shopify Analytics (Trekkie)Analytics

5 hits

Triggers(5)

Every dataLayer push observed during page load — with full payload and configuration analysis.

›GTM lifecycle events (3)— gtm.js, gtm.dom, gtm.load, etc.

Variables(9)

Data points present in the dataLayer that your tags can read (the values pushed alongside each event).

gtm.starteventgtm.uniqueEventIdtimestampstatusconsentmoStatuscategoriescmdtarget

Network hits(6)

The actual tracking requests your browser sent — the ground-truth proof that a tag fired.

200gtm.jshttps://www.googletagmanager.com/gtm.js?id=GTM-WWRD37Z2

200analyticshttps://monorail-edge.shopifysvc.com/v1/produce

JavaScript errors (2)

Multiple import maps are not yet supported. https://crbug.com/927119

Overall Tracking Health

90out of 100Grade AExcellent

Tag manager installed20/20

GTM container installed and loading.

GA4 tracking10/20

GA4 configured but no hits observed (may be consent-gated).

Ecommerce funnel coverage20/20

4 of 4 key funnel stages look healthy.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode10/10

Consent Mode v2 configured.

Performance10/10

Tags load quickly.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Pass

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.

default: yesupdate: yes✓ ad_storage✓ analytics_storage✓ ad_user_data✓ ad_personalization✓ functionality_storage✓ personalization_storage✓ security_storageCMP: Shopify Customer Privacy

Tag PerformancePass

Tags loaded quickly (GTM in 1.39s) — no performance concern.

GTM 1.39sDOM ready 2.65sPage load 4.30s

Cross-domain TrackingInfo

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.

Enhanced ConversionsInfo

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.

User-ID TrackingInfo

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.

Checkout & Purchase CoverageWarning

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.

Checks

GTM container detectedPass

GTM-WWRD37Z2, GTM-WWRD3Z2

A Google Tag Manager container is installed on this page.

Container script loads (gtm.js)Warning

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 issue

Noscript fallback presentPass

Found <noscript> ns.html iframe.

The fallback for visitors with JavaScript disabled is in place.

Snippet placement in <head>Pass

GTM snippet appears inside <head>.

The container is loaded early, as Google recommends, so tags fire as soon as possible.

dataLayer initialised before GTMWarning

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 issue

GA4 firingWarning

G-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 issue

JavaScript errors during loadInfo

2 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.

Shopify platform detectedPass

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.

Shopify native analytics (Trekkie)Pass

Trekkie beacon fired (monorail)

Shopify's built-in Trekkie analytics library is active and sending data to Shopify's own reporting.

Shopify Web Pixels API (Customer Events)Pass

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.

Shopify platform detectedInfo

cdn.shopify.com / window.Shopify

This site runs on Shopify. Tracking setup and common pitfalls differ by platform, which is factored into this audit.

Google Consent Mode v2Pass

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.

Tag load performancePass

GTM 1393ms, DOMContentLoaded 2654ms

Tags loaded quickly (GTM in 1.39s) — no performance concern.

Cross-domain trackingInfo

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.

Enhanced Conversions (Google Ads)Info

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.

User-ID tracking (GA4)Info

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.

Checkout / purchase coverageWarning

purchase observed=false, checkout page audited=false

Fix this issue

Marketing Funnel Coverage

0 observed· 11 not auditable on this page

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

Product List / Collection Viewhigh

view_item_listMeta: ViewContentfound in JS ✓

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.

Product Click from Listmedium

select_item

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

Product Detail Page Viewcritical

view_itemMeta: ViewContentfound in JS ✓

Not observable on home pages — 'view_item' only fires on product detail pages. Audit that page type to verify coverage.

Cart Activity

Add to Cartcritical

add_to_cartMeta: AddToCartfound in JS ✓

Not observable on home pages — 'add_to_cart' only fires on product pages and cart. Audit that page type to verify coverage.

Remove from Cartmedium

remove_from_cartfound in JS ✓

Not observable on home pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.

Cart / Bag Page Viewhigh

view_cartfound in JS ✓

Not observable on home pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.

Checkout Funnel

Begin Checkoutcritical

begin_checkoutMeta: InitiateCheckoutfound in JS ✓

Not observable on home pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.

Shipping Info Enteredhigh

add_shipping_infofound in JS ✓

Not observable on home pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.

Payment Info Enteredhigh

add_payment_infoMeta: AddPaymentInfofound in JS ✓

Not observable on home pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.

Purchase / Order Confirmationcritical

purchaseMeta: Purchasefound in JS ✓

Not observable on home pages — 'purchase' only fires on order confirmation / thank-you page. Audit that page type to verify coverage.

Post-Purchase

Refund / Order Cancellationlow

refund

This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.

Multi-page Coverage — 2 additional pages checked

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.

Product/products/almond-macaron-scented-candle-set

GTM: GTM-WWRD37Z2GA4: not firingShopify Analytics (Trekkie)

gtm.domconsent_statusgtm.load

Collection/collections/all

GTM: GTM-WWRD37Z2GA4: not firingShopify Analytics (Trekkie)

gtm.domconsent_statusgtm.load

Report ID: 52bea03381

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.

Fix this issue Try PayHelm free

Ask a follow-up question