Website Tracking & Analytics Audit

katzeboutique.com Tracking & SEO Audit — Grade D

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

Problems foundhttps://www.katzeboutique.com/

Read the full audit summary

The audit of your website's homepage tracking setup indicates several issues that need attention. Firstly, your Google Tag Manager (GTM) container is present but failed to load correctly, which means none of your tracking tags could fire. Additionally, your Google Analytics 4 (GA4) setup is present but did not record any activity, suggesting a configuration issue. There are also warnings about the lack of a <noscript> fallback and the dataLayer not being initialized before GTM, which could affect data accuracy. For your Shopify store, neither Trekkie nor the Web Pixels API were detected, which means Shopify's native analytics are not functioning, and there is no risk of duplicate pixel firing. Next, you should audit a product page, cart, checkout, and order-confirmation page to ensure tracking is functioning across the entire customer journey. Given these issues, I recommend connecting your store to PayHelm AI for a more comprehensive analysis and assistance in resolving these tracking gaps.

SEO review not includedAI discovery review not included

What to look at first

Priorities below are taken directly from findings in this report.

Shopify Store Detectedkatze-boutique.myshopify.com

Trekkie / Native Analytics

Not detected

Web Pixels API

Not observed

Shopify Analytics

Not detected

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-KJNDRH5Lhead

Not loaded

Tags(0)

No tags were observed sending data. They may be gated behind cookie consent, or none are configured.

— none observed —

Triggers(0)

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

— no dataLayer events captured —

Variables(0)

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

— no dataLayer variables captured —

Network hits(0)

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

— no tracking requests observed —

JavaScript errors (2)

Failed to load resource: the server responded with a status of 429 ()

Failed to load resource: the server responded with a status of 404 ()

Overall Tracking Health

69out of 100Grade DNeeds work

Tag manager installed12/20

Tag setup present but not confirmed 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 Mode0/10

Consent Mode not detected.

Performance7/10

Tag load timing not measured.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Warning

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.

default: noupdate: no✗ ad_user_data✗ ad_personalization

Tag PerformanceInfo

No tag load timing was captured (the container may not have loaded, or timing was unavailable).

DOM ready 0.13sPage load 0.13s

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-KJNDRH5L

A Google Tag Manager container is installed on this page.

Container script loads (gtm.js)Fail

0/1 container(s) returned a successful gtm.js response.

The container script did not load (blocked, unpublished, or wrong ID), so no tags will fire.

Fix this issue

Noscript fallback presentWarning

No <noscript> fallback found in the HTML source.

The recommended <noscript> fallback is missing. It's minor, but Google's standard install includes it.

Fix this issue

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-E1LH2768R2 — 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: katze-boutique.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)Info

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.

Shopify Web Pixels API (Customer Events)Info

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.

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 v2Warning

No consent API calls observed

Fix this issue

Tag load performanceInfo

DOMContentLoaded 130ms

No tag load timing was captured (the container may not have loaded, or timing was unavailable).

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

1 gap to verify0 observed· 10 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: ViewContent

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 gap

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: ViewContent

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: AddToCart

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_cart

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_cart

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: InitiateCheckout

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_info

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: AddPaymentInfo

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: Purchase

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.

Report ID: 215a35e3a8

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