Consent and cookies on your site
The consent modes, the Monfri banner, how Monfri follows a consent manager you already have, and what marketing consent changes.
You decide how the Monfri script asks your visitors for consent. In CDP, open Settings → Tracking & SDK and scroll to Advanced tracking configuration. Change what you need and click Save configuration — the script on your site picks it up by itself; nothing is pasted again.
Consent mode
| Mode | What happens |
|---|---|
| Anonymous until consent (recommended) | Until the visitor answers, visits are counted anonymously and nothing is written to their device. After Accept, tracking is full; after Decline, it stays limited. |
| Strict opt-in | Nothing but what is strictly needed is sent until the visitor accepts. |
| Follow CMP only | Monfri waits for your own consent manager and does exactly what it says. |
| Implied (all on, no consent asked) | Everything is on and nobody is asked — only where your lawyer has confirmed that this is allowed for your site. |
Sites set up from 7 October 2026 start with Anonymous until consent, the Monfri banner on, and both switches below on. Sites set up before that are Implied until you change them.
The Monfri banner
Tick Show the Monfri consent banner when your site has no consent manager of its own. Visitors see a small banner with Accept and Decline, with equal weight. Nothing is stored on the visitor's device before they choose.
Add your Privacy or cookie page — the banner links to it as "More information". A link on your site can open the banner again with cdp.showConsentBanner(), for example a "Cookie settings" link in your footer.
A consent manager you already have
When your site has a consent manager, the Monfri banner never shows; the decision comes from your manager instead:
- IAB TCF v2.2 banners — with Bridge IAB TCF CMP ticked, Monfri follows their choices.
- Cookiebot, CookieYes, Complianz and OneTrust — Monfri reads their decision by itself.
- Usercentrics, Iubenda, Klaro, CookieScript, Termly, Osano and similar — Monfri recognises them and keeps its banner away, but it cannot read their decision. Your developer passes it on with
cdp.consent(); ask us at [email protected] for the details.
With a consent manager, Follow CMP only is usually the right mode.
The privacy switches
- Honor GPC / DNT — a browser that sends Global Privacy Control or Do Not Track is treated as an opt-out.
- Anonymize IP — visitors' IP addresses are shortened on our servers; their city is still recognised.
- Device fingerprint — Off (privacy-first, recommended for news), Passive (non-invasive signals) or Full (consented only).
What marketing consent changes
Some features act only for visitors who gave marketing consent — for example the chatbot's proactive invitations. The recipes can be limited to consenting contacts too: Workspace settings → Marketing consent for recipe emails in the Hub. Order receipts and shipping notices are never affected by it.
Each consent decision is recorded and shows in GDPR → Consent Records — see Personal data requests in CDP: export, delete, consent records.
Good to know
The legal side — which mode your site needs — depends on your country and your site. Monfri gives you the switches; your privacy policy should say what you use.
If something doesn't work
The banner does not show
Your site has a consent manager of its own — then that is expected — or Show the Monfri consent banner is not ticked, or the visitor already answered. In a private window you see it again.
Two banners show
Your consent manager is not one Monfri recognises. Untick Show the Monfri consent banner and pass the decision with cdp.consent().
Fewer visitors since I changed the mode
Stricter modes count fewer people in full: those who decline, or never answer, are limited or not counted. That is the purpose of the mode.