feat: add PostHog analytics via a same-origin CloudFront proxy#53
Merged
Conversation
Wires in posthog-js through Next.js's instrumentation-client.ts (no provider/pageview boilerplate needed with the current SDK defaults). Events route through a new /relay/* CloudFront behavior straight to PostHog's own origin — a CloudFront Function strips the prefix, no Lambda invocation involved — so requests are same-origin and don't get dropped by ad/tracker blockers the way a direct posthog.com call would. Dev and prod use separate PostHog projects, tokens injected per-stage via GitHub Actions secrets at build time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Wires in posthog-js through Next.js's instrumentation-client.ts (no provider/pageview boilerplate needed with the current SDK defaults). Events route through a new /relay/* CloudFront behavior straight to PostHog's own origin — a CloudFront Function strips the prefix, no Lambda invocation involved — so requests are same-origin and don't get dropped by ad/tracker blockers the way a direct posthog.com call would. Dev and prod use separate PostHog projects, tokens injected per-stage via GitHub Actions secrets at build time.