Description
OptSens is a Consent Management Platform (CMP) that helps make your website compliant with GDPR, ePrivacy, CCPA, CPRA, ZZPL (Serbia), FADP (Switzerland) and other global privacy regulations.
This plugin is a connector to the OptSens cloud service. To use it you need an OptSens account at my.optsens.com. OptSens is a paid service with multiple plan tiers (Essential, Plus, Pro, Business). The plugin itself is free and open source.
Features
- IAB TCF 2.3 certified consent framework
- Google Consent Mode v2 (all seven consent types)
- CCPA / CPRA opt-out with Do Not Sell link
- GPP (Global Privacy Platform) support
- Automatic script and cookie blocking
- 52 banner languages with auto-detection
- Geo-targeting per region
- WordPress Consent API integration
Account required
This plugin requires an OptSens account. Sign up at my.optsens.com, add your domain to receive a Domain ID, then enter that ID in the plugin settings page. Plan details are shown in your OptSens account.
External services
This plugin connects to two OptSens services to deliver the consent management experience.
cdn.optsens.com
The plugin loads the OptSens consent management script from this CDN on every public page of your site. The script is loaded as <script src="https://cdn.optsens.com/optsens.min.js/YOUR_SITE_ID">. Each visitor’s browser fetches the script and sends its own IP and User-Agent header to the CDN as part of the normal HTTP request. The CDN does not log or store these headers beyond standard CDN cache metrics.
Data sent: visitor IP address, User-Agent (standard HTTP request headers only)
Trigger: every public page load when a Domain ID is configured
Privacy policy: https://optsens.com/privacy-policy
api.optsens.com
When you save your Domain ID in the plugin settings, the plugin sends one HTTPS request to validate that the ID is real and that the WordPress site hostname matches the domain registered to that ID. No visitor data is sent. The request is made only from the WordPress admin screen, never from public pages.
Data sent: Domain ID, hashed WordPress site hostname (first 16 chars of SHA-256)
Trigger: when an admin saves the settings, plus a 5-minute cached re-check on settings page render
Privacy policy: https://optsens.com/privacy-policy
Privacy
The plugin itself does not collect or store user data on your WordPress server beyond a single option (optsens_site_id) and short-lived validation cache transients. All consent records are stored in the OptSens cloud, scoped to your account. Visitors interact directly with the OptSens script; their consent choices, anonymized analytics, and IP-derived geo region are processed by the OptSens service under the OptSens Privacy Policy linked above.
For OptSens as a data processor under GDPR, request a Data Processing Agreement from your account contact at OptSens.
Screenshots




Installation
- Install the plugin via WordPress admin (Plugins, Add New, Upload Plugin) or upload the folder to /wp-content/plugins/
- Activate the plugin from the Plugins screen
- Go to OptSens in the admin sidebar
- Enter your Domain ID and click Connect website
- The consent banner appears on your site automatically
FAQ
-
Where do I get a Domain ID?
-
Sign up at my.optsens.com, add your domain, then copy the Domain ID from the integration screen. Detailed steps: docs.optsens.com.
-
Does it work with the WP Consent API and Site Kit?
-
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) andeuconsent-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. -
Is Google Consent Mode v2 supported?
-
Yes. All seven consent types (ad_storage, analytics_storage, ad_user_data, ad_personalization, personalization_storage, functionality_storage, security_storage) with denied defaults.
-
Does the plugin work on multisite?
-
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.
-
What happens if my OptSens account is suspended?
-
The script tag is still injected but the consent banner returns an inactive state. Visitors see no banner. Reactivate your account to resume.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“OptSens | Cookie Consent Platform for GDPR & CCPA” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “OptSens | Cookie Consent Platform for GDPR & CCPA” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.1
- WP Consent API integration: visitor choices are passed to the API, so Site Kit and other supporting plugins follow the banner.
1.0.0
- Initial release.
