WordPress
Connect the official plugin and verify your published site.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Official plugin connection
- Download the ConsentEase plugin.
- In WordPress, choose Plugins → Add New Plugin → Upload Plugin, upload the ZIP, install and activate.
- Open Settings → ConsentEase → Connect to ConsentEase.
- Sign in and confirm the correct website in the guided connection flow, then return to WordPress.
Use a publicly reachable HTTPS website and an administrator account with permission to install plugins. Check the plugin's included readme for its current WordPress/PHP requirements; do not bypass its compatibility checks.
What the connection does
WordPress receives the selected website's public banner installation, not access to your whole ConsentEase account. Banner design, inventory and records stay in the ConsentEase dashboard. Run the plugin's installation checks for script reachability, duplicate loaders and competing consent plugins.
Caching and script ordering
Clear page/plugin/CDN caches after installation or changes. Delay-JavaScript and optimisation tools can reorder initialization; verify consent defaults actually precede the tags they govern. The plugin cannot guarantee ordering against every theme or optimisation plugin.
Alternative: manual header installation
If you cannot use the official plugin, paste the complete dashboard snippet as the first item of a site-wide header tool, above Google Tag Manager and other trackers, and exclude it from delay-JavaScript and combine/defer settings. Do not combine this with the connected plugin or a GTM loader.
Disconnect and migrate
Deactivation keeps the connection; deleting the plugin removes it. Disconnect from WordPress or the ConsentEase dashboard when needed. Verify the replacement method before removing a working setup; disconnecting does not erase all browser cookies or your historical consent evidence.
WooCommerce and page-builder surfaces still need purpose-based cookie review and checks of checkout/payment/embedded tracking.
Verify the published site
Use separate fresh browser contexts for no choice, accept, reject and custom preferences. Check tag consent requirements, network traffic, storage and reopening preferences. Test relevant routes and mobile layouts. A theme installation does not prove coverage of checkout, embedded frames or hosted third-party pages.