Add lightweight website measurement and improvement loop#83
Merged
Conversation
masarray
marked this pull request as ready for review
July 20, 2026 10:05
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
What changed
Data sources
Safe defaults
The website remains fully functional with measurement disabled until
GA4_MEASUREMENT_IDis configured. The reporting engine clearly marks GA4, Search Console or CrUX data unavailable when read-only credentials or sufficient field samples are absent; it never fabricates metrics.Validation
The scheduled remote GA4/Search Console/PageSpeed report is intentionally not executed on pull requests. It runs weekly or manually after the read-only repository configuration is present.