First-party analytics events + Vitals dashboard v2

[truthixify]

Tier: L (5-7 days) | Type: feature

Context. Wave 7 shipped an untyped trackEvent wrapper in src/analytics.ts around window.plausible, and a Web Vitals dashboard v1 at /vitals (src/pages/Vitals.tsx) that already has a per-page filter (selectedPage, lines 39 and 220-226) sourced from src/data/vitalsData.ts. Two gaps: (a) the generic trackEvent wrapper is not typed and is not DNT-aware on its own (DNT-checking currently lives inside useVitals.ts line 60, only for Vitals emissions), so any new caller has to remember to check DNT; (b) v1 has no per-locale filter, no event conversion tiles, and no way to correlate perf to incidents. Wave 9 content decisions need this to graduate from guessing.

Scope.

• Small typed event helper src/utils/track.ts: named events with strict TS payloads; wraps the existing trackEvent from src/analytics.ts; lifts the DNT check out of useVitals.ts so it applies to every named event; no-ops when the analytics script is not loaded.
• Instrument a documented set of conversion events: cta_click (with source), newsletter_submit, newsletter_confirm, blog_post_read (fires on scroll depth 80%), calculator_share, chain_matrix_sort, outbound_click (grouped by destination category).
• Vitals dashboard v2 at /vitals: keeps the existing per-page filter, adds per-locale filter, adds event conversion tiles alongside the existing LCP/INP/CLS charts, and a 30-day incident overlay from the status page (issue i18n scaffolding + Spanish locale baseline #10).
• Documentation on /privacy and /security updated to enumerate every event name, payload schema, retention, and the exact endpoint it hits.
• No new third-party requests; everything goes to the same first-party analytics endpoint already in use.

Acceptance.

• Every documented event fires exactly once per intended user action (Playwright coverage)
• DNT header set: zero network requests to the analytics endpoint (Playwright test fails otherwise)
• /vitals v2 renders per-page + per-locale filters, event tiles, and the incident overlay
• /privacy lists every event name and payload
• Build passes
• Lighthouse Perf/SEO stay >= 90 on /vitals

Files. src/utils/track.ts (new), src/pages/Vitals.tsx, src/hooks/useVitals.ts, src/pages/Privacy.tsx, src/pages/Security.tsx (see issue #1), instrumented components across src/components/ and src/pages/, e2e/analytics.spec.ts (new).

[Salauayo]

@Salauayo has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I've gone through your requirement thoroughly, I will fix this issues and implement a clean pull request to match your acceptance criteria.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Salauayo to this issue.

[akandeisaac021-design]

@akandeisaac021-design has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Focused on building trust through consistent, meaningful contributions. I approach every issue with curiosity, attention to detail, and a commitment to delivering clean, maintainable, and well-tested solutions. Driven by impact, not just commits, I value clear communication, effective collaboration with maintainers, continuous learning, and delivering meaningful value to every project I contribute to.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @akandeisaac021-design to this issue.

[Adedoyinjr]

@Adedoyinjr has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi! I’d like to work on this issue. I’ll first review the existing analytics, Web Vitals, and dashboard architecture, then implement the first-party event flow and Vitals dashboard v2 using the project’s established patterns. I’ll keep event collection lightweight and privacy-conscious, define consistent event/metric shapes, handle missing or partial telemetry gracefully, and add focused tests for the critical tracking and dashboard states without introducing unnecessary dependencies.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adedoyinjr to this issue.

[drips-wave]

Congratulations, @Adedoyinjr! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Adedoyinjr: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊