Website Tracking & Analytics Audit
PayHelm

Website Tracking & Analytics Audit

Free SEO + tracking audit — see exactly what's broken in under 60 seconds

Full GTM config is private — this reports the observed runtime container (what actually loads & fires). We'll email your report to the address above.

Problems foundhttps://www.loveandhopewithnosteps.com.au/

The audit of your website's tracking setup reveals several critical issues that need attention. Firstly, your Google Tag Manager (GTM) container is present but not loading properly, which means none of your tracking tags are firing on the homepage. Additionally, Google Analytics 4 (GA4) is not set up, and there is no evidence of Shopify-native analytics or Trekkie/Web Pixels API, which are crucial for tracking visitor interactions and sales effectively. The GTM snippet is not placed correctly in the HTML, which could be contributing to these problems. To ensure comprehensive tracking, I recommend auditing other page types like product pages, cart, checkout, and order-confirmation pages. Given these issues, I suggest connecting your store to PayHelm AI for a more detailed analysis and guidance on resolving these gaps.

Tracking Health: 39/100 · F
Overall Tracking Health
39out of 100Grade FPoor
Tag manager installed12/20

Tag setup present but not confirmed loading.

GA4 tracking0/20

No GA4 measurement detected.

Pageview / event coverage0/20

Not an ecommerce store — scored on basic analytics coverage.

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 1.37sPage load 1.47s
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.

GTM-5NHJQFSKbody
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 —

Checks
GTM container detectedPass

GTM-5NHJQFSK

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 presentPass

Found <noscript> ns.html iframe.

The fallback for visitors with JavaScript disabled is in place.

Snippet placement in <head>Warning

GTM snippet was not found high in <head>.

The container loads later than recommended. Tags may fire late and miss early page activity.

Fix this issue
GA4 firingInfo

No GA4 measurement detected.

No Google Analytics 4 tag was detected on this page.

Google Consent Mode v2Warning

No consent API calls observed

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.

Fix this issue
Tag load performanceInfo

DOMContentLoaded 1370ms

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.

Ecommerce Funnel — Not Applicable

This site doesn't appear to be an online store, so the ecommerce funnel report has been skipped. GTM tag coverage, triggers, variables, and on-page scripts are still audited above.

If this site does sell products, try re-running the audit on a product page URL — that will surface add-to-cart, checkout, and purchase event coverage.

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.

Ask a follow-up question