Website Tracking & Analytics Audit

payhelm.com Tracking & SEO Audit — Grade F

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

Problems foundhttps://www.payhelm.com/

Read the full audit summary

Your website's tracking setup needs attention, as the audit indicates some critical issues. The Google Tag Manager (GTM) container is detected but failed to load properly, which means no tracking events are firing on your homepage. Additionally, Google Analytics 4 (GA4) is not present, and there are no Shopify-native analytics detected, which are essential for tracking visitor interactions. The absence of the Trekkie/Web Pixels API and Shopify analytics suggests a risk of missing valuable data insights. There are no specific events expected to fire on the homepage that are missing, but the infrastructure needs to be fixed to ensure future data collection. Given these findings, I recommend auditing other key pages like product, cart, checkout, and order-confirmation pages to ensure comprehensive tracking across your site. To address these issues and enhance your store's analytics, consider connecting your store to PayHelm AI for expert guidance.

SEO review not includedAI discovery review not included

What to look at first

Priorities below are taken directly from findings in this report.

WooCommercedetected

WooCommerce markup (woocommerce / wc-* classes) in HTML

GTM-WMBP43Bhead

Not loaded

Tags(0)

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

— none observed —

Triggers(2)

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

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

Variables(6)

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

eventevent_categoryevent_labelvaluecustom_parametersgtm.start

Network hits(0)

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

— no tracking requests observed —

JavaScript errors (18)

Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Failed to load resource: net::ERR_FAILED

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

Overall Tracking Health

59out of 100Grade FPoor

Tag manager installed12/20

Tag setup present but not confirmed loading.

GA4 tracking0/20

No GA4 measurement detected.

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.69sPage load 0.70s

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

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

GTM snippet appears inside <head>.

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

dataLayer initialised before GTMPass

dataLayer is defined before the container snippet.

Data is available to tags from the very first event.

GA4 firingInfo

No GA4 measurement detected.

No Google Analytics 4 tag was detected on this page.

JavaScript errors during loadInfo

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

WooCommerce platform detectedInfo

WooCommerce markup (woocommerce / wc-* classes) in HTML

This site runs on WooCommerce. 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 694ms

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.

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.

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: 1c0818f4e4

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