forge-analyticslisted

Audit, install, and fix Google Analytics 4 tracking on a website so the data is actually useful for conversions. Scans the codebase for existing analytics (GA4, gtag, GTM, Plausible, Vercel Analytics), reports what is tracked vs missing in plain English, then installs or repairs a clean event layer — CTA clicks, form starts/submits, phone/WhatsApp/email/booking clicks, nav usage, section views, scroll depth, outbound links — with consistent event names, useful parameters, key-event marking, route-change support, no duplicates, no PII, and production-only gating. Optionally pulls live GA4 data to verify events are firing and grade real conversion data. Use when the user says "set up analytics", "install GA4", "add my Google tag", "audit my analytics", "is my tracking working", "am I tracking the right things", "fix my events", "track conversions", "G-XXXXXXXXXX", "check my analytics setup", or hands over a site and asks whether the analytics are any good.
RamzanReshi/forge-analytics · ★ 0 · Data & Documents · score 72

Install: claude install-skill RamzanReshi/forge-analytics

# Forge Analytics Make a site's analytics functional and logical: correct install, meaningful events, good parameters, real conversion insight. Three modes. Pick based on what the user asked; when unclear, run **Audit** first — it is read-only and tells you what the other modes need to do. | Mode | Trigger | Output | |---|---|---| | **Audit** | "check/audit my analytics", "is tracking working", no tag given | Plain-English report card. No code changes. | | **Install** | "set up GA4", "add this tag", tag ID given, or audit found gaps | Analytics helper + wired events + docs | | **Verify** | "are events firing", GA4 credentials available | Live data check + conversion grading | Always finish with the **plain-English summary** (see `references/reporting.md`). That is the deliverable the user actually reads. --- ## Mode 1: Audit (read-only) Run the scanner, then interpret. Never skip straight to conclusions — read the actual files. ```bash python3 scripts/audit_analytics.py --root . --out /tmp/forge-analytics-audit.json ``` The scanner detects: measurement IDs, gtag/GTM snippets, existing helper modules, event call sites, route-change handling, env gating, consent tooling, and competing analytics vendors. It flags but does not fix. Then read the flagged files yourself and judge quality against `references/event-taxonomy.md`: 1. **Install correctness** — one tag, loaded once, not duplicated across index.html *and* a component. `send_page_view` handling matches whether r