Repository navigation
fix(analytics): keep initial pageviews enabled - #31
Merged
Merged
Conversation
This branch was previously deployed
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
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.
Summary\n- Allow the Google tag config to send the initial pageview on each document load.\n- Skip that first path in the client tracker and keep queued manual pageviews for later App Router path changes.\n- This keeps pageview collection independent of React effect timing while avoiding duplicate initial events.\n\n## Validation\n- npm run lint\n- npm run build\n- Static export assertion: active ID present, old ID absent, initial suppression removed, SPA pageview code retained.\n- git diff --check