Insights
Nothing published here yet.
Rather than fill this page with three articles written to have something on it, here is the actual editorial queue. Each piece publishes when it is worth someone's time.
- In the queueWhat actually happens after someone presses “Reject all” on your website
- In the queueGoogle Consent Mode v2: basic vs advanced, and which one you are really running
- In the queueHow to test whether a cookie banner blocks anything, in ten minutes
- In the queueCookies are not the point any more: storage and access technologies explained
- In the queueProof of consent: what a receipt needs to contain to be worth keeping
- In the queueIAB TCF v2.4 and what the web transition means for publishers
- In the queueGPC, GPP and Consent Mode: three signals, one visitor choice
- In the queueWhy per-subpage pricing is the wrong meter for consent tooling
- In the queueConsent for website builders: compiling privacy instead of retrofitting it
- In the queueThe accessibility of consent dialogues, and why it is a product defect
If one of these would be useful sooner, say which — it moves up the queue.
Know what runs before you ask visitors to trust it.
Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.
No code to install for a scan Public pages only DotCensus runs on DotCensus