Show what the browser tag never saw - #4
Merged
Merged
Conversation
The tag has to load and run before it can report, so anything that never executes JavaScript is invisible to it. That was unmeasurable until server-side recording existed. Now that the Phoenix plug reports the same pageviews the tag does, the gap between them is a number, and this tab is it. A pageview reported by the server alone carries no viewport height and no heartbeat, because a server has no viewport and does not sit on a page. Both are required before calling one untagged -- a visitor who leaves inside a second is gone before the first heartbeat, and either signal alone would misread them. - Splits misses into automated and not. A crawler missing the tag is expected; a person missing it is a blocked script or an untagged page, and the tab says so plainly - Counts crawlers even with the crawler filter on, since hiding the largest thing the tag misses would defeat the report - Groups by path, never title: a title is one of the things only the tag can supply 619 tests passing, 11 of them new. Closes #3 --- Pages affected: - [Seriously Simple Analytics](https://seriouslysimpleanalytics.com/) -- the dashboard this tab joins. - [AI crawler analytics](https://seriouslysimpleanalytics.com/ai-crawler-analytics) -- the automated half of what the tag misses. - [Analytics MCP server](https://seriouslysimpleanalytics.com/analytics-mcp-server) -- the same numbers, queryable from an agent. - [MCP Harbor](https://ai.mcpharbor.com/) -- a site already feeding this with server-side data. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
lbesecker195
changed the base branch from
main
to
mcp-registry-optimization
September 19, 2026 04:49
3 tasks
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 tag has to load and run before it can report, so anything that never executes JavaScript is invisible to it. That was unmeasurable until server-side recording existed. Now that the Phoenix plug reports the same pageviews the tag does, the gap between them is a number — and this tab is that number.
A pageview reported by the server alone carries no viewport height and no heartbeat, because a server has no viewport and does not sit on a page. Both are required before calling one untagged: a visitor who leaves inside a second is gone before the first heartbeat, so either signal alone would misread them.
The split that matters is automated versus not. A crawler missing the tag is expected and is the reason server-side recording exists. A person missing it is a finding — a blocked script, a failed asset, or a page the snippet was never added to — and the tab calls that out rather than burying it in a total.
Crawlers are counted here even with the crawler filter on. A report about what the tag misses that hid the largest thing it misses would be worse than no report.
Grouped by path, never by title, because a title is one of the things only the tag can supply — grouping by it would return one unnamed row holding everything.
Verified against a real dashboard: 645 pageviews, 97.8% seen by the tag, 8 automated misses and 6 that were not automated.
619 tests pass, 11 of them new.
Closes #3
Pages affected:
🤖 Generated with Claude Code