Integrate NexaGuard CMP with WordPress

Last updated: February 21, 2026

This page documents the current WordPress plugin behavior for nexaguard-cmp (stable 0.2.1), aligned with the production CMP engine.

1. Overview

NexaGuard CMP for WordPress provides:

automatic loader integration through WordPress script APIs

optional Google Consent Mode v2 defaulting in <head>

WP Consent API bridge for ecosystem interoperability

admin debug/reset tools for QA validation

2. Plugin Details

Property	Value
Plugin Name	NexaGuard CMP
Slug	`nexaguard-cmp`
Stable tag	`0.2.1`
Requires WordPress	`5.8+`
Tested up to	`6.8`
Requires PHP	`7.4+`
Listing	wordpress.org/plugins/nexaguard-cmp

3. Install

Option A - WordPress Admin

Go to Plugins -> Add New.

Search NexaGuard CMP.

Install and activate.

Option B - ZIP Upload

Download plugin ZIP.

Go to Plugins -> Add New -> Upload Plugin.

Upload, install, and activate.

4. Configure (Admin)

Open NexaGuard CMP in WP admin and set:

App ID (settings-id) (required)

Auto-inject CMP Script (recommended ON)

Enable Google Consent Mode v2 (ON to inject consent default head stub)

Debug Mode (temporary QA mode)

Consent Model (WP Consent API):

optin (EU-style default)

optout (US-style default)

Notes:

assets_url and api_url are fixed by plugin runtime and not user-editable.

the old admin warning about installing WP Consent API was intentionally removed for cleaner UX.

5. Runtime Loading Order

When enabled, plugin behavior is:

<head> (early): Consent Mode stub initializes dataLayer/gtag, sets developer_id.<id>, and pushes one guarded gtag('consent','default', denied...).

Footer: wp-consent-bridge.js enqueues first.

Footer: CMP loader (loader.js) enqueues after bridge and receives attributes (including id="nexaguard-cmp" and data-settings-id).

Example generated loader tag shape:

If Enable Google Consent Mode v2 is OFF, head stub is skipped and loader receives data-consent-mode="off".

The bridge exposes:

window.NXG_WPConsentAPI.set(category, value)

window.NXG_WPConsentAPI.setAll(map)

window.NXG_WPConsentAPI.acceptAll()

window.NXG_WPConsentAPI.rejectAll()

It also listens for:

nexaguard:consent (bulk map)

nexaguard:consent:category (single category)

Canonical categories:

functional

preferences

statistics

statistics-anonymous

marketing

Default GCM-to-WP mapping:

analytics_storage -> statistics

ad_storage -> marketing

ad_user_data -> marketing

ad_personalization -> marketing

7. Shortcodes and Block

[nexaguard_cmp] -> ensures loader enqueue

[nexaguard_preferences] -> renders privacy settings link

Gutenberg block cmp-block -> server-rendered loader enqueue path

8. Verification Checklist (Console)

Run on a front-end page:

After Accept All:

After Reject All:

Last Consent Mode update:

Expected:

one consent default call on load (when consent mode enabled)

category updates reflected via wp_has_consent(...)

GCM update reflects current vendor/purpose selection logic

9. Troubleshooting Highlights

Issue	Likely cause	Fix
Banner not visible	missing App ID or caching	set App ID, reset consent, purge cache/CDN
Duplicate banner	manual loader + plugin both active	keep a single integration path
WP categories not updating	bridge/API not available	check `typeof NXG_WPConsentAPI` and ensure WP Consent API functions are present
No Consent Mode default	option disabled or script ordering conflict	enable `Enable Google Consent Mode v2` and verify head output

10. Uninstall

On delete, plugin removes nexaguard_cmp_options (single-site or multisite per site).

Web Setup

Google Consent Mode v2 Validation

IAB TCF v2.3 Support

Troubleshooting Playbook

Integrate NexaGuard CMP with WordPress

1. Overview#

2. Plugin Details#

3. Install#

Option A - WordPress Admin#

Option B - ZIP Upload#

4. Configure (Admin)#

5. Runtime Loading Order#

6. WP Consent API Bridge#

7. Shortcodes and Block#

8. Verification Checklist (Console)#

9. Troubleshooting Highlights#

10. Uninstall#

11. Related Docs#