Cookie consent and consent mode banner

Cookie consent in Hummerce works on two independent levels: a built-in information banner that only notifies the customer about cookies, and Google Consent Mode v2 - a mechanism that holds back data sent to Google Analytics 4 and Google Ads until the customer gives consent in a consent management platform (CMP). Both elements are configured separately and can be combined.

Cookie information banner - core platform feature (disabled by default); Consent Mode v2 requires a consent management platform outside Hummerce. Last updated: 2026-10-07.

¶ Benefits and use cases

Information banner ready in the panel right away - turning it on and setting its basic text costs nothing extra and needs no technical implementation.
Compliance with Google's requirements for Consent Mode v2 - Google Ads campaigns and GA4 reports keep some conversion data even without the customer's consent to analytics cookies.
One consent platform for all marketing tools connected through Google Tag Manager - GA4, Facebook Pixel and Conversions API in Hummerce, Edrone - marketing automation integration and others react to the same customer consent.
Separate consent categories and symbols per integration - e.g. a dedicated marketing consent symbol for a chosen tool.

¶ How it works

The built-in Hummerce module (disabled by default) shows a cookie message with a link to the privacy policy on every page, until the customer clicks the accept button.
Acceptance is saved in a browser cookie, not on the customer's account - after clearing cookies or in a private window, the banner shows again.
The banner only informs: it doesn't ask for consent by category and doesn't pass any consent to Google or other tools. It doesn't replace a consent management platform (CMP).
The banner's look is chosen from ready-made templates (light or dark background, at the bottom, at the top, or a floating window).

Google measurement and ads (GA4, Google Ads) can only store data after the customer's consent in the relevant category. Consent is reported by a consent management platform (CMP, e.g. Cookiebot, OneTrust), connected in Google Tag Manager - marketing tag container.
BS4 and BS5 templates: the store can send the default consent state from the panel settings before the tags load - after turning on Send consent event (disabled by default). In BS5 this works from version 2.35.62.
Alternatively, the default consent state can be set in GTM through the CMP template. The consent update after the customer's choice is always sent by the CMP.
Full consent rules for e-commerce events and the differences between templates are described in Google Analytics 4 - Full Sales Funnel, No Code.

Integrations that run their own scripts (e.g. Facebook Pixel and Conversions API in Hummerce, Edrone - marketing automation integration) have their own consent mode - they wait for the customer's consent in the category handled by the same CMP platform.
Some integrations distinguish consent with an extra symbol (e.g. a separate marketing consent symbol), others only use the consent category set in the CMP.

¶ Version

Cookie information banner - a core platform feature, available in all current versions (disabled by default).
Consent Mode v2 - requires store version 2.32 or newer, plus a consent management platform (CMP) chosen and configured by the store.

¶ Dependencies

Google Tag Manager - marketing tag container with a connected consent management platform (CMP) - Consent Mode v2 works through GTM, not on its own.
A consent management platform (CMP, e.g. Cookiebot, OneTrust) - a separate service, chosen and paid for by the store.
A BS5 or BS4 store template with data layer calls - see Google Analytics 4 - Full Sales Funnel, No Code.

¶ Implementation

Cookie information banner - works once enabled in the panel, with no extra technical configuration.
Consent Mode v2 requires implementation - it doesn't start on its own. Scope:
- choosing and configuring a consent management platform (CMP),
- categorizing the store's scripts and cookies in the CMP,
- connecting the CMP inside the Google Tag Manager container,
- setting the consent required for individual tags (GA4, pixels, marketing integrations),
- testing consent mode on the test environment, then a production rollout.
Minimum estimated time:
- cookie information banner - from 1 h (enabling it and writing the message text),
- Consent Mode v2 with a CMP connected in GTM - from 8 h, not counting the cost of the CMP platform itself.
- The time for a specific implementation depends on its scope - we quote it individually.
What the time depends on:
- the number of scripts and tags to categorize in the CMP,
- the chosen CMP platform,
- the number of language versions of the banner text and consent messages,
- the store template (BS4 or BS5).

¶ Limitations

The built-in Hummerce cookie banner only informs - it doesn't ask for consent by category and doesn't pass any consent to Google or other tools.
Consent Mode v2 requires an external consent management platform - without it, the store has no mechanism for collecting and passing consent by category.
The store sends the default consent state only when Send consent event is turned on (disabled by default). The consent update after the customer's choice is sent by the CMP, not the store.
Accepting the information banner is saved in a browser cookie, not on the customer's account - switching browsers or clearing cookies shows the banner again.
We do not verify the configuration for legal compliance (GDPR, ePrivacy) - the privacy policy content, the choice of consent categories and the CMP platform are up to the store.

¶ Future development

A built-in consent banner with categories, reducing the need for an external CMP platform in simpler cases.

¶ Frequently asked questions

Does Hummerce have a built-in cookie information banner?
Yes. The module shows a message with a link to the privacy policy on every page, until accepted - it's disabled by default.

Does the Hummerce cookie banner meet Consent Mode v2 requirements?
No. The banner only informs. Consent by category is collected and passed by an external consent management platform (CMP), connected in Google Tag Manager.

Does Consent Mode v2 work right after a store update?
No. It requires implementation: choosing and configuring a CMP platform and connecting it in the GTM container.

Do all marketing integrations react to the same customer consent?
Yes, when connected through the same GTM container and the same CMP platform - each integration can still have its own consent category or symbol.

How long does a Consent Mode v2 implementation take?
From 8 h to connect a CMP platform in GTM, not counting the cost of the CMP platform itself. The cookie information banner alone - from 1 h.

Does Hummerce guarantee GDPR compliance?
We do not verify the configuration for legal compliance - the privacy policy content, consent categories and the choice of CMP platform are up to the store.

Want to check how cookie consent and Consent Mode could work in your store? Contact the Hummerce team (in Polish).

¶ Configuration details

¶ Access in the admin panel

¶ REST API and MCP

There are no operations on the cookie banner or Consent Mode in the REST API or the AI assistant (MCP) - settings are changed in the store panel and in the Google and CMP tools.

¶ Store messages

The information banner's text is changed in the Message Editor - Store Text and Translations. Default values are in Polish and English.

Key	Default value
`msg.cookie.message`	This website uses cookies to ensure you get the best experience on our website
`msg.cookie.dismiss`	Got it!
`msg.cookie.learnMore`	More info

¶ Parameters

The module doesn't add its own item or customer parameters.

¶ Cookie consent and consent mode banner