feat: configure PostHog reverse proxy to bypass ad blockers #630
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.
Description
Motivation and Context
FIX #
Screenshots
API Changes
Change Type
Testing Performed
Checklist
High-level PR Summary
This PR configures a PostHog reverse proxy to bypass ad blockers by routing analytics requests through the application's own domain instead of directly to PostHog servers. The configuration adds URL rewrite rules in
next.config.tsto proxy requests from/ingestto PostHog's servers, and updates the PostHog client initialization to use the local/ingestendpoint instead of the external PostHog host. This approach helps prevent ad blockers from interfering with analytics collection while maintaining full PostHog functionality.⏱️ Estimated Review Time: 5-15 minutes
💡 Review Order Suggestion
surfsense_web/next.config.tssurfsense_web/instrumentation-client.ts