Consent-Aware Domain Analytics

1. 1

   Back up your WordPress database and installed plugin files. Keep the previous ZIP and test restoration before changing a live shop.

2. 2

   In the Novelience customer area, open Mes produits et licences (My products and licences). Download consent-aware-domain-analytics-1.2.1.zip (version 1.2.1) and compare its SHA-256 with the product page: f6702b50712071e3e06911d015c2df6f64e28917e58cf2648e153d2deb12069c.

3. 3

   In WordPress, open Plugins › Add New › Upload Plugin, select the ZIP, and activate it. For an update, choose to replace the existing plugin in place; do not uninstall the old version first.

4. 4

   Check existing settings and run the product-specific checks below on your own theme, checkout and integrations.

1. 1

   Map each functional domain context to one Google tag or Tag Manager identifier. Without Domain Context Router, the default context is used.

2. 2

   Connect your consent UI to the provider-neutral controller event/API or its supported Complianz adapter. Test denial, grant and withdrawal with Google requests intercepted locally.

3. 3

   If WooCommerce is active, verify view_item, add_to_cart, begin_checkout and a verified purchase on synthetic orders, without customer identity fields.

With Google requests simulated, confirm no provider loads before consent. Check allowed events and ensure receipts and token-bearing referrers do not start Tag Manager.

• Google Consent Mode starts with all storage categories denied. A remote Google script can load only after a statistics grant on eligible pages.
• Direct Google tag metadata strips query strings and fragments and reduces recognized private routes to the origin. A no-referrer policy is installed before a provider loads.
• Tag Manager is blocked on recognized sensitive current URLs or referrers, including order receipts and token-bearing links; its API is absent on those pages.
• The plugin cannot control an arbitrary Tag Manager container or custom private routes that have not been declared. Audit such routes and container tags before enabling them.
• A local browser marker limits duplicate purchase dispatch in that browser but does not prove remote collection. Clearing storage or blocking scripts can affect deduplication and delivery.
• Granting consent can send the visitor IP and ordinary request metadata to Google. Review your notices, provider settings and legal basis for your own site.