Guide
The jobs, not the features.
Ten practical guides for the work consent actually involves: finding what is loading, holding it until the visitor agrees, proving that you did, and migrating off whatever is there now.
How to audit cookies on a website
Every consent project starts with an inventory. Browser observation is essential runtime evidence, and it should be reconciled with source, tag-manager configuration, vendor consoles, CSP reports and server-side data flows.
Time: Estimate: hours for a first pass
Blocking scripts before consent
The reliable distinction is whether optional executable code is absent before a valid choice, not whether a banner or disabled-looking tag is visible.
Works: Never creating the element
Fixing trackers that fire before consent
Six common causes of an optional request appearing before a choice, arranged as a diagnostic sequence rather than a guess.
Symptom: Requests before any choice
Writing a cookie declaration
A list of cookies is a transparency document, and a wrong one is a documented inaccuracy. Generate it from what a scan observed rather than from what a vendor’s documentation claims.
Source: A verified scan
Proving consent
The obligation is not to collect consent. It is to be able to show, later, that you did, for a specific visitor, against specific wording.
Source: GDPR Art. 7(1); LGPD Art. 8 §2
Choosing a consent model
Four profiles, three models, and one decision that shapes every visitor’s experience. Most sites should make it once, on purpose, and write down why.
Profiles: Four
GDPR cookie banner requirements
A checklist, with the reasoning attached. Most banners fail on two items, and they are the same two items every time.
Applies in: EEA, with UK close behind
Setting up Google Consent Mode
One ordering mistake accounts for most broken Consent Mode implementations, and it produces a page that looks correct in every way except the one that matters.
Mechanism: Consent default and update calls
Translating a consent banner
Consent has to be informed, and information in a language someone does not read is not information. The buttons are the easy part and the least important one.
Limit: Up to 60 languages per configuration
Migrating consent platforms
The failure mode is not losing data. It is running two consent systems at once, each confidently answering the same question differently.
Risk: Two banners, two states
Start with your own site
A free scan names what is loading before anyone has chosen anything.