ConsentProbe

A consent banner can offer Reject All and still let analytics fire. ConsentProbe is built to catch that gap. You give it a public storefront URL, it loads the page in a real browser, and the report lists the cookies set, the storage written, the network requests made and the scripts loaded, with screenshots of what the visitor saw.

The free run is one fresh visit from a US location outside California, before any click on the banner. It gives you a baseline but can't tell you what happens after a rejection. That needs a paid run. The $49 EU audit adds Reject All and Accept visits to the fresh one, the $49 California audit pairs visits with the Global Privacy Control signal off and on, and the $79 Global 2 order runs both.

The site is strict about what each piece of evidence proves, and that's the most useful thing about it. A banner screenshot shows what the visitor was offered. The consent tool's own state shows what it claimed to record. Only the network log shows whether requests actually stopped. Reports name the region and scenarios that ran, and each finding points back to a cookie row, a request or a screenshot from that visit. A US-baseline result isn't presented as an EU or California conclusion.

The site also publishes findings from its own runs with store names removed. One article records a store's browser still sending Microsoft Clarity collection requests after Reject All, and another counts requests to six third-party services after a visitor declined Shopify's banner.

ConsentProbe doesn't install a banner, change your theme or give a legal opinion. It doesn't crawl checkout, admin or logged-in pages, and it can't see server-side events that never reach the browser. Treat the report as a technical record for an engineering ticket or a conversation with your consent-tool vendor. There are also free quick checks, one showing whether your own browser sends GPC and one decoding a TCF v2 consent string.