Cookie Consent Hub

Yes. The plugin connects to the CookieConsentHub service to load your consent banner configuration and customizations, and to handle consent logging. See the External services section above for what that entails.

Yes. The plugin is designed to work with WP Rocket, W3 Total Cache, LiteSpeed Cache, and WP Super Cache. Scripts are blocked server-side so the cached HTML already has scripts in a blocked state.

Google Analytics (including the GA4 gtag loader), Facebook Pixel, TikTok Pixel, LinkedIn Insight Tag, Hotjar, Mixpanel, Intercom, Zendesk, HubSpot, and other common tracking scripts. Scripts are categorized as analytics, marketing, or personalization. The full list is shown on the plugin’s settings screen.

No, and deliberately. Consent Mode v2 works by letting the GTM container load and then signalling the visitor’s consent state to it, so that GTM itself withholds the tags that need consent. Blocking gtm.js outright would stop those signals from ever being delivered. Tags loaded directly rather than through GTM are still blocked as listed above.

Scripts added through the normal WordPress queue are rewritten as WordPress prints each one, which costs almost nothing. On WordPress 6.9 and later there is additionally one pass over the finished page; responses with no script tag at all are skipped entirely, and on a cached site that pass runs once per cache build rather than once per visitor. If you would rather not have it, turn the option off — the banner script still blocks trackers in the browser.

Only scripts registered through WordPress’s own script queue can be rewritten as they are printed. These cannot, and are left to the banner to hold back in the browser:

• Tracking code pasted directly into a theme file or a theme “header scripts” setting
• Tags another plugin prints into the page instead of queueing them
• Tags inside post or page content, such as a Custom HTML block
• Tags a script loads after the page has already reached the browser

On WordPress 6.9 and later, WordPress can also hand the plugin the finished page, which covers the first three of those before anything is sent. Some page builders and performance plugins switch that off for the whole site — Elementor is one — and on earlier WordPress versions it does not exist at all. In those cases the tags are held in the browser by the banner instead. Either way, running any of the four supported caching plugins also hands the plugin the whole page while the cache is being built.

In the CookieConsentHub dashboard. The settings screen in WordPress covers the few options that need to be available locally; everything else lives in the dashboard.