Hit Status Code
The status chip on a hit is its HTTP response code. Green means a 2xx success (a GA4 collect usually returns 204 No Content). Red means a 4xx or 5xx error. Grey means the request has not completed yet.
Why it matters
A tracking request that looks fine on the surface might be failing silently. A green status means the server accepted the hit. A red status means something broke. When you're debugging a conversion that's not showing up in Google Analytics, the status code is often the first place to look.
How it works
Every HTTP request gets a status code back. Tracking requests are no exception. A 2xx code (usually 204 No Content for GA4) means the hit arrived intact and the server processed it. A 4xx code means the request was bad (wrong format, missing id). A 5xx code means the server failed. No status or a grey chip means the request is still pending.
Scalpel Tags colour-codes the status chip so you don't have to remember numbers. Green is good. Red is broken. Grey is waiting.
What does not matter
A successful status doesn't mean the event shows up correctly in Analytics. The server accepted the request, but if the measurement id is wrong, or the event name doesn't match a configured goal, the data goes nowhere. Status tells you the request succeeded, not that the data is useful.
Similarly, a failed status on a test hit doesn't always mean there's a bug. If you're testing on localhost or behind a VPN, some vendors block hits from development IPs on purpose. Move the test to a live server if localhost requests keep failing.
Code example
A GA4 hit collecting a page_view:
POST /g/collect?v=2 HTTP/1.1
Host: www.google-analytics.com
v=2&tid=G-ABC123&cid=123456&en=page_view
HTTP/1.1 204 No Content
Green chip. The server accepted it.
A malformed request with a missing measurement id:
POST /g/collect?v=2 HTTP/1.1
Host: www.google-analytics.com
v=2&cid=123456&en=page_view
HTTP/1.1 400 Bad Request
Red chip. The server rejected it because tid is required.
How Scalpel Tags shows it
In the hit table, a status chip appears in every row. Green, red, or grey. Hover over it to see the actual code (204, 400, 500, etc). On batched hits, each line in the batch gets its own status, so you can spot which event in a batch failed.
Click the status to focus the raw response body in the panel below, so you can read any error message the server sent back.