cookielex

CookieLex is a consent management platform for websites that need a configurable cookie banner and related privacy tools.
This plugin connects a WordPress site to a CookieLex account or CookieLex site key. After the site is connected, the plugin loads the CookieLex CMP script on public WordPress pages so the CookieLex banner can display and use the banner configuration from your CookieLex dashboard.
Depending on your CookieLex account and site configuration, CookieLex can help you manage consent choices, cookie categories, consent logging, cookie scanning, and privacy or cookie policy tools. Configuration is managed in CookieLex, not primarily inside WordPress.
Website owners remain responsible for configuring CookieLex appropriately for their site, jurisdiction, installed scripts, policies, and legal obligations. This plugin and the CookieLex service can support privacy compliance workflows, but they do not guarantee compliance with GDPR, ePrivacy, CCPA/CPRA, or any other law.
<h3>External services</h3>
This plugin connects to CookieLex services so it can connect your WordPress site to CookieLex, load the hosted consent banner, and synchronize the site connection.
This service is provided by CookieLex.
Website: https://cookielex.com/
Terms and conditions: https://app.cookielex.com/terms-and-conditions
Privacy policy: https://app.cookielex.com/privacy-policy
Production service domain used by the plugin: https://app.cookielex.com/
The plugin makes these external requests:
<ul>
<li>When an administrator clicks “Connect to CookieLex”, WordPress redirects the administrator to <code>https://app.cookielex.com/integrations/wordpress/connect</code>.</li>
<li>The connect request includes the WordPress callback URL, site URL, a temporary state value, plugin version, and WordPress version.</li>
<li>When CookieLex redirects back to WordPress with a connection token, the plugin sends that token to <code>https://app.cookielex.com/api/integrations/wordpress/exchange</code>.</li>
<li>After a successful connection, the plugin stores a heartbeat token in the WordPress option <code>cookielexccpc_heartbeat_token</code> and sends a daily WP-Cron heartbeat to <code>https://app.cookielex.com/api/integrations/wordpress/heartbeat</code>.</li>
<li>When a site key is saved or returned by the connection flow, the public site loads the CookieLex CMP script from the configured embed URL. By default this is <code>https://app.cookielex.com/cmp/embed/{site_key}</code>.</li>
</ul>
Data sent to CookieLex by this plugin may include:
<ul>
<li>Site key.</li>
<li>Site URL or domain.</li>
<li>WordPress version.</li>
<li>Plugin version.</li>
<li>Temporary connection state and connection token during the administrator connect flow.</li>
<li>Heartbeat token during the daily heartbeat request. The token is sent in a POST JSON request body and is used only to authenticate the plugin installation status.</li>
<li>Connection metadata returned by CookieLex, such as embed URL, dashboard URL, domain, and connection time, which is stored in the WordPress option <code>cookielexccpc_settings</code>.</li>
<li>Daily heartbeat metadata, including site key, plugin version, WordPress version, and site/domain information. This is used to show whether the WordPress plugin is actively installed and recently seen in CookieLex.</li>
</ul>
The frontend CookieLex CMP script is loaded by visitors’ browsers from CookieLex servers. That browser request includes normal web request data, such as IP address and user agent, as part of the request to CookieLex. The CMP script may process visitor consent choices according to your CookieLex account and banner configuration.
This plugin does not send raw WordPress administrator passwords to CookieLex. The WordPress admin screen masks the stored site key and does not print raw connection or heartbeat tokens.
CookieLex provides this service under its terms and conditions at https://app.cookielex.com/terms-and-conditions and privacy policy at https://app.cookielex.com/privacy-policy.
<h3>Data storage</h3>
The plugin stores only the integration settings needed to connect WordPress to CookieLex.
Data stored in WordPress options may include:
<ul>
<li><code>cookielexccpc_settings</code>: site key, embed URL, dashboard URL, connected domain, connection time, heartbeat URL, and last heartbeat time.</li>
<li><code>cookielexccpc_heartbeat_token</code>: heartbeat token returned by CookieLex after the site is connected.</li>
</ul>
The plugin also stores a temporary connection state in the transient <code>cookielexccpc_connect_state</code> during the administrator connect flow. This transient expires after 10 minutes.
When the site is disconnected from the CookieLex admin page, the plugin removes the stored CookieLex settings, heartbeat token, and scheduled heartbeat event. When the plugin is uninstalled, <code>uninstall.php</code> removes the same stored options, scheduled event, and temporary connection transient.

CookieLex Cookie Consent & Privacy Compliance

Add the CookieLex consent banner to WordPress and connect your site to CookieLex.

wpTruss Plugins

Truss Consent Manager is a full consent management plugin for WordPress and WooCommerce. It goes beyond a simple cookie banner to actively detect, categorise, and block tracking scripts until your visitors give consent.
Core Features
<ul>
<li>Three banner layouts — Cookie Bar (full-width), Card (corner), Floating Box (centred)</li>
<li>Simple and granular consent modes — Accept All / Decline, or per-category toggles (Analytics, Marketing, Functional)</li>
<li>Script Scanner — automatically detects tracking scripts on your site by scanning real frontend output. Identifies 14 known trackers including Google Analytics, Google Tag Manager, Meta Pixel, TikTok Pixel, Microsoft Clarity, Hotjar, Matomo, and more.</li>
<li>Script Blocking Engine — prevents detected scripts from loading before consent is given. Rewrites script tags to <code>type="text/plain"</code> and re-activates them after consent.</li>
<li>Google Consent Mode v2 — injects the required <code>gtag consent default</code> call before any Google scripts load, then updates consent signals automatically when visitors accept or decline.</li>
<li>Smart toggle visibility — granular toggles only appear for categories where trackers were actually detected on your site.</li>
<li>Fully customisable — banner colours, button labels, privacy policy link, cookie expiry, card position.</li>
<li>Developer API — <code>wpcm_register_script( $handle, $category )</code> for manual script registration.</li>
</ul>
Google Consent Mode v2 — Signal Mapping
When Google Consent Mode is enabled (default), the plugin injects a denied default state before any Google scripts load and updates the following signals based on visitor consent:
<ul>
<li>Analytics consent → <code>analytics_storage</code></li>
<li>Marketing consent → <code>ad_storage</code>, <code>ad_user_data</code>, <code>ad_personalization</code></li>
<li>Functional consent → <code>functionality_storage</code>, <code>personalization_storage</code></li>
</ul>
This works automatically with Google Analytics 4, Google Ads, and Google Tag Manager.
Privacy-first design
Consent is stored in a first-party browser cookie (<code>wpcm_consent</code>). No consent data is sent to any external server by this plugin. The Script Blocking Engine runs entirely server-side and client-side — no cloud dependency.
<h3>External Services</h3>
This plugin integrates with the following external services when Google Consent Mode v2 is enabled:
Google Consent Mode / Google Tag Manager / Google Analytics 
When Google Consent Mode is enabled (Settings → Advanced → Google Consent Mode v2), this plugin injects JavaScript that communicates with Google’s <code>dataLayer</code> and <code>gtag()</code> API. This sends consent signals to Google when a visitor interacts with the consent banner.
<ul>
<li>What is sent: consent grant/deny signals (no personal data, no IP address, no identifiers)</li>
<li>When it is sent: when a visitor accepts, declines, or saves preferences; and on every page load for return visitors (to re-apply stored consent)</li>
<li>Google Privacy Policy: https://policies.google.com/privacy</li>
<li>Google Terms of Service: https://policies.google.com/terms</li>
</ul>
If you disable Google Consent Mode in the plugin settings, no data is sent to Google by this plugin (though your own Google Analytics / GTM setup may still send data independently).

Truss Consent Manager

Cookie consent banner with script detection, script blocking, and Google Consent Mode v2 — built for WooCommerce stores.

CookieLex Cookie Consent & Privacy Compliance vs Truss Consent Manager