Consently – Cookie Consent & Compliance

Consently is a powerful Consent Management Platform (CMP) that helps you comply with GDPR, CCPA, ePrivacy, and IAB TCF v2.3 regulations. This plugin connects your WordPress site to your Consently account to display a fully customizable cookie consent banner.

Key Features

• Account Connection – Link your WordPress site to a Consently account with a single API key
• Banner Injection – Injects the Consently consent banner before all other scripts for proper compliance
• Google Consent Mode v2 – Sets deny-all defaults before any Google tag, then updates on consent
• Cache Plugin Compatibility – Auto-configures WP Rocket, LiteSpeed, W3 Total Cache, Autoptimize, SG Optimizer, and WP Super Cache
• WP Consent API Bridge – Broadcasts consent signals to compatible WordPress plugins
• Cookie Scanner – Combines remote browser scan with local WordPress analysis for comprehensive cookie detection
• Settings – Local settings plus read-only view of your Consently configuration
• Diagnostics – Full system status view for troubleshooting
• WP Site Health Integration – Adds Consently checks to WordPress’s built-in health tool
• Multisite Support – Network activation with per-subsite configuration

How It Works

1. Sign up at consently.net and get your API key
2. Install this plugin on your WordPress site
3. Enter your API key and click Connect
4. Your site is automatically registered and the consent banner goes live immediately

External services

This plugin connects to the Consently consent management platform (consently.net) to provide its functionality. It is required for the plugin to work, since the consent banner, cookie database, and compliance configuration are managed in your Consently account.

1. Consently API – api.consently.net

All API calls authenticate with the API key you enter and are made from the WordPress admin only. Almost all are triggered by an explicit action of yours; the one exception is the site address registration described below, which runs automatically when your site address changes. No API calls are made on plugin activation or on front-end page loads.

• POST /api/wp/connect – Triggered when you click “Connect”. Sends your site URL, site name, WordPress version, and the plugin version to register the site.
• GET /api/wp/site-config/{site_id} – Triggered when you connect or refresh configuration. Sends the site ID; retrieves your banner ID and script-blocking configuration.
• POST /api/wp/domains – Sends the site ID and your current site address so consent can be recorded from it. Triggered when you click “Sync Now”, and automatically (once per change) when your site address differs from the one already registered — for example when you point a custom domain at a site first created on a hosting provider’s subdomain.
• POST /api/v1/scans – Triggered when you start a cookie scan. Sends the website ID and the page URLs to scan.
• GET /api/v1/scans/{id} – Triggered while a scan is running, to poll its status. Sends the scan ID.
• POST and GET /api/v1/websites/{id}/cookies – Triggered when you sync scan results. Sends and retrieves cookie records (name, domain, category, etc.).

2. Consently CDN – app.consently.net

The consent banner JavaScript (app.consently.net/consently.js) is loaded on your site’s front-end pages so visitors can see and interact with the consent banner. Only your banner ID is passed, via a data attribute on the script tag.

By using this plugin, you agree to Consently’s Terms of Service and Privacy Policy.

Local scanner reference data (not an external service): The cookie scanner ships a bundled, local data file (includes/data/tracker-domains.json) listing known tracker domain names. It is used only to classify scripts and cookies already present on your own site, by string matching against those names. The plugin does not contact, load files from, or send data to any of those domains — they are reference data only. api.consently.net and app.consently.net above are the only external services the plugin actually connects to.