Summary

Implement Google Analytics for OpenHuman and verify that analytics events are flowing in the configured environment.

Problem

OpenHuman needs product analytics visibility to understand traffic, activation, engagement, and critical funnel behavior. Without Google Analytics configured and verified, the team lacks a reliable baseline for product usage and campaign/referral performance.

Constraints:

• Analytics must respect privacy requirements and avoid sending secrets, raw user content, message bodies, transcripts, credentials, or sensitive personal data.
• Environment-specific measurement IDs should be configurable and should not be hard-coded outside the approved config path.
• Desktop/Tauri behavior should be considered separately from any web landing page behavior.

Solution (optional)

Add Google Analytics initialization through the existing app configuration path, gate it by environment/config, and define a minimal event taxonomy for app open, onboarding milestones, auth/connect events, and key engagement surfaces. Verify events in GA DebugView or the relevant dashboard.

Acceptance criteria

• GA configured — Google Analytics is initialized using environment/config values for the intended staging/production targets.
• Page/app views tracked — Core app view or route/screen transitions are tracked where appropriate.
• Key events tracked — Initial product events are defined and emitted for onboarding, app open, account/connect milestones, and major engagement actions.
• Privacy safe — No secrets, raw messages, transcripts, credentials, or sensitive content are sent to Google Analytics.
• Environment gating — Analytics can be disabled or separated across local, staging, and production environments.
• Verification complete — Events are observed in GA DebugView or the target analytics dashboard and the measurement ID/environment are documented.
• Regression safety — Unit or integration coverage verifies analytics initialization, config gating, and event payload sanitization where testable.
• Diff coverage ≥ 80% — the implementing PR meets the changed-lines coverage gate (Vitest + cargo-llvm-cov, enforced by .github/workflows/coverage.yml).

Related

• Product analytics and growth measurement workstream.