Website Tracking & Analytics Audit

fitnesstrainer.nyc Tracking & SEO Audit — Grade B

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

Works, with issueshttps://fitnesstrainer.nyc/

Read the full audit summary

Your website's tracking setup shows some areas that need attention. Currently, Google Analytics 4 (GA4) is set up and firing correctly, but there are two different GA4 IDs present, which could lead to data discrepancies. There's no Google Tag Manager (GTM) container detected, which means you're using gtag.js directly instead. This isn't necessarily a problem, but it limits flexibility for future tracking enhancements. Additionally, there are no Shopify-native analytics or Trekkie/Web Pixels API detected, which is expected since your site isn't on Shopify. On the homepage, the Meta Pixel and one of the GA4 tags fired as expected, but there's a gap in tracking 'view_item_list' events, which should ideally be captured on this page type. There was also a console error indicating a failed resource load, which could affect site performance or tracking accuracy. Given these findings, it would be wise to audit other key pages like product, cart, and checkout pages next to ensure comprehensive tracking. Since there are some real issues identified, I recommend connecting your store to PayHelm AI for a more detailed analysis and guidance on resolving these gaps.

SEO review not includedAI discovery review not included

What to look at first

Priorities below are taken directly from findings in this report.

Overall Tracking Health

87out of 100Grade BGood

Tag manager installed12/20

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

Consent Mode v2 configured.

Performance10/10

Tags load quickly.

No conflicts0/5

Conflicting or deprecated analytics IDs detected.

Advanced Tracking Features

Consent Mode v2Pass

Consent Mode v2 is configured. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.

default: yesupdate: yes✓ ad_storage✓ ad_user_data✓ ad_personalization✓ analytics_storage✓ wait_for_update

Tag PerformancePass

Tags loaded quickly — no performance concern.

GA4 first hit 1.65sDOM ready 0.72sPage load 2.72s

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.

Conflicting GA4 IDsWarning

Multiple GA4 measurement IDs were found (G-M7VP7KY6JS, G-BF2FDR6KMM). Sending the same events to more than one GA4 property is sometimes intentional, but is often an accident that doubles event counts or splits data — confirm each ID is meant to be here.

G-M7VP7KY6JSG-BF2FDR6KMM

Checks

GTM containerWarning

No GTM-XXXX container; gtag.js present instead.

Tags are loaded directly via gtag.js rather than through Tag Manager. That works, but you lose GTM's centralised management, versioning, and conditional firing controls.

Fix this issue

GA4 firingPass

G-M7VP7KY6JS, G-BF2FDR6KMM — collect hit observed.

Google Analytics 4 is actively sending pageview/event data.

JavaScript errors during loadInfo

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

Google Consent Mode v2Pass

default=true, update=true, signals=[ad_storage, ad_user_data, ad_personalization, analytics_storage, wait_for_update]

Consent Mode v2 is configured. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.

Tag load performancePass

GA4 first hit 1651ms, DOMContentLoaded 721ms

Tags loaded quickly — 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.

Conflicting GA4 IDsWarning

G-M7VP7KY6JS, G-BF2FDR6KMM

Fix this issue

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

On-page Scripts — Should Be in GTM (2)

These tracking scripts are hardcoded directly in your page HTML. Moving them into GTM makes them easier to update, pause, version, and conditionally fire — without touching your code.

Meta (Facebook) Pixel

Meta Pixel script (fbevents.js) found hardcoded directly in the page HTML.

Fix: Remove the hardcoded snippet and use a GTM 'Facebook Pixel' or 'Custom HTML' tag instead.

Risk: If GTM also fires Meta Pixel, you'll double-count conversions and inflate ROAS. Centralising in GTM also lets you pause, version, and conditionally fire without a code deploy.

Google Analytics 4 (direct gtag.js)

GA4 gtag.js snippet installed directly in the page HTML (outside GTM).

Fix: Remove the hardcoded GA4 snippet and manage it via a GTM 'Google Analytics: GA4 Configuration' tag.

Risk: Running GA4 both directly and via GTM sends duplicate pageviews and inflates every metric in your reports.

Report ID: 75faeb2957

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