

CMPly cookie consent banner displayed on the official CMPly website.
CMPly is a cookie consent and consent management plugin for WordPress that helps you manage cookies, trackers, and visitor consent.
Automatically scan your website for cookies and tracking technologies, display a customizable cookie consent banner, block non-essential scripts before consent, and manage consent from your CMPly dashboard.
This plugin requires an active CMPly.app site configuration. CMPly provides the consent banner, consent storage, cookie/provider metadata, and related consent-management functionality.
CMPly automatically loads the required consent management configuration on your WordPress website.
CMPly scans your website to identify cookies, trackers, and third-party services.
Detected technologies can be reviewed and classified from your CMPly dashboard, helping you keep your cookie configuration up to date as your website changes.
CMPly supports Google Consent Mode v2 and allows you to configure consent defaults for Google services.
You can manage global and regional consent settings directly from the CMPly settings inside WordPress.
CMPly loads its SDK early in the page <head> so that configured third-party scripts can be controlled before they execute.
The SDK is intentionally loaded without defer or async, because delayed execution could allow tracking scripts to run before the visitor’s consent preferences are known.
Advanced options include:
This plugin connects to CMPly.app, a third-party consent-management service, when CMPly is enabled and a Site ID is configured.
When an administrator chooses Connect or Verify, WordPress sends the site URL, connection identifiers, plugin version, and a short-lived connection code to CMPly. CMPly returns the Site ID and API key server-to-server. When an administrator opens, refreshes, or saves the Google Consent Mode screen, WordPress sends the site URL, Site ID, connection ID, API key, and GCM settings to CMPly. GCM responses are cached in WordPress for five minutes. The API key is stored as a non-autoloaded WordPress option, is never printed in public HTML, and is deleted on disconnect or uninstall.
The administrator-side connection and GCM requests use CMPly endpoints under https://cmply.app/api/integrations/wordpress/, including /sites/{siteId}/gcm. These requests are used only to authenticate the WordPress connection and read or save the connected site’s settings.
The plugin loads the CMPly JavaScript SDK from:
https://cmply.app/sdk/init.jsThe SDK may request these CMPly API endpoints in the visitor’s browser:
/api/sites/{siteId} to load banner settings./api/sites/{siteId}/cookies-list to load cookie details./api/sites/{siteId}/providers to load detected provider rules./api/sites/{siteId}/view to record a banner/site view./api/consent to record a consent choice.Data sent to CMPly may include the configured Site ID, consent categories selected by the visitor, consent metadata generated by the SDK, and standard request metadata such as IP address, user agent, referrer, and timestamp. CMPly uses this data to provide cookie consent functionality, consent records, analytics, and script-blocking configuration.
Service links: