A cookie banner asks visitors which website tools they want to allow. The next job is making those choices work. Here is what to set up, test and keep up to date.
Three parts to check
The notice explains the choices. The integration controls connected tools. The record shows what choice was saved. A screenshot of the notice checks only the first part.
Start by listing your tools and their owners. Decide which category each belongs to. Keep optional tools from starting before the required choice in an opt-in setup. Follow each tool's documentation as well as your banner setup.
Pick a plan by workload
For ConsentPop, Free includes one site and 5,000 monthly widget loads, with choices and records. Paid plans add capacity, settings, or more sites. Compare your expected usage and client workload on the pricing page.
A free library may fit a site whose developer wants to manage the integration directly. For example, CookieConsent documents script management. Hosted settings are a management choice, not proof that a free tool cannot support consent.
Test the whole journey
Use the audit checklist. Check no choice, reject, partial choice, accept, reload, and withdrawal. Test desktop, mobile, and keyboard use. Keep your test date and actual observations.
Maintain the setup
Recheck after adding a tag, replacing a plugin, or changing relevant categories and services. Make your privacy information match the tools in use. Background verification has coverage and quota limits; it is not a promise that every new tool is connected automatically.
For several client sites, see the freelancer workflow.