Methodology

How ConsentProbe tests storefront runtime behavior

ConsentProbe runs automated browser scenarios and records requests, cookies, CMP actions, and screenshots, then flags potential compliance risks.

Flagged risks are technical observations for your team and counsel to review. They are not legal advice and not a compliance verdict.

EU fresh visit

A clean EU browser profile opens the storefront without interacting with the consent banner to record pre-choice tracking.

EU reject all

ConsentProbe locates the CMP banner, clicks Reject All, and checks whether marketing tags or analytics requests continue firing.

EU accept all

ConsentProbe clicks Accept All on the CMP banner to provide a comparison baseline of vendors that load only after consent.

California fresh visit

A clean California browser profile opens the store with GPC disabled to record baseline tracking behavior.

California GPC

A California browser profile with Global Privacy Control enabled checks whether ad networks and third parties honor the opt-out signal.

Collected evidence layers

Cookie and storage snapshots

Network requests and third-party scripts

CMP detections and button actions

Screenshots and scenario timestamps

Technical findings with recommended remediation

BASIC

Baseline audits identify CMP banners, detect third-party vendors, record storage and network requests, and capture full-page screenshots.

FULL

Regional audits add evidence-grounded interpretation, severity prioritization, owner assignments, and specific retesting steps for engineering and marketing teams.

Related storefront guides

These checklists explain how to read cookies, network requests, CMP actions, and consent-mode traffic against the same evidence layers used in a runtime audit.

How ConsentProbe tests storefront runtime behavior | ConsentProbe