scripts: read the web product page — "blind to the website" was also wrong - #447
Merged
Conversation
…wrong
`App Store Web Preview Engagement Standard` had 14 ONGOING instances and had
never been read. It covers the apps.apple.com product page as viewed in a
BROWSER: 163 rows over 63 days, 2026-04-01..08-17.
web product page views 156
├─ Tap "View in Mac App Store" 40 (25.6%)
├─ Product screenshots expanded 4
├─ Developer preview page 2
└─ Developer website 2
US 70 · CN 20 · Chrome 122 · Desktop 126
That `View in Mac App Store` tap is a measurable web -> store handoff, so this
file's own docstring claim — "structurally blind to someone who reads the
website and runs brew install" — is partly false and is corrected here.
It NARROWS the gap without closing it, and the section says so where someone
would read it:
* `Source Type` is entirely `Unavailable`, so it cannot separate a visitor
our website sent from one a search engine sent. That was the actual
question, and it remains unanswered.
* Crawler-contaminated: bingbot accounts for 6 of the 156 page views, and the
section prints that count rather than burying it.
* A web page view is a much stronger intent signal than an in-store
impression, so 25.6% must NOT be read against the storefront's 0.851%.
Different denominators, different animals.
Also printed rather than smoothed over: 40 handoff taps here versus 5 Mac
`Web referrer` page views in the storefront report. Either the handoff loses
most people or the two reports attribute differently. Two numbers, not one,
until someone establishes which.
Third instance of the same pattern in this project — "we are blind to X"
turning out to mean "nobody opened the report about X". The docstring now says
so, because the next person will have the same instinct.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 was unread
App Store Web Preview Engagement Standardhad 14 ONGOING instances and had never been opened. It covers theapps.apple.comproduct page as viewed in a browser — 163 rows over 63 days, 2026-04-01 → 08-17:That handoff tap makes this file's own docstring claim — "structurally blind to someone who reads the website and runs
brew install" — partly false. Corrected here.It narrows the gap; it does not close it
The section says all three of these where someone would actually read them:
Source Typeis entirelyUnavailable, so it cannot separate a visitor our website sent from one a search engine sent. That was the actual question, and it stays unanswered.bingbotaccounts for 6 of the 156 page views. The section prints that count rather than burying it.One discrepancy, printed rather than smoothed over
40 handoff taps here versus 5 Mac
Web referrerpage views in the storefront report. Either the handoff loses most people, or the two reports attribute differently. Two numbers, not one, until someone establishes which — so the code doesn't reconcile them.The pattern
This is the third time in this project that "we are blind to X" turned out to mean "nobody opened the report about X" — after the censored
Detailedvariants and the install/deletion cohort. The docstring now says so, because the next person will have the same instinct.Verification
--self-testpasses (the anti-threshold guard applies to the new feed too).ruffclean — and it caught anF541in my own new code, which is the gate from ci: make ruff actually lint the Python it claimed to lint #437 working on the person who built it.🤖 Generated with Claude Code