Works with your stack
Cookie consent for the BeTheme theme on WordPress
7 keys of its own
The BeTheme theme by Muffin Group can set 7 cookies and browser-storage keys of its own for visitors. With the theme active, Cookie Rocks recognises them and gives each the category shown below.
By Muffin Group · muffingroup.com
Is this your product? Tell us if anything here is out of date. Write to us
What matters for consent with BeTheme
What it stores
2 necessary and 5 preferences, by the category our legal watch gives each key. The table below lists each one: what it is for, how long it lasts and when it is set.
Before the choice
We reproduced 7 keys with the same name, duration and logic as the theme’s code, on a test site. Without a consent tool that knows them, 7 were set before the choice, 7 kept after Reject all.
Cookie Rocks today
With the theme active, Cookie Rocks recognises these keys and gives each the category in the table. Keys in a refused category are erased after the page loads, and those the server sets are held until the visitor accepts.
What you can do now
Nothing to turn off: Cookie Rocks holds and erases these keys by category. When you turn on a new theme feature, check the Cookies screen for anything left To classify.
Cookies and storage BeTheme sets
| Name | Kind | Lasts | Category | Why |
|---|---|---|---|---|
mfn_closed_section_{section uid} Tested | Cookie | set by the site | Preferences | Remembers a display choice or that a message or pop-up was shown or closed: a convenience, not strictly needed; consent in prior-consent countries.When and what forWhen: After a click on the close button of a closeable section; only on sections with 'close for X days' set. What it is for: Remembers that the visitor closed a closeable header or builder section (for example a top bar), so it stays hidden. Lasts: number of days set on the section (data-close-days); not set when 0. |
mfn_popup_{popup id} Tested | Cookie | 365 days or set by the site | Preferences | Remembers the visitor's lists or past actions beyond the visit: a convenience, not strictly needed; consent in prior-consent countries.When and what forWhen: After the visitor closes a popup whose display mode is 'once' or 'cookie based'. What it is for: Remembers that the visitor has seen or closed a Betheme popup template, so it is not shown again (also read in PHP to skip rendering). Lasts: 365 days ('show once' popups) or the number of days set on the popup (data-cookie, cookie-based display). |
mfn_wishlist Tested | Cookie | 365 days | Preferences | Remembers the visitor's lists or past actions beyond the visit: a convenience, not strictly needed; consent in prior-consent countries.When and what forWhen: After a click on 'add to wishlist'; only with WooCommerce and option shop-wishlist enabled. What it is for: Keeps the list of product IDs the visitor added to the Betheme WooCommerce wishlist (comma separated). |
mfn-gdpr Tested | Cookie | 365 days by default | Necessary | Stores the visitor's own cookie or consent choice: exempt, a site must remember the choice (CNIL, recommendation 2020, art. 2; EDPB).When and what forWhen: After a click on the accept button of the old GDPR bar; only with option 'gdpr' enabled (default off). What it is for: Remembers that the visitor accepted the old Betheme cookie notice bar, so the bar is hidden. Lasts: 365 days by default (button attribute data-cookiedays). |
mfn-post-love-{post id} Tested | Cookie | 365 days | Preferences | Remembers the visitor's lists or past actions beyond the visit: a convenience, not strictly needed; consent in prior-consent countries.When and what forWhen: After a click on the love (heart) button; only with the theme's Love option enabled. What it is for: Remembers that the visitor already 'loved' (liked) a post or portfolio item, so the counter is not raised twice. |
mfnConsent Tested | Cookie | 365 days by default | Necessary | Stores the visitor's own cookie or consent choice: exempt, a site must remember the choice (CNIL, recommendation 2020, art. 2; EDPB).When and what forWhen: After a click in the Betheme consent banner; only with option 'GDPR 2 / Consent Mode' (gdpr2) enabled (default off). What it is for: Stores the visitor's choices in Betheme's own Google Consent Mode banner (ad_storage, ad_user_data, ad_personalization, analytics_storage as JSON) so the banner is not shown again and gtag consent is restored. Lasts: 365 days by default (theme option gdpr2-settings-cookie_expire, data-expires). |
mfnFakeSale Tested | Cookie | 1 day | Preferences | Remembers a display choice or that a message or pop-up was shown or closed: a convenience, not strictly needed; consent in prior-consent countries.When and what forWhen: After a click on the close button of the fake sale notification; only with WooCommerce and the fake sale notification option enabled. What it is for: Remembers that the visitor closed the 'someone just bought' sales notification, so it stops for a day. |
WordPress themes
Other plugins of the same kind.
Questions
Does BeTheme need a cookie banner?
Its own keys are listed below with their category. The tools you add through it, such as videos, maps or analytics, are held by Cookie Rocks like everywhere else.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For BeTheme sites
See what your theme stores, held or cleared.
tested keys
Every feature of the complete plugin for 30 days, no card.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support

Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.