Extension Pro
ConsentScope DevTools Panel
Inspect consent events, cookies, storage, scripts and network activity in a dedicated browser DevTools workspace.
Consent problems are timing problems. A tracker may fire a few milliseconds before the consent platform initializes, a tag manager may inject a vendor script indirectly, or a storage write may happen long before the banner becomes interactive. A popup summary can reveal the issue, but developers also need the sequence that produced it.
The ConsentScope DevTools Panel brings the live audit into the browser tools you already use. It combines the consent timeline, cookies, browser storage, third-party scripts and observed network requests for the inspected tab, with clear before-consent and after-consent states.
The panel is available to Pro users and works with ConsentScope's existing detection engine. It adds a debugging surface without changing the monitored page or sending diagnostic exports automatically.
Start the panel before the action you want to debug
Open developer tools on the target page, select ConsentScope and reload. If you open the panel only after dismissing a banner, the visible state may not explain the initial sequence. Write down whether the visit started with no saved preference, a rejection or an earlier grant.
Keep a separate run for each scenario. First leave the banner untouched, then test rejection in a clean session. A later run can test partial consent or withdrawal without clearing the accepted state. This prevents a common reporting error: presenting observations from several different consent states as one continuous reproduction.
Choose the view that answers your next question
| Question | Start with | Follow-up |
|---|---|---|
| What happened before the choice? | The timeline and phase labels | Confirm the consent event was detected |
| Which endpoint was contacted? | The requests view | Inspect destination and available document context |
| Which service might have loaded it? | The initiator view | Verify the integration in code or the tag manager |
| What should another developer receive? | Debug Snapshot | Add the exact steps and review the exported data |
The dedicated panel keeps ConsentScope observations together. It does not replace the browser's source debugger, complete Network tools or a CMP administration console. Use those tools when you need a source breakpoint, a response body or the published consent configuration.
Walk through a route-specific regression
Imagine that the homepage passes a fresh-visit check, but navigating to a pricing page starts an optional service after Reject. Keep the panel open while reproducing that navigation. Identify the first unexpected request and note whether the consent phase changed or only the resource inventory changed.
Next inspect the route's components and integrations. A dynamically mounted widget is a different lead from a globally installed tag. Use Initiator Trace when the browser exposes context, then confirm the owner before editing the implementation. This example is a suggested debugging exercise, not an actual client result.
Handle empty or unexpected results
Check that the panel is inspecting the intended tab and that ConsentScope has permission to observe that page. Reload after opening the tools. Browser-internal pages, restricted documents or an incomplete load may not provide the observations you expect. An empty table does not establish a clean consent implementation.
If a consent event is missing, document it and compare the banner's visible choice with the recorded activity. Do not rewrite the phase labels mentally as if detection had succeeded. The CMP check and the vendor's integration tools can help explain the gap.
Keep the debugging session reproducible
A useful ticket includes the URL, browser version, extension version, starting storage state and precise actions. Add the observed request or cookie name and the expected behavior. Keep unrelated customer browsing out of the attachment by reproducing the issue in a dedicated session.
Export a reviewed snapshot for technical detail. If the client needs a summary, prepare a separate PDF report that explains scope and next steps. The panel is an investigation surface, not evidence that every page or region has been audited.
How it works
Open browser DevTools on the page you want to inspect and select the ConsentScope panel.
Reload the page so ConsentScope captures the complete sequence from initial navigation onward.
Filter the timeline or request table to isolate pre-consent cookies, storage writes and third-party calls.
Open the initiator view or create a redacted Debug Snapshot when you need evidence for a ticket or client report.
Key benefits
One chronological view
See page load, request, storage and consent events in the order they happened.
Developer context
Inspect request type, destination, timing and consent state without switching tools.
Pro-only access
Keep advanced diagnostics within licensed audit workflows.
Faster remediation
Turn a generic violation into an actionable engineering investigation.
Who is it for
Frontend developers
Debug CMP initialization order and scripts that escape consent controls.
Technical agencies
Collect clear evidence before handing remediation work to a client team.
Privacy engineers
Connect compliance findings with browser-level technical behavior.
Frequently asked questions
Where do I open the panel?
Does the panel modify the inspected website?
Is the DevTools Panel included in Free?
Unlock ConsentScope DevTools Panel 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