| 开发者 |
clearconsent
coreconsent |
|---|---|
| 更新时间 | 2026年7月20日 23:34 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
coreconsent folder to /wp-content/plugins/, or install through Plugins → Add New.No plugin can do that on its own. CoreConsent gives you the controls — a consent banner, consent-gated script loading, and Google Consent Mode signals — but how you configure them, and what your legal obligations are, is up to you. If you're unsure, talk to someone qualified in privacy law for your situation.
Add it the supported way so CoreConsent controls it: configure it as a service in Settings → CoreConsent, or tag the script with type="text/plain" and a data-cc-name attribute. CoreConsent then loads it only after the visitor consents. If you paste a gtag snippet directly high in your theme's <head>, it can run before the consent default is set — so add it through the normal method, or place it after CoreConsent's output. Pro's scanning and Script Manager handle this for you.
Yes, in the free version. CoreConsent sets all v2 consent signals to denied by default and updates them when the visitor makes a choice. Google tags load after consent (consent-gated mode).
Yes. Consent is applied in the visitor's browser, and the page HTML is the same for everyone, so your pages cache normally. After you change which services are blocked, clear your page cache so the change takes effect right away.
It's designed not to. The banner is lightweight vanilla JavaScript, and because it's caching-friendly it doesn't force your pages to load uncached.
Network-wide scanning and pushing settings across subsites is part of CoreConsent Agency.