Guides
The work, not the feature list.
Each of these is a task somebody actually has to do. They are written as procedures for doing it properly, whether or not the tool you use is this one.
- 01
Set up Google Consent Mode properly
The ordering that actually matters: defaults before tags, update on decision, and how to tell from a scan whether your implementation got it right or only looks right.
- 02
Test whether your cookie banner really blocks anything
A procedure you can run by hand in ten minutes with browser devtools — refuse, reload, watch the network. Most banners fail this, and finding out yourself is better than being told.
- 03
Block the Meta Pixel until consent
Where the pixel usually comes from, why a tag-manager trigger is more reliable than a pattern match, and how to confirm it is genuinely held rather than merely delayed.
- 04
Find every cookie a website sets
Why the source HTML and the network tab give different answers, why a single page is not enough, and what a three-state scan adds over a manual look.
- 05
Consent for a WordPress site
Where tracking enters a WordPress site — themes, plugins, embeds — and the order to deal with them in, whether or not you use our plugin.
- 06
Consent for a Shopify store
Themes, apps and checkout-adjacent scripts, and what is and is not modifiable on the platform.
- 07
Understand GPC and what it obliges you to do
What the signal is, what it means in different jurisdictions, and why a runtime should detect it and let policy decide the effect.
- 08
Understand IAB TCF v2.4
What the framework does, who needs it, what registration involves, and how to tell whether you actually need it or have been told you do.
- 09
Keep proof of consent worth having
What a receipt should contain, why version references matter more than timestamps, and what makes a consent log useless at exactly the wrong moment.
- 10
Make a consent banner accessible
Focus management, keyboard operation, screen-reader labelling and contrast — the four things that make a modal interruption usable rather than an obstacle.
The full text of each guide is being written and will publish here as it is finished. We would rather list what is coming than fill this page with eight articles nobody would finish reading.
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