Website Tracking & Analytics Audit

entryplus.in Tracking & SEO Audit — Grade B

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

Works, with issueshttps://entryplus.in/

Read the full audit summary

Your website's analytics setup has some areas that need attention. Google Analytics 4 is successfully tracking activity on your homepage, but there is no Google Tag Manager (GTM) container detected, which is a common tool for managing and deploying tags. Instead, the site uses gtag.js directly. Additionally, Google Consent Mode is not fully configured, which could impact data collection compliance. There are no Shopify-native analytics or Trekkie/Web Pixels API detected, which is expected since Shopify is not used. The Meta Pixel and Microsoft Clarity tags are firing correctly, ensuring some level of visitor tracking. Next, you should audit your product pages, cart, checkout, and order-confirmation pages to ensure all necessary events are being tracked. Given the current issues, I recommend connecting your store to PayHelm AI for more comprehensive analytics support.

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.

Pageview / event coverage20/20

Not an ecommerce store — scored on basic analytics coverage.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode5/10

Consent Mode present but incomplete (v2 signals missing).

Performance10/10

Tags load quickly.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Warning

Consent Mode is set up, but the v2 signals (ad_user_data, ad_personalization) were not seen. Consent Mode v2 needs ad_user_data and ad_personalization for Google Ads remarketing and modeling to work.

default: noupdate: no✓ ad_storage✓ analytics_storage✗ ad_user_data✗ ad_personalization

Tag PerformancePass

Tags loaded quickly — no performance concern.

GA4 first hit 3.10sDOM ready 1.68sPage load 4.10s

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.

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-ETFE11L9MN — collect hit observed.

Google Analytics 4 is actively sending pageview/event data.

Google Consent Mode v2Warning

default=false, update=false, signals=[ad_storage, analytics_storage]

Consent Mode is set up, but the v2 signals (ad_user_data, ad_personalization) were not seen. Consent Mode v2 needs ad_user_data and ad_personalization for Google Ads remarketing and modeling to work.

Fix this issue

Tag load performancePass

GA4 first hit 3095ms, DOMContentLoaded 1678ms

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.

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.

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

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.

Microsoft Clarity

Microsoft Clarity snippet hardcoded in the page HTML.

Fix: Use the GTM Microsoft Clarity template or a Custom HTML tag.

Risk: Centralising in GTM enables conditional firing and updates without a code deploy.

Report ID: 5a27ccf3a1

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