Track website visits, filters and downloads in PostHog - #75
Merged
Conversation
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.
The website had Google Analytics download tracking and a separate PostHog Node build client, but no PostHog browser SDK. Add browser initialization for the production hostname using the existing public write-only project token. Capture pageviews and interactions, report explicit filter selections, and forward successful single, ZIP and Bambu bundle downloads to both analytics providers.
The SDK loads asynchronously and queues early events. Provider failures are isolated from each other and from downloads. Local/preview hosts do not initialize PostHog. Session replay and surveys are disabled; anonymous visitors do not create identified person profiles.
Validation: