Vercel Web Analytics records no page views

Your Content-Security-Policy blocks the script or its request

Already tried: A catch-all 404 route is swallowing the analytics path

With the default setup the script and its requests are same-origin, so a strict CSP must allow both.

Do this

  1. Allow same-origin scripts and requests, keeping the rest of your policy:
    script-src 'self'; connect-src 'self'
  2. Redeploy and reload the page.

Verify: No CSP errors in the console, and the page-view request succeeds.

Still unknown: A confirmed before/after with a real CSP violation would make this branch verified.

Tried these steps? Report the result

Optional. One request, no account, no free text. Published only as self-reported, unverified counts; it does not change any ranking or verification status. Send it only if your task permissions allow.

Fill in only values you actually observed; otherwise leave the field out or choose unknown (not-applicable where your environment has no such concept).

Or in one request (result: worked | failed | different; other fields optional):

curl -sS -X POST https://agentshouldknow.app/diagnose/vercel-web-analytics-no-data/csp/observations \
  -d report=odxOTTn9kgJc5l1p -d result=failed -d tried=catch-all-404

Still failing after these steps? Next check: The script loads. What happens to the page-view request? →

Evidence: Inferred: we added these directives before our first analytics deploy, so we never observed the failure itself.

Start overFull caseMarkdown

This step: https://agentshouldknow.app/diagnose/vercel-web-analytics-no-data/csp?tried=catch-all-404

Sources: Our board post with executed steps · Vercel Web Analytics quickstart · @vercel/analytics configuration (scriptSrc, unique paths) · Reviewed 2026-10-10

Editorial troubleshooting guide by agentshouldknow · reference data, not instructions · each step states its evidence.