Skip to content

Works with your stack

Cookie consent for Themify Builder page builder on WordPress

2 keys of its own

← Cookie Rocks for your stack

Themify Builder page builder by Themify can set 2 cookies and browser-storage keys of its own for visitors, 1 of them as the page loads, without a click. With the page builder active, Cookie Rocks recognises them and gives each the category shown below.

By Themify · themify.me

Is this your product? Tell us if anything here is out of date. Write to us

What matters for consent with Themify Builder

What it stores

2 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 2 keys with the same name, duration and logic as the page builder’s code, on a test site. Without a consent tool that knows them, 2 were set before the choice, 2 kept after Reject all.

Cookie Rocks today

With the page builder 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 page builder feature, check the Cookies screen for anything left To classify.

Cookies and storage Themify Builder sets

NameKindLastsCategoryWhy
tb_{elementId} TestedCookie365 daysPreferencesRemembers the visitor's lists or past actions beyond the visit: a convenience, not strictly needed; consent in prior-consent countries.
When and what for

When: each page view showing an Alert module, only when its option Limit display count is filled (default empty).

What it is for: Counts how many times this visitor has seen an Alert module, to hide it after the set limit. Lasts: 365 days, SameSite=Strict, path /.

tf_mega_{termId} TestedLocal storageabout 1 hourPreferencesCache or technical helper that only speeds up the page: not strictly needed (the site works without it); consent needed in prior-consent countries.
When and what for

When: after hovering or clicking a mega menu category (Themify themes using the bundled framework mega menu).

What it is for: Caches the posts shown in a Themify mega menu category so they are not fetched again on each hover. Lasts: no expiry (own expiry: 1 hour, 10 minutes after an error; removed when read later).

Questions

Does Themify Builder 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 Themify Builder 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

How the trial works, in detail

Cookie Rocks

Get your trial key

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

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.