{"id":243575,"date":"2025-07-29T07:54:03","date_gmt":"2025-07-29T07:54:03","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/cheq-enforce\/"},"modified":"2026-08-20T13:02:05","modified_gmt":"2026-08-20T13:02:05","slug":"cheq-enforce","status":"publish","type":"plugin","link":"https:\/\/ar.wordpress.org\/plugins\/cheq-enforce\/","author":23334089,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.2.0","stable_tag":"1.2.0","tested":"7.1","requires":"5.0","requires_php":"7.2","requires_plugins":null,"header_name":"CHEQ Enforce","header_author":"CHEQ","header_description":"Auto-block unauthorized tracking, protect data, give legal, compliance & martech teams control to meet global privacy laws without delay.","assets_banners_color":"7c6f85","last_updated":"2026-08-20 13:02:05","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/cheq.ai\/enforce\/","header_author_uri":"https:\/\/cheq.ai\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":574,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"cheqadurgavich","date":"2025-07-29 07:57:06"},"1.1.0":{"tag":"1.1.0","author":"cheqadurgavich","date":"2026-05-18 15:53:22"},"1.2.0":{"tag":"1.2.0","author":"cheqadurgavich","date":"2026-08-20 13:02:05"}},"upgrade_notice":{"1.2.0":"<p>This release reports visitor consent to the WP Consent API correctly for the first time. Plugins that read the API, including Google Site Kit, will now honor the visitor&#039;s choice where previously they were told no consent manager was present and could track regardless. After updating, check the Consent Category Mapping on the CHEQ Enforce settings screen against the category names in your CHEQ account.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3335735,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":3335735,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0","1.2.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[245528,245529,20278,27218,125671],"plugin_category":[],"plugin_contributors":[245530],"plugin_business_model":[],"class_list":["post-243575","plugin","type-plugin","status-publish","hentry","plugin_tags-cheq","plugin_tags-consent-management-platform","plugin_tags-cookie-compliance","plugin_tags-enforce","plugin_tags-ensighten","plugin_contributors-cheqadurgavich","plugin_committers-cheqadurgavich"],"banners":{"banner":"https:\/\/ps.w.org\/cheq-enforce\/assets\/banner-772x250.png?rev=3335735","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/cheq-enforce\/assets\/icon-128x128.png?rev=3335735","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Use this lightweight WordPress plugin to add <a href=\"https:\/\/cheq.ai\/enforce\/\">CHEQ Enforce<\/a> to your website. The plugin will inject the CHEQ Enforce library script into your site's <code>&lt;head&gt;<\/code> tag after configuring the domain, account, and path settings that can be found in your CHEQ Enforce account. Once installed and configured, CHEQ Enforce can serve a customized consent experience and automatically enforce your website visitor's consent.<\/p>\n\n<h3>Configuration<\/h3>\n\n<ol>\n<li>In the WP Admin, open <strong>CHEQ Enforce<\/strong> in the sidebar.<\/li>\n<li>Enter:\n\n<ul>\n<li><strong>Domain<\/strong>: e.g. <code>nexus.ensighten.com<\/code><\/li>\n<li><strong>Account<\/strong>: your CHEQ Enforce account name<\/li>\n<li><strong>Publish Path<\/strong>: the path segment under your account<\/li>\n<\/ul><\/li>\n<li>Under <strong>Consent Category Mapping<\/strong>, enter the matching consent category name from your CHEQ account beside each WP Consent API category. The five WP categories are fixed and cannot be edited; each one takes a single CHEQ category name. Names must match exactly, including capitalization. The same CHEQ category may be entered in more than one row, and its consent then applies to each \u2014 entering Analytics against both statistics and statistics-anonymous, for example. A row left blank is treated as not consented by plugins that read the WP Consent API.<\/li>\n<li>Click <strong>Save Changes<\/strong>.<\/li>\n<\/ol>\n\n<p>The Consent Category Mapping only affects plugins that read the WP Consent API, such as Google Site Kit. It does not change what CHEQ Enforce itself blocks.<\/p>\n\n<p>The plugin will then output:\n    <code>&lt;script src=\"https:\/\/&lt;domain&gt;\/&lt;account&gt;\/&lt;publish_path&gt;\/Bootstrap.js\"&gt;&lt;\/script&gt;<\/code>\nat the very top of your site's <code>&lt;head&gt;<\/code>.<\/p>\n\n<h3>About<\/h3>\n\n<p>As the global leader in Go-to-Market Security, 15,000+ companies \u2014 from emerging brands to Fortune 50 \u2014 trust CHEQ to protect business-critical digital engagement from human, agent, and machine-driven threats.<\/p>\n\n<p>Powered by our unrivaled, context-specific detection engine, CHEQ safeguards companies against threats to business continuity, brand reputation, privacy compliance, and marketing effectiveness \u2014 all without compromising customer experience.<\/p>\n\n<p>https:\/\/cheq.ai\/cheq-terms-of-service\/<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the entire <code>cheq-enforce<\/code> directory to:\n   <code>wp-content\/plugins\/cheq-enforce\/<\/code><\/li>\n<li>Activate the plugin via <strong>Plugins \u2192 Installed Plugins<\/strong>.<\/li>\n<\/ol>\n\n<!--section=changelog-->\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>Fixed the WP Consent API integration: a JavaScript error stopped consent changes from being forwarded, so visitor choices were never applied.<\/li>\n<li>CHEQ Enforce now tells the WP Consent API that consent is required before a category becomes active. Previously it registered as a consent manager but never declared this, so other plugins were told no consent manager was present and could track regardless of the visitor's choice.<\/li>\n<li>Consent categories are now mapped to the WP Consent API on the settings screen, so accounts that use their own category names are recognized. Accounts naming a category Advertising, for example, were ignored before, so consent for it was never applied. A single CHEQ category can be mapped to more than one WP Consent API category.<\/li>\n<li>A returning visitor's existing consent is now applied when the page loads, rather than only after they change it.<\/li>\n<li>Consent recorded before the WP Consent API finishes loading is now applied once it is ready, instead of being discarded.<\/li>\n<li>Fixed consent being recorded incorrectly when a consent payload arrived in an unexpected format, and stopped one bad entry from discarding the remaining categories.<\/li>\n<li>The plugin now stays inactive until an account and publish path are set, instead of loading a broken script and removing Google Site Kit's consent defaults with nothing to replace them. An admin notice explains what to configure.<\/li>\n<li>Fixed clearing the Domain field leaving the plugin active with an unusable script URL; the default domain is now restored automatically.<\/li>\n<li>Site Kit's consent default is now replaced only inside Site Kit's own snippet, leaving consent code added by other plugins or your theme untouched.<\/li>\n<li>Fixed the settings screen mangling domain, account, and publish path values containing &amp;, &lt;, or quotes each time they were saved.<\/li>\n<li>Made output buffering safer alongside caching and optimization plugins, and it no longer risks emptying the page head.<\/li>\n<li>The consent integration code is minified before it is added to the page.<\/li>\n<li>Corrected the setup instructions: the settings screen is the top-level CHEQ Enforce menu item, not under Settings.<\/li>\n<li>Tested with WordPress 7.1.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Added an integration with WP Consent API.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release.<\/li>\n<\/ul>","raw_excerpt":"Auto-block unauthorized tracking, protect data, give legal, compliance &amp; martech teams control to meet global privacy laws without delay.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/243575","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=243575"}],"author":[{"embeddable":true,"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/cheqadurgavich"}],"wp:attachment":[{"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=243575"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=243575"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=243575"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=243575"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=243575"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ar.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=243575"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}