CMPly – Cookie Consent Banner & GDPR Cookie Scanner
| 开发者 | cmplyapp |
|---|---|
| 更新时间 | 2026年8月15日 19:21 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
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.
Key Features
- Cookie Consent Banner – Display a customizable consent banner and preference center on your WordPress site.
- Automatic Cookie Scanner – Scan your website to detect cookies, trackers, and third-party services.
- Prior-Consent Blocking – Block configured non-essential scripts before the visitor gives consent.
- Google Consent Mode v2 – Configure global and regional consent defaults for Google services directly from WordPress.
- Cookie Classification – Organize detected cookies into consent categories.
- Consent Records – Keep records of visitor consent and consent changes.
- Multi-language Support – Automatically detect the visitor's language or configure it manually.
- Simple WordPress Integration – Connect your WordPress site to CMPly in just a few clicks.
- Install and activate the CMPly plugin.
- Open Settings > CMPly and connect your website to CMPly.
- CMPly scans your website for cookies and tracking technologies.
- Review detected cookies and configure your consent banner.
- Publish your configuration.
<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:
- Automatic or manual SDK embedding.
- Site ID configuration.
- SDK cache-busting version.
- Language override.
- URL exclusions with wildcard support.
安装:
- Install CMPly from the WordPress plugin directory.
- Activate the plugin.
- Go to Settings > CMPly.
- Click Connect to CMPly.
- Follow the setup process to scan your website and configure your consent banner.
- Clear your website cache if you use a caching plugin.
屏幕截图:
常见问题:
Do I need a CMPly account?
Yes. The WordPress plugin connects your website to the CMPly consent management platform. An advanced manual Site ID setup is also available.
Does CMPly scan my website for cookies?
Yes. CMPly can scan your website for cookies, trackers, and third-party services so they can be reviewed and classified.
Does CMPly block cookies before consent?
CMPly can block configured non-essential scripts until the visitor provides the required consent.
Does CMPly support Google Consent Mode v2?
Yes. Global and regional Google Consent Mode v2 settings can be configured for your connected website directly from WordPress.
Can I customize the cookie banner?
Yes. Banner appearance, content, and consent settings are managed from your CMPly account.
Does CMPly support multiple languages?
Yes. CMPly can automatically use the visitor's browser language, and a specific language can also be configured.
Why is the CMPly script not loaded with defer or async?
CMPly needs to execute early during page loading so it can prevent configured third-party scripts from running before consent. Loading it with defer or async could make prior-consent blocking less reliable.
What if I already added the CMPly script manually?
Turn off Auto-inject SDK in Settings > CMPly and keep the manual script near the top of the document head. Keep only one CMPly SDK script on the page.
How does the Connect button work?
The button opens the CMPly web app with your WordPress site URL, return URL, and a signed WordPress callback-state token that expires after 30 minutes. CMPly separately returns a ten-minute, single-use authorization code. WordPress exchanges that code with CMPly over HTTPS and stores the resulting credentials server-side.
Can I disable CMPly on specific pages?
Yes. Add one path per line in Exclude Paths, for example:
/checkout/*
Does this plugin set cookies by itself?
The WordPress plugin stores only its admin settings in the WordPress database. The public consent cookie is created by the CMPly SDK in the visitor's browser.
更新日志:
1.0.24
- Refreshed the cookie banner screenshot using the official CMPly website for consistent branding.
- Added six real product screenshots for the WordPress.org listing.
- Documented the cookie banner, WordPress connection status, consent-aware scan results, cookie classification, banner customization, and Google Consent Mode v2.
- Reworked the WordPress.org listing around the cookie consent banner, automatic cookie scanner, prior-consent blocking, and Google Consent Mode v2.
- Added clearer setup steps, feature explanations, technical integration details, and frequently asked questions.
- Updated the plugin display name and description without changing the
cmplyslug or connection behavior.
- Fixed WordPress account connections when the web callback returns without the nested WordPress nonce.
- Kept the signed, administrator-bound callback state mandatory and continued validating a WordPress nonce whenever one is returned.
- Added authenticated editing of Google Consent Mode v2 and regional consent defaults from WordPress.
- Added validation, five-minute response caching, manual refresh, and actionable connection errors for GCM settings.
- Synchronized the GitHub release source with the reviewed WordPress.org package.
- Added automated, version-validated deployment to WordPress.org.
- Clarified the connection flow by distinguishing the signed WordPress callback state from the single-use CMPly authorization code.
- Reworded upgrade messaging to avoid implying guaranteed protection from legal risk.
- Hide Reconnect while the connection is healthy and show it only after a verification failure.
- Automatically refresh plan and pageview usage when CMPly settings open and the saved snapshot is older than 15 minutes.
- Keep Verify connection as an immediate manual refresh and diagnostic action.
- Show fractional pageview usage below ten percent instead of rounding it to zero.
- Preserve freshly synchronized pageview usage, limits, and connection ID through WordPress option sanitization.
- Hide dashboard upgrade promotions for paid plans.
- Allow Verify to repair a missing connection ID using the saved API key, Site ID, and domain.
- Store the connection ID separately from editable plugin settings.
- Hide the header upgrade button for paid plans.
- Synchronize pageviews from the same billing-period statistics used by the CMPly dashboard.
- Hide the dashboard connection prompt after a CMPly account has been connected.
- Use the saved connection ID as the persistent UI connection state.
- Show the safe CMPly API error and HTTP status when credential exchange fails.
- Pass callback state as a dedicated CMPly parameter so nested URL encoding cannot remove it.
- Added precise callback-state diagnostics for missing, malformed, expired, wrong-user, and invalid-signature failures.
- Use a stateless, administrator-bound HMAC callback state that survives navigation, caching, and multiple tabs.
- Store the one-time connection state in administrator metadata so it works independently of transient cache backends.
- Replaced the external callback nonce with a one-time administrator-bound state token.
- Fixed nonce encoding in the nested WordPress connection callback URL.
- Replaced the WordPress expired-link screen with an actionable plugin error message.
- Added visible connection success and error messages.
- Distinguished manual Site ID configuration from an authenticated CMPly account connection.
- Fixed duplicate upgrade button icon during cached asset transitions.
- Fixed admin icon rendering and enabled interactive FAQ answers.
- Added live plan and pageview usage synchronization from CMPly.
- Initial release.
- Added one-time connection exchange and server-side connection verification.
- Added live plan and pageview usage synchronization from CMPly.