CookieStart – CMP Banner & Cookie Consent
| 开发者 | cookiestart |
|---|---|
| 更新时间 | 2026年9月9日 21:46 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
CookieStart is a consent management platform for WordPress websites and WooCommerce stores.
The plugin connects your website to the CookieStart service and provides access to CMP configuration directly from the WordPress administration panel. It can display the CookieStart consent banner, detect scripts and cookies, classify them into consent categories, scan website URLs, review consent history, and control script behavior before consent is granted.
Main features:
- Cookie consent banner provided by the CookieStart platform.
- CookieStart account registration directly from WordPress.
- Connection of an existing CookieStart account using an API key and domain ID.
- Website status dashboard with integration status and scan information.
- Website compliance score and audit summary.
- Manual and automatic website scans.
- Scan progress, scanned URL list, errors, and scan history.
- Detection and classification of scripts used by the website.
- Detection and classification of cookies.
- Manual category overrides for scripts and cookies.
- Consent categories: necessary, preferences, statistics, and marketing.
- Consent records and consent change history.
- Automatic processing and transformation of supported scripts.
- Optional automatic blocking of scripts before consent.
- Optional blocking of unknown scripts.
- Script allowlist and blocklist rules.
- Default category for unrecognized scripts.
- Optional grouping of first-party scripts.
- Google Consent Mode v2 support.
- Local preview of scripts detected in WordPress output.
- Runtime configuration cache management.
- Debug mode and integration logs.
- Usage statistics and scan limits available in the dashboard.
- Support for WordPress and WooCommerce websites.
安装:
- Upload the plugin folder to
/wp-content/plugins/or install the ZIP file through the WordPress Plugins screen. - Activate CookieStart through the Plugins screen in WordPress.
- Open CookieStart in the WordPress administration menu.
- Create a CookieStart account or connect an existing account.
- Add or connect the current website.
- Configure the consent banner, consent categories, script processing, and runtime settings.
- Run a website scan and review the detected scripts and cookies.
- Assign or verify the appropriate consent categories.
- Test the consent banner and blocked scripts on the frontend.
屏幕截图:
常见问题:
Do I need a CookieStart account?
Yes. The plugin connects WordPress to the external CookieStart consent management service.
Can I create an account from WordPress?
Yes. The plugin includes an account registration and website onboarding flow. Registration data is sent to the CookieStart identity service after you submit the registration form.
Can I connect an existing CookieStart account?
Yes. You can connect an existing website configuration by entering the CookieStart API key and domain ID.
Does the plugin work with WooCommerce?
Yes. CookieStart can be used on WordPress websites and WooCommerce stores.
Does the plugin block scripts before consent?
The plugin can process the generated HTML, detect supported script elements, assign consent categories, and transform selected scripts so they can be activated after the relevant consent is granted. Automatic blocking and blocking of unknown scripts can be enabled in the settings.
Can I exclude or completely block selected scripts?
Yes. The plugin provides an allowlist and a blocklist based on one pattern per line.
Does CookieStart scan my website?
A website scan can be started from the WordPress administration panel. The scan is performed by the external CookieStart crawler service. Scan availability and limits depend on the connected CookieStart plan.
Can I review detected scripts and cookies?
Yes. Detected scripts and cookies are displayed in dedicated administration views. Their consent categories can be reviewed and changed.
Can I review consent history?
Yes. The plugin displays consent records and the history of consent changes retrieved from the CookieStart service.
Does the plugin support Google Consent Mode v2?
Yes. Google Consent Mode v2 can be enabled in the CookieStart runtime settings.
Does installing CookieStart guarantee GDPR compliance?
No. CookieStart provides consent management and auditing tools, but the website owner remains responsible for configuration, legal content, cookie classification, and compliance with applicable laws.
Where can I review CookieStart's privacy policy?
更新日志:
1.1.5
- Blocked inline scripts before consent by matching the whole script family instead of a single stored example, so page-specific variants of the same tracker are held back as well.
- Recognized WooCommerce Google Listings & Ads and Meta Pixel inline script families when deciding what to block before consent.
- Limited the runtime adapter to entitlement fail-open, restoring remaining WordPress placeholders when the banner is disabled because a plan is over quota, suspended, or inactive.
- Prevented stale scan history from restarting dashboard status polling and stopped overlapping AJAX status requests.
- Synchronized script blocking and Google Consent Mode settings from the CookieStart dashboard when opening WordPress settings.
- Kept WordPress authentication sessions alive by rotating expiring tokens during the scheduled integration heartbeat.
- Retried the heartbeat once with a refreshed access token after an authorization failure before using API-key fallback.
- Reduced the size of onboarding illustrations while preserving high-density display quality.
- Separated and domain-scoped runtime settings and runtime configuration caches to prevent incompatible cached responses.
- Added direct links from the WordPress menu to the banner configuration and packages and plans for the connected domain.
- Shortened and reordered the external CookieStart panel links in the WordPress menu.
- Added a three-step onboarding guide while the first automatic website scan is running.
- Removed the duplicate plugin URI header so the author URI uniquely identifies the CookieStart website.
- Enabled CookieStart processing by default for new installations and when the setting is missing, while preserving existing disabled settings.
- Removed the WordPress plugin version query from the published domain
script.jsURL. The shared CMP IIFE keeps its own SDK version.
- Switched frontend CMP loading to the domain-specific published
script.js(Path B). - Removed the plugin-side live
CookieStart.initbootstrap; initialization now comes from the published domain artifact. - Kept existing plugin releases on the legacy Path A integration for backward compatibility.
- Removed direct inline scripts from the administration panel.
- Removed an unused output-buffer hook that could leave a buffer open.
- Clarified when CookieStart services receive data and that third-party script providers are not contacted by the plugin.
- Excluded bundled translation catalogs from the WordPress.org release package.
- Fixed deterministic SDK loading and initialization order.
- Stopped the runtime adapter from replacing the CookieStart SDK global.
- Encrypted stored access and refresh tokens with authenticated AES-256-GCM.
- Removed personal data and API payloads from diagnostic logs.
- Hardened API message rendering in the WordPress administration panel.
- Scheduled integration heartbeat only after a domain is connected.
- Prevented agreement-type requests before plugin configuration.
- Improved output-buffer ownership and uninstall cleanup.
- Updated the public plugin name to CookieStart – CMP Banner & Cookie Consent.
- Disabled frontend SDK loading until the plugin is explicitly enabled and fully configured.
- Removed the insecure encryption-key fallback and added authenticated AES-256-GCM storage with legacy-data migration.
- Added complete English source strings and a Polish translation catalog.
- Improved banner language selection using the current WordPress locale.
- Reworded audit results as a technical CMP assessment and added a clear legal-compliance disclaimer.
- Improved account connection messages and clarified that passwords are used only for the current request.
- Removed persistent storage of the CookieStart account password.
- Added session renewal through the rotating Identity refresh-token endpoint.
- Added one-time external login codes so authentication tokens are no longer placed in panel URLs.
- Added cleanup of passwords stored by earlier plugin versions.
- Added CookieStart account registration and login from WordPress.
- Added automatic website creation and connection flow.
- Added website scanning, scan progress, scan limits, and scan result views.
- Added compliance dashboard and audit summary.
- Added script and cookie category management.
- Added consent records and consent history views.
- Added runtime settings, script allowlist and blocklist, debug mode, and integration heartbeat.
- Added Google Consent Mode v2 support.
- Improved automatic script detection, transformation, and blocking.
- Improved WordPress.org validation compatibility.