Extension Pro
Network Request Interception
Review observed browser requests alongside consent timing to investigate pixels, analytics calls and unexpected destinations.
A cookie inventory can miss activity that sends data without creating a new cookie. ConsentScope Pro adds observed network requests to the audit so you can investigate visible destinations and timing alongside the visitor's consent choice.
Despite the feature's name, this is a passive observation workflow, not a request-blocking firewall. The browser API and extension permissions determine what is available. A request record is not a complete payload capture or a map of every server-side recipient.
Use the request list to identify a specific transmission to investigate. Confirm its purpose with the implementation owner, and compare its behavior before interaction, after rejection and after the relevant grant.
Start with the action, then inspect the request
Record the visitor action that produces the call: initial page load, opening a widget, submitting a test form or changing a consent preference. Repeating that action is more useful than searching a large request list without a hypothesis. Keep the consent state visible in the test record.
Compare the same action in a clean rejected session and a session where the relevant purpose is allowed. If the request occurs in both, establish whether that is intentional for the integration. A content request, a consent receipt and an analytics event should not receive the same conclusion merely because all use HTTP.
Read the available fields without inventing the missing ones
| Field or signal | Useful for | Limit |
|---|---|---|
| Destination URL | Identifying a service or endpoint | A first-party URL may forward data elsewhere |
| Request type and method | Distinguishing resource and API patterns | They do not reveal the full purpose |
| Timing and consent phase | Reconstructing the observed sequence | Consent detection can be incomplete |
| Initiator or document context | Finding the responsible frame or origin | Not necessarily the exact source line |
Chrome documents the capabilities and constraints of its webRequest API. Browser-internal traffic, permissions and request handling can limit visibility. Present the output as captured browser evidence rather than a promise to intercept every possible transmission.
Investigate a first-party collection endpoint
A hypothetical site sends a POST to its own /collect endpoint after Reject. The same-origin URL does not establish that the call is necessary, and it does not prove that data leaves the organization. Ask the server-side owner what the endpoint receives, how it handles consent and which systems it contacts.
Keep browser and server evidence separate until they can be correlated. The server-side tracking guide explains the broader review. ConsentScope cannot fill missing backend logs with an inferred data-flow diagram.
Use cookies and request timing together
For Google integrations, account for the difference between basic blocking and advanced cookieless pings. Use the Consent Mode check and Tag Assistant to establish the intended state. Then inspect identifiers and new storage writes where available, rather than classifying a request solely by its domain.
When the destination is unexpected, consult the script inventory and initiator view. Attach a reviewed snapshot to a private ticket. URLs can contain sensitive parameters even when cookie values have been removed.
How it works
Begin observation before reloading the page you intend to test.
Review the observed destinations, request types and timing against consent.
Reproduce the interaction that starts the suspicious call and inspect available initiator context.
Fix the responsible integration outside ConsentScope and rerun the same scenario.
Key benefits
Request-level context
Review visible transmissions as well as cookies.
Consent timing
Place the observed call before or after the detected choice.
A focused handoff
Give the owner a destination and reproducible action to investigate.
Who is it for
Security teams
Investigate unexpected browser requests and third-party connections.
Privacy engineers
Compare browser-visible tracking requests with the selected consent state.
Developers
Review request context and timing when reproducing an integration issue.
Frequently asked questions
Can this block a tracking request?
Can it see server-to-server forwarding?
Does the request list include complete bodies and response data?
Unlock Network Request Interception with ConsentScope Pro
Extension Pro provides lifetime access to the paid browser features. Monitor and Agency are separate subscriptions for cloud monitoring. Compare the plans for your workflow.
View Extension Pro