Tracking problems are often invisible from the front end
Automated browser scanWorking product build
Compliance Scan
A browser-driven scan that checks advertising platforms, tracking method, cookie banner and pre-consent behaviour.
- Scope
- Standalone acquisition tool
- Timeline
- MVP with successive validation rounds
- Status
- Working product build
What we built
From domain to a verifiable scan result
The Compliance Scan opens a website in a secured browser environment, observes network traffic and cookies before and after consent and translates those signals into an understandable result.
03 / USE CASES
For teams that need to know what their website technically does.
Advertisers
Checks whether advertising tags, click IDs and consent behaviour match the chosen measurement and privacy strategy.
Agencies and media buyers
Creates a repeatable technical baseline before campaigns, tracking or server-side implementations are changed.
Privacy and analytics
Gives technical teams a concrete view of cookies, requests, CMP behaviour and signals before and after consent.
04 / DELIVERABLES
Deliverables
Browser automation
A bounded scan that opens websites safely and collects relevant signals.
Platform detection
Identification of advertising platforms through requests, cookies and configuration signals.
Tracking classification
Distinguishes client-side, hybrid and server-side collection where externally verifiable.
Consent review
Separate observation before consent and after interacting with a recognised cookie banner.
05 / PROCESS
From challenge to working product
- 01
Signal model
Advertising platforms, CMPs, cookies and tracking methods were translated into verifiable rules.
- 02
Scan engine
Browser budget, concurrency, security and failure paths were built around the scanner.
- 03
Result flow
Technical findings are combined into a readable result and commercial next step.
06 / GUIDES
The growth questions this system addresses
Need to build something that has to perform commercially?