Analytics script or SDK is present and loaded
Why it matters
Without an analytics SDK wired up, you cannot answer basic product questions: which acquisition channels convert, which pages drive signups, which features get used. You are shipping to production blind. Marketing spend gets allocated on gut feel, pricing experiments cannot be measured, and conversion regressions go undetected until revenue drops. Installing a package without wiring a measurement ID is worse than not installing it — it signals the job is done when zero data is flowing.
Severity rationale
High because zero observability blocks every downstream growth, conversion, and retention decision the product depends on.
Remediation
Pick one analytics provider and wire it end-to-end. For Vercel-hosted Next.js, the fastest path is npm install @vercel/analytics plus <Analytics /> in app/layout.tsx. For product telemetry, use PostHog with posthog-js initialized in a 'use client' provider. Store the measurement key in NEXT_PUBLIC_GA_MEASUREMENT_ID or equivalent and reference it from the initialization site.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Analytics & Tracking Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-analytics·automated