ModeConsentRun a Free SentinelScan
SentinelScan Evidence

Browser scan evidence

Real Chromium sessions capture cookies, scripts, requests, consent state, runtime errors, and page behavior for implementation validation.

Request Browser EvidenceView Services
  • Cookie and script inventory from browser sessions
  • Network request and page-state evidence
  • Runtime errors that can affect tracking

Browser scan evidence starts from the runtime page, not a vendor dashboard. SentinelScan records what a visitor's browser can observe during scan sessions.

That evidence helps teams separate configuration claims from live behavior across cookies, scripts, network requests, page state, and runtime errors.

The useful output is not only a list of findings. It is a record of timing, vendor exposure, consent visibility, and page conditions that can be handed to the people responsible for repair.

Scan coverage

What browser evidence captures.

The goal is to preserve enough detail for remediation, not just assign a score.

Cookies

Observed cookies are grouped for review by timing, classification, and consent relevance.

Scripts and vendors

Third-party scripts are tied to vendor domains and categories so teams can review exposure and decide which controls should govern them.

Network requests

Analytics, advertising, and platform requests are captured when visible during the scan.

Consent state

Visible dataLayer consent defaults and updates are preserved so teams can compare the intended state with runtime behavior.

Page state

SEO hygiene, canonical state, viewport, headings, and structured data are checked for regressions.

Runtime errors

Console and execution errors are surfaced when they may affect consent or tracking behavior.

Operational use cases

Built for teams that need validation before they rely on consent data.

  1. 01

    Launch checks

    Check high-value templates and conversion paths before public release.

  2. 02

    Consent bug triage

    Use runtime evidence to identify whether the issue is CMP configuration, GTM sequencing, hard-coded scripts, app embeds, or platform setup.

  3. 03

    Stakeholder review

    Give legal, marketing, analytics, and engineering teams one evidence set.

  4. 04

    Script cleanup

    Find vendors and scripts that no longer belong in the page stack.

Report evidence

Client-ready scan reports turn browser behavior into reviewable findings.

SentinelScan reports are designed to help legal, marketing, analytics, and web teams review the same technical evidence without relying on screenshots alone.

Grades

Compliance and security grades

Reports summarize technical scan results without claiming a legal conclusion.

Consent

Consent Mode and dataLayer status

Default, update, and page-state signals are preserved when visible so implementation teams can review timing and state.

Requests

GA4, Google Ads, cookies, and scripts

Network requests, cookies, third-party scripts, and regional differences are preserved for review.

Stakeholders

Public report URL

A client-ready URL lets legal, analytics, marketing, and web teams inspect the same scan.

Technical credibility

  • Headless Chromium scans
  • Regional scan workers
  • Postgres-backed scan history
  • Scheduled monitoring
  • Client-tagged automatic scans
  • Exportable summaries
SentinelScan audit

Start from the browser, not the settings screen.

SentinelScan captures the runtime evidence teams need before they can fix consent and tracking behavior.

Request Browser Evidence