An analytics request appears in Chrome DevTools and returns a successful status. The report still looks wrong. That is possible: delivery, valid content and correct reporting are separate checks.
Reading the request helps you identify what the browser sent, where it sent it, and what the receiving service confirmed. Start with those facts before changing a tag or explaining a missing event.
Identify the destination and purpose
A URL identifies the target. Its scheme indicates HTTP or HTTPS, the hostname identifies the host, and the path identifies the resource. Query parameters follow the question mark. HTTPS protects the exchange in transit; it does not establish that the values are correct.
For a measurement request, check the full destination and any property or stream identifier required by that endpoint. A request sent to a test destination can be technically successful while contributing nothing to the production report.
The method describes the intended operation. GET retrieves a representation; POST submits content and can cause side effects. OPTIONS can appear before a cross-origin request. MDN documents these HTTP method meanings.
Do not infer the full payload from the method. A POST request can have query parameters as well as a body. Inspect both. The endpoint documentation determines which fields belong where.
Read the headers and the values separately
Headers describe the exchange. Request headers and response headers belong to different directions. For example, Content-Type identifies the media type of the content being sent. A JSON body normally uses application/json.
The body carries the submitted content. Query parameters carry values in the URL. In DevTools, compare the decoded values with the expected field names, types and units. A value can look right on screen while being encoded or typed incorrectly.
