Extension Pro
Debug Snapshot
Export a privacy-conscious diagnostic bundle with redacted scan data, a compact HAR-style request log and an optional screenshot.
Compliance bugs often need to be reproduced by someone who was not present during the scan. A useful handoff should include the timeline and request evidence, but it should not casually expose cookie values or other sensitive page data.
Debug Snapshot packages the current ConsentScope observations into a portable JSON file. It includes normalized scan details, a compact HAR-style network section and, when requested, a screenshot of the inspected tab. Cookie values are redacted by default.
The snapshot is generated only when the Pro user requests it. It is designed for issue trackers, internal debugging and support handoffs, not as a replacement for a full browser HAR or legal report.
Capture the smallest session that reproduces the issue
Use a test profile and navigate directly to the affected page. Reproduce only the steps needed to trigger the behavior. A compact session is easier to interpret and less likely to contain unrelated browsing, account details or private page content.
Record the starting state before exporting: new visitor, saved rejection or previously accepted service. If the problem is withdrawal, do not reset storage between acceptance and revocation. The resulting sequence is part of the evidence. Include the extension version when comparing snapshots from different machines.
What to send with the JSON file
| Ticket field | Why it matters | Illustrative entry |
|---|---|---|
| Tested URL and template | Identifies the affected implementation | Public product page, logged out |
| Starting consent state | Makes the sequence reproducible | No stored preference |
| Actions | Shows how the problem was triggered | Load, reject, open booking widget |
| Expected and observed behavior | Separates the requirement from the evidence | Marketing remains off; vendor request observed |
| Known limitations | Prevents a false sense of completeness | No source stack available for this request |
The table is a ticket-writing example, not a report from a customer scan. Replace it with the actual reproduction details. The snapshot carries technical observations; it cannot explain a business requirement that the tester never wrote down.
Redaction is a safeguard, not permission to publish
Cookie-value redaction reduces one source of exposure. It does not make every artifact anonymous. A URL can contain an account identifier or a search term. A screenshot can show a customer name, private dashboard or typed form value. Inspect the exported material before sharing it.
Prefer a private issue tracker with access limited to the people who need the evidence. Do not upload a snapshot to a public ticket merely because it was generated by an auditing tool. If a sensitive workflow is involved, use staging or a synthetic account and omit the screenshot unless it is necessary.
Choose a snapshot, a HAR or a PDF for the task
Use Debug Snapshot when the recipient needs ConsentScope's captured context in a structured file. Use the browser's Network tooling when the investigation requires a fuller HTTP archive or details not present in the compact HAR-style section. Those formats are related, but they are not interchangeable.
Use a PDF report for a client summary with scope and reviewed findings. Keep detailed diagnostics out of that summary unless the recipient needs them. The DevTools panel is the place to investigate before exporting.
Make the before-and-after comparison honest
After the fix, recreate the same URL, consent state and interaction sequence. Retain the original snapshot and label the new one with the retest date. Compare the specific request or cookie behavior rather than only the total number of entries.
If the second run has a different region, browser state or blocked page load, explain that difference. A smaller file does not prove less tracking, and a missing request in an incomplete run does not verify a fix. Use initiator context to investigate persistent activity and keep unresolved questions in the ticket.
How it works
Reproduce the consent issue and open the ConsentScope DevTools Panel.
Choose whether to include a screenshot in the diagnostic bundle.
Create the snapshot; ConsentScope redacts cookie values and serializes the captured timeline and requests.
Attach the downloaded JSON file to a private ticket or share it with the team responsible for remediation.
Key benefits
Redacted by default
Cookie values are removed from the exported diagnostic data.
Portable evidence
Share one structured file instead of copying rows from multiple browser panels.
Compact request log
Include HAR-style request metadata without pretending to be a full browser HAR.
Better bug reports
Give developers reproducible context, timing and an optional visual reference.
Who is it for
Engineering teams
Receive structured evidence that is easier to reproduce and investigate.
Agencies
Attach a concise technical artifact to client remediation tickets.
Privacy engineers
Document findings while minimizing sensitive values in the export.
Frequently asked questions
Are cookie values included?
Is the request export a full HAR file?
Is a screenshot always captured?
Unlock Debug Snapshot 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