The collector returns 202 for both stored and dropped hits, and drop reasons are recorded on the site side, not sent back to the browser. Read a 202 in the network panel together with the realtime report.

Prerequisites

The page includes the snippet from Web analytics quickstart, and you can open the browser network panel.

Steps

1. Confirm the script ran

   The network panel should request w.js, and webcount should exist. A second copy exits immediately.

2. Find the collect request

   Next should be a POST to /api/v1/pulse on the script's origin. No request means the hit never left the browser.

3. Open realtime

   Look at the last few minutes on ConsoleWeb analyticsRealtime. If it is missing there, it will be missing from the event list.

4. Check hostname and time zone

   The hostname must be registered. See Project settings. Report dates use the project time zone, not your laptop clock.

Verify

Realtime shows the pageview you just made, with the same path and title.

Common failures

Do Not Track or Global Privacy Control stops the script unless you override it. localhost does not send by default. A mismatched host, a paused site, a monthly quota, or an exclusion rule drops the hit after the 202. If a single-page app misses route changes, see Pageviews & SPAs. Policies and blockers are in CSP, blockers & networks.

Next steps

For server events, add debug=1 to validate without storing. See Server events quickstart.