docs(analytics): plan for proxy + server-side business events#713
Draft
spashii wants to merge 1 commit into
Draft
docs(analytics): plan for proxy + server-side business events#713spashii wants to merge 1 commit into
spashii wants to merge 1 commit into
Conversation
Team-facing plan (docs/plan.md) and engineering companion (docs/analytics-implementation-plan.md) covering the reverse-proxy foundation, server-side event capture, portal journey + source attribution, app-health events, and the open decisions (proxy home / EU residency, PostHog MCP, marketing-site stitching). Planning only; no code changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Draft plan (docs only, no code) for instrumenting the analytics we currently can't see: where customers come from, the participant journey, and app health.
Two docs:
docs/plan.md— team-facing "what and why", non-technical. Meant to seed a discussion thread.docs/analytics-implementation-plan.md— engineering companion: the "how", phased, with endpoints and the corrected proxy config.Highlights for review
e.dembrane.com) vs self-host in our ams3 cluster vs a Vercel/istopgap. Hinges on EU data residency tolerance.analytics.py), so they can't be blocked or lost. Naming:server_prefix, with asourceproperty for cross-client funnels like registration.Status
Planning only. Nothing built. Open decisions are listed at the bottom of the implementation doc (proxy home, PostHog MCP connection, marketing-site PostHog project, dashboards in both EU projects).
🤖 Generated with Claude Code