Cookiebot Consent Management Platform (CMP) provides a customizable WordPress cookie banner. It provides tools for collecting and managing cookie choices; installing a plugin alone does not establish legal compliance. Clear choices can help build trust with website visitors by explaining tracking and letting visitors manage their consent.
Cookiebot CMP integrates with Google Tag Manager and Google Consent Mode to communicate visitors’ consent choices to configured tags. Setup still requires appropriate default consent states and checks that tags respond correctly. Cookiebot CMP uses automated website scanning to identify cookies and tracking resources. Review scan results and classifications; a scan is not proof that every tracking method has been detected or controlled.
Cookiebot CMP and the WordPress Plugin are designed to be used by both technical and non-technical teams that value automated, scalable processes.
Features
💫 Highly customizable
Customize your WordPress cookie banner to match your user experience. Enable visitors to opt in or out of individual cookie categories.
🚀 Automated cookie scan
Use regular automated scans to keep an inventory of the cookies and tracking technologies in use on your website.
🌟 Automatically updated cookie declaration
Publish Cookiebot’s generated cookie declaration on your privacy page. It can support your disclosures, but it does not replace a complete privacy notice.
Review the generated declaration against your actual integrations and configuration, especially after changes to the website.
✅ Integration with Google Consent Mode
Cookiebot supports Google Consent Mode. Enable and configure the integration for your installation method, set appropriate default consent states and verify that consent updates reach the intended Google tags. Consent signals do not, by themselves, establish legal compliance or guarantee advertising revenue.
⚡ Automatic cookie blocking
Automatic blocking can hold back identified non-essential tracking resources until the relevant consent is given. Check script order, cookie classifications and tag-manager rules. Cookies set by the server require server-side handling.
🌎 Regulations and consent frameworks
Cookiebot provides features that can support consent management in different regions. Assess which of the following laws or frameworks applies to your activity and configure the service accordingly; a banner alone does not satisfy every obligation:
- GDPR (DSGVO, EU)
- DMA (EU)
- ePrivacy (EU)
- LGPD (Brazil)
- POPIA (South Africa)
- CCPA and CPRA (California)
- VCDPA (Virginia)
- IAB Transparency and Consent Framework (TCF)
California opt-out settings
If California sale or sharing opt-out requirements apply, provide the required opt-out method, honor applicable preference signals and ensure requests affect the relevant processing. A “Do Not Sell or Share My Personal Information” link alone is not a complete compliance setup.
🔗 Integration with website platforms
Cookiebot offers integration options for platforms such as WordPress, Shopify, Drupal and Adobe Experience Manager. Follow the instructions for your platform; see the available integrations.
🟠 Consent widget
Let visitors reopen their consent choices through Cookiebot’s widget and change or withdraw their consent.
🔒 Consent records
Cookiebot stores consent records in its service. Review the provider’s current data-processing terms, retention settings and access controls for your use case.
📥 Data download option
Use available consent records when responding to a relevant data request. A consent-record download may cover only part of the information the person is entitled to receive.
💬 Banner languages
Choose from the languages available in Cookiebot’s settings and review the wording shown to your visitors.
Google-certified CMP
Cookiebot is a Google-certified CMP. Google requires an appropriately configured certified CMP integrated with the IAB TCF for personalized ads through its publisher products in the EEA, UK and Switzerland. Certification does not establish full compliance with privacy law, and choosing a certified CMP does not replace the publisher’s configuration and consent responsibilities.
