Your cookie policy explains what your website uses. Your banner lets visitors choose. Start with a short, clear notice, then check that your website tools follow the choice.
Start with the tools on your site
List analytics, advertising, chat, video, and other embeds. Note which team owns each one. Check your page source and tag manager as well as your website settings. A script can be added in more than one place.
For each tool, record its purpose, the cookie group it belongs to, and how it receives consent. Updating banner text does not connect an unconfigured script.
Write a notice people can use
Explain the purpose of each optional group in plain words. Link to your current cookie policy. Use clear button labels, such as Accept all, Reject all, and Manage preferences. Avoid making a technical test sound like a legal guarantee.
Your policy should reflect the tools you actually use. Check vendor documentation and the rules that apply to your business before publishing legal text.
Connect the choice to the tool
Install ConsentPop using the code from your dashboard. Then follow the setup guide for optional scripts. Keep optional scripts from running until the choice allows them. If another plugin injects the same tag, remove that duplicate source or configure its consent behavior too.
Check the result
Open browser developer tools and watch network requests. Test a new visit, rejection, a partial choice, acceptance, reload, and withdrawal. Confirm that the policy link works and a visitor can reopen preferences. Keep the tested URL, date, and observed result.
A saved choice is not a complete historical copy of the notice someone saw. Describe your records according to what you actually retain.
Use the cookie consent audit for the full checklist.