Public pages use no advertising trackers. The secure portal uses an essential session cookie and the service providers described in our privacy policy.

Skip to main content
← Back to Resources
Process·November 8, 2026·2 min read

How to Read a Website Data Transmission

A sample browser request explains the page, destination, fields, timing, and consent record, and what each can tell you about a website visit.

PR
Privacy Resolve
Last reviewed November 8, 2026

A browser request is a message your browser sends to load a page or use a website feature. Some go to the website itself. Others go to a separate service. Reading the destination and the information in the request helps explain what happened during a visit.

An example

Imagine a visitor opens https://example.test/services and chooses "Reject optional tracking." The visit record then shows a request to https://metrics.example.test/event with these sample fields:

  • page_path: /services
  • event: page_view
  • visitor_id: demo-visitor
  • consent_state: rejected

These sample domains, values, and events illustrate the fields. They are not a record of a real website visit. The .test domain is used for this example.

Page and destination

The page address tells you where the visitor was. The destination tells you where the browser sent the request. A different hostname alone does not establish who owns the service or whether information went to an independent third party. Check the domain, the website's vendor settings, and the actual service involved.

Information sent

Look at the request's query parameters and body, not just its name. In this example, the fields describe a page view and contain a sample visitor identifier. Real requests can have different fields. An identifier may allow events to be linked even when a request does not contain a person's name.

Do not assume a tool received the contents of a form just because it was present on the page. The record should show which fields were actually transmitted. Equally, the absence of a name does not by itself establish that a request was anonymous.

Compare the request time with the page load, the consent choice, and any later activity. A screenshot of a banner shows what appeared on the page. The request record shows what the browser sent. Together they can help distinguish the site's displayed choice from its behavior during that visit.

The sample consent_state value illustrates the field. For a real visit, read the available record of the choice and sequence.

What the record establishes

A recorded request can establish that particular information left a browser for a particular destination during the recorded visit. A successful network status can show that the destination answered. It does not alone establish every later use of the information, the destination's internal retention, or legal liability.

The legal question depends on the information, the recipients, the circumstances, and the law cited. The state-law guide explains why those questions should be kept separate.

Compare the record with your own site

Ask your website provider to identify the destination and match the request to the settings in use at the time. Keep the original record and note any later changes. Use the evidence-file guide for timestamps and file-integrity checks.

If the record identifies the wrong website, event, or business, use the factual correction route. Keep private records and access codes in the portal or direct correspondence rather than public comments.

General information only, not legal advice, and not a substitute for the advice of an attorney. Laws, deadlines, defenses and outcomes vary by jurisdiction and facts.