| 开发者 | optsens |
|---|---|
| 更新时间 | 2026年9月26日 06:18 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Sign up at my.optsens.com, add your domain, then copy the Domain ID from the integration screen. Detailed steps: docs.optsens.com.
Yes. When the WP Consent API plugin is active, OptSens passes each visitor's choice to it: functional to preferences, analytics to statistics, analytics or performance to anonymous statistics, and advertising to marketing. Plugins that read the API follow the banner. Until the visitor chooses, the API reports no consent. For Site Kit by Google, turn on Consent Mode in Site Kit's settings; OptSens then keeps Site Kit's consent updates in line with its own Google Consent Mode signals.
The OptSens script sets two cookies after a visitor accepts or rejects the banner: os_consent (consent preferences, 180 day default lifetime) and euconsent-v2 (IAB Transparency and Consent string, 13 month lifetime). No cookies are set before the visitor interacts with the banner. Third-party tracking cookies are blocked until consent is given.
Yes. All seven consent types (ad_storage, analytics_storage, ad_user_data, ad_personalization, personalization_storage, functionality_storage, security_storage) with denied defaults.
Yes. The Domain ID is per-site, so each site in a network needs its own ID and its own activation.
Yes, but customization happens in your OptSens dashboard, not in this plugin. The plugin only injects the script tag and reads configuration from your account.
The script tag is still injected but the consent banner returns an inactive state. Visitors see no banner. Reactivate your account to resume.