Add growth funnel analytics to docs and developer pages

[juandolealt]

Summary

• add acquisition and engagement analytics across docs and developer pages, with early event queuing and deferred PostHog loading
• capture pageviews, search interactions, code and command copies, demo engagement, and strategic CTA clicks
• align CTA properties with the website envelope: cta_type, button_text, destination, location, broad conversion_intent, and granular conversion_detail
• isolate browser analytics to Tempo production hosts and register site, surface, tempo_app_id, client_type=browser, and release metadata
• sanitize URLs, page paths, heatmap URL keys, campaign data, and named blockchain properties including wallet, sender, recipient, transaction hash, and memo fields

Scope

This PR provides acquisition and engagement measurement infrastructure only. It does not define or verify activation, qualified-developer, or human-traffic outcomes. client_type=browser describes the runtime and is not a human verification signal.

Data safety

• no raw search queries, copied code, commands, wallet addresses, transaction hashes, memos, form values, request headers, or request bodies are sent
• inputs, text, attributes, and sensitive selectors are masked for replay
• arbitrary query parameters and URL fragments are removed; wallet-like path segments are redacted
• UTM values use a conservative allowlist; click IDs are reduced to a presence marker
• replay is disabled when the landing URL contains non-attribution or unsafe query data

Validation

• CI=true pnpm exec vitest run src/lib/posthog-analytics.test.ts (31 tests)
• CI=true pnpm test (163 tests)
• pnpm check:types
• CI=true pnpm build
• Biome and git diff --check

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tempo-docs	Ready	Preview, Comment	Jul 11, 2026 2:39am

[juandolealt]

@snario can i add this? so we can track actions, link clicks, etc. in posthog