Website Tracking & Analytics Audit

alexfolacci.com Tracking & SEO Audit — Grade B

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

Works, with issueshttps://www.alexfolacci.com/

Read the full audit summary

Your website's tracking infrastructure is mostly in place, but there are a few areas that need attention. Google Tag Manager (GTM) and Google Analytics 4 (GA4) are set up and firing correctly on your homepage, which is a good sign. However, there are some warnings related to the GTM setup, such as the absence of a <noscript> fallback and the GTM snippet not being placed high in the <head> section of your HTML, which could affect tracking reliability. Additionally, Google Consent Mode settings need a review to ensure compliance and optimal performance. Since your site is not on Shopify, there's no need to worry about Shopify-specific tracking issues like Trekkie or Web Pixels API. For a comprehensive audit, you should next examine the product, cart, checkout, and order-confirmation pages. Given the current warnings, I recommend connecting your store to PayHelm AI for a more detailed analysis and guidance.

SEO review not includedAI discovery review not included

What to look at first

Priorities below are taken directly from findings in this report.

Wix Storeslikely

Wix Stores markup in HTML

GTM-M9BM69ZFruntime

Loaded

Tags(2)

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

Google AdsConversion / Remarketing

4 hits

Google Analytics 4GA4 Event

1 hit

Triggers(8)

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

user_iddeveloper_id.dYzMzMDsite_idgtm.starteventgtm.uniqueEventIdcmdtargetparams

Network hits(15)

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

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

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=UA-109128189-2

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=UA-221384130-1

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=AW-8627453248

beaconadshttps://ad.doubleclick.net/ccm/s/collect?auid=584504091.1784769678&gtm=45He67l1h1v9197972191za200zd9197972191xea

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=AW-11378795146&cx=c&gtm=4e67l1h1

200ga-otherhttps://www.google-analytics.com/analytics.js

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=UA-221384130-1&cx=c&gtm=4e67l1h1

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=AW-8627453248&cx=c&gtm=4e67l1h1

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=G-T7H0NRHXNM&cx=c&gtm=4e67l1

204adshttps://stats.g.doubleclick.net/g/collect?v=2&tid=G-T7H0NRHXNM&cid=751976745.1784769679&gtm=45be67l1h1v9116649450z89197972191za20gzb9197972191zd9197972191&rcb=9

200adshttps://googleads.g.doubleclick.net/pagead/viewthroughconversion/8627453248/?random=1784769678473&cv=11&fst=1784769678473&bg=ffffff&guid=ON&async=1&en=gtag.conf

200adshttps://googleads.g.doubleclick.net/pagead/viewthroughconversion/11378795146/?random=1784769678699&cv=11&fst=1784769678699&bg=ffffff&guid=ON&async=1&en=gtag.con

beaconga4-collecthttps://analytics.google.com/g/collect?v=2&tid=G-T7H0NRHXNM&gtm=45be67l1h1v9116649450z89197972191za20gzb9197972191zd9197972191&_p=1784769677943&_gaz=1&gcs=G111&

200ga-otherhttps://www.google-analytics.com/plugins/ua/ec.js

Overall Tracking Health

89out of 100Grade BGood

Tag manager installed20/20

GTM container installed and loading.

GA4 tracking20/20

GA4 is installed and sending data.

Ecommerce funnel coverage20/20

4 of 4 key funnel stages look healthy.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode5/10

Consent Mode present but incomplete (v2 signals missing).

Performance4/10

Tag loading is slower than ideal.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Warning

The v2 consent signals were seen, but a consent update after the user chooses was not observed. Consent Mode v2 needs both a gtag('consent','default',…) call before tags load and a gtag('consent','update',…) call once the visitor responds.

default: yesupdate: no✓ ad_storage✓ ad_user_data✓ ad_personalization✓ analytics_storage✓ functionality_storage✓ personalization_storage✓ security_storage

Tag PerformanceWarning

Google Tag Manager loaded in 1.6s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.

GTM 1.62sGA4 first hit 2.20sDOM ready 0.43sPage load 1.02s

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

A Google Tag Manager container is installed on this page.

Container script loads (gtm.js)Pass

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

The container's JavaScript downloaded successfully, so GTM can run.

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

GA4 — collect hit observed.

Google Analytics 4 is actively sending pageview/event data.

Wix Stores platform detectedInfo

Wix Stores markup in HTML

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

Google Consent Mode v2Warning

default=true, update=false, signals=[ad_storage, ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage, security_storage]

Fix this issue

Tag load performanceWarning

GTM 1624ms, GA4 first hit 2201ms, DOMContentLoaded 426ms

Google Tag Manager loaded in 1.6s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.

Fix this issue

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.

Product Click from Listmedium

select_itemfound in JS ✓

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: 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_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: 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_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: 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.

Report ID: bbd172e0ea

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