iubenda
iubenda is one of the top consent management platforms (CMPs) in our CMP ranking. The Pixel Manager integrates with it automatically. This page explains how the integration works, why a page reload follows the banner click, and which settings we recommend.
Short answer
iubenda is supported and compatible with the Pixel Manager for WooCommerce, in the free and in the Pro version. Install the iubenda WordPress plugin, enable Explicit Consent Mode in the Pixel Manager, and run version 1.58.10 or newer. Nothing needs to be configured for detection.
The "Consent Management Platforms" card in the Pixel Manager admin does not list iubenda. That is expected and has no effect on tracking.
How the Pixel Manager detects iubenda
The integration runs in the visitor's browser and relies on the iubenda consent cookie:
- The
_iub_cs-<site id>cookie. iubenda writes it when the visitor decides. It contains the purposes the visitor allowed. The Pixel Manager reads it on every page load. The granular variant of the cookie is deliberately not read. - A page reload after the banner click. iubenda does not fire an event the Pixel Manager could use to apply consent on the same page, and its cookie is not yet written at the moment the visitor clicks. The Pixel Manager therefore watches for clicks on the iubenda accept and reject buttons and reloads the page. The reload is expected. It is how the first page view gets measured after acceptance.
iubenda purposes map to the Pixel Manager's consent categories like this:
| iubenda purpose | Pixel Manager category |
|---|---|
| 1 Necessary | necessary |
| 2 Functionality, 3 Experience | preferences |
| 4 Measurement | statistics |
| 5 Marketing | marketing |
A purpose that is absent from the cookie is treated as denied. The Pixel Manager never grants an iubenda purpose by default.
Install modes. We recommend the iubenda WordPress plugin. When it is active, the Pixel Manager marks its own inline configuration scripts with the _iub_cs_skip class so that iubenda's automatic script blocker leaves them alone. If you add the iubenda script by other means, the cookie is still read, but that protection is missing and iubenda's blocker may block the Pixel Manager's configuration.
The admin card does not list iubenda. The "Consent Management Platforms" card in the Pixel Manager settings is built on the server from a fixed list of WordPress plugins, and iubenda is not on it. The card reads "None detected on this site" even when the integration works. Use the Console Logger to confirm detection. See also How the Pixel Manager detects your CMP.
iubenda support is not a Pro feature.
Recommended configuration
- Update the Pixel Manager to 1.58.10 or newer. Older versions could set a wrong Google Consent Mode default for a returning visitor. See Troubleshooting.
- Install the iubenda WordPress plugin rather than pasting the script, for the autoblocker protection described above.
- Enable Explicit Consent Mode in WooCommerce > Pixel Manager > Consent Management, so that the Pixel Manager follows the decision made in iubenda. Details in the Consent Management overview.
- Enable Google Consent Mode v2 in the Pixel Manager. The Pixel Manager sets the defaults to denied in Explicit Consent Mode and sends the update after the choice. See Default Settings for what it sets. If iubenda's own Google Consent Mode is on as well, make sure only one of the two issues the default block.
- Leave Explicit Consent Regions empty unless you deliberately want implicit tracking outside certain regions. See Explicit Consent Regions.
- Run one tracking plugin. Shops that run a second pixel plugin next to the Pixel Manager get duplicate or conflicting events. Move all pixels into the Pixel Manager.
Verify the integration
- Open your shop in a private browser window, logged out of WordPress. Tracking is off for administrators by default.
- Append
?pmwloggeronto the URL and open the browser console. See the Console Logger guide. - Before you answer the banner you should see
Consent mode: explicitwith all non-essential categories denied. - Click accept in the iubenda banner. The page reloads. After the reload you should see:
Pixel Manager: Iubenda CMP consent detected
Pixel Manager: CMP consent applied from: Iubenda
with the allowed categories set to true, and the pixels loading.
- Run
pmw.consent.categories.get()in the console to read the current state.
Troubleshooting
The admin card says "None detected"
Expected for iubenda, see above. Verify detection with the Console Logger instead.
personalization_storage shows as granted before the banner on a return visit
On Pixel Manager versions before 1.58.10, a returning visitor who had accepted only functional cookies in iubenda could see a Google Consent Mode default of granted for personalization_storage, which was then corrected to denied by the update. Fresh sessions were never affected. Update to 1.58.10 or newer, which also switched the iubenda reader to deny-by-default for absent purposes and maps purpose 3 (Experience) to preferences.
The page reloads after I click the banner
Expected. iubenda offers no consent event the Pixel Manager could react to on the same page, so the Pixel Manager reloads once after the click to read the freshly written cookie.
Pixels do not load after accepting
Check for script optimisation first. Plugins that defer or delay JavaScript, and "Remove Query Strings" options in caching plugins, can serve a stale Pixel Manager bundle after an update. The console then shows Consent module failed to load - falling back to deny-by-default, which is deliberate. Switch the option off, purge caches, and exclude the Pixel Manager from JavaScript delay. The Caching and Optimization Exclusions page lists what to exclude.
If the console shows nothing at all, iubenda's blocker may be blocking the Pixel Manager's configuration script. Make sure the iubenda WordPress plugin is active, so that the Pixel Manager can mark its scripts to be skipped, or add the Pixel Manager to iubenda's exceptions.
Version history
- 1.58.10 (May 2026): deny-by-default for absent purposes, correct cookie matching, purpose 3 mapped to preferences, and the
personalization_storagedefault fix. - 1.38.0 (February 2024): the Pixel Manager's inline scripts are excluded from iubenda's blocker.
- 1.32.5 (July 2023): iubenda support added.
When to contact support
Send us the following so we can reproduce your setup in one pass:
- Your store URL.
- The debug information from WooCommerce > Pixel Manager > Support.
- Whether iubenda runs as the WordPress plugin or as a script you added yourself, and whether its Google Consent Mode is on.
- Which caching, script optimisation, tag manager, or other tracking plugins are active.
- A screenshot of the browser console with
?pmwloggeron, taken in a private window while logged out of WordPress, before and after accepting the banner.
Pro customers use the support form. Free users find help in the WordPress.org support forum.
Frequently asked questions
Is iubenda compatible with the Pixel Manager for WooCommerce?
Yes. iubenda is supported and scores 89 in our CMP ranking. No configuration is needed for detection.
Why does the Pixel Manager admin say no CMP is detected when I use iubenda?
Because the admin card only checks a fixed list of WordPress plugins, and iubenda is not on it. The storefront integration works regardless. Verify with the Console Logger.
Why does the page reload after I accept the banner?
Because iubenda provides no event the Pixel Manager could react to on the same page. The reload is the mechanism that lets the Pixel Manager measure the first page view after acceptance.
Is iubenda support a Pro feature?
No. All CMP integrations are included in the free version.
