Repository navigation
feat(web): count page views - #24
Merged
Merged
Conversation
Enabling Web Analytics in the Vercel dashboard collects nothing from a Next.js app on its own - the beacon is a component, and without it the toggle is off in one place and absent in the other. `<Analytics />` mounts in the root layout. The question it answers is the one the chain cannot. The seller account counts demo runs exactly, two payments each, but a visitor who opened the page and did not press the button leaves no trace on chain at all. Those two cases want different fixes and until now looked identical: 0 runs against 93 views could mean the page does not convert or that almost nobody arrived. Cookieless, and page views only. The claim that nothing of ours sits in the payment path is unaffected - this runs on the page, not between the button and the chain. Collection starts from deploy. The launch traffic is already gone and does not backfill. 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
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.
Enabling Web Analytics in the Vercel dashboard collects nothing from a Next.js app on its own. The beacon is a component, so without it the feature is on in one place and absent in the other, and the project reports 0 views indefinitely.
What is here
@vercel/analytics2.0.1app/layout.tsx<Analytics />from@vercel/analytics/next, mounted inbodyFindings
The chain cannot answer this question. The seller account counts demo runs exactly, at 2 payments each, and it stood at 63 before the launch post and 63 after 93 views. A visitor who opened the page and did not press the button leaves no trace on chain, so "the page does not convert" and "almost nobody arrived" look identical from there and want opposite fixes.
The dashboard toggle is half the feature. Other frameworks inject the script at the platform layer; a Next.js app has to mount the component, and
@vercel/analytics/nextis the subpath that carries the App Router version.Nothing changes about the payment path. The beacon is cookieless and records page views. It runs on the page rather than between the button and the chain, so the claim in
web/README.mdthat no route sits behind the button still holds.Verification
tsc --noEmitclean and 37 tests pass, which confirms the subpath resolves at the type level. The script itself mounts client-side after hydration and is debug-only in development, so it does not appear in served HTML locally and is checked on the deployment instead.Collection starts at deploy. The launch traffic is already gone and does not backfill.
Scope
Web only. The contract, the SDK and the seller are untouched. Unaudited, and built for testnet.