Skip to content

Works with your stack

Cookie consent for the Bricks page builder on WordPress

5 keys of its own

← Cookie Rocks for your stack

The Bricks page builder by Bricks can set 5 cookies and browser-storage keys of its own for visitors. With the page builder active, Cookie Rocks recognises them and gives each the category shown below, except a key named in an Interaction, which you classify yourself.

By Bricks · bricksbuilder.io

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

What matters for consent with Bricks

What it stores

2 necessary and 3 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 5 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, 5 were set before the choice, 5 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. One key cannot be recognised: a key named in an Interaction. It appears as To classify on the Cookies screen, where you choose its category.

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 Bricks sets

NameKindLastsCategoryWhy
{custom key chosen in an Interaction} TestedLocal storageno expiry or sessionPreferencesName and purpose chosen by the site builder: unknown, so treated as needing consent. The site owner can reclassify it.
When and what for

When: only if the site uses a Browser storage interaction, on the chosen event.

What it is for: Interactions 'Browser storage: Add / Count' write any key and value the site builder chooses (e.g. to remember a dismissed notice). Lasts: no expiry (localStorage) or session (sessionStorage).

brx_popup_{id}_total TestedLocal storageno expiryPreferencesRemembers 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 for

When: when a popup opens, only with the 'Across sessions' limit set (default off).

What it is for: Counts how many times a popup was shown, for the 'Across sessions' limit.

brx_popup_{id}_total TestedSession storagesessionPreferencesRemembers 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 for

When: when a popup opens, only with the 'Per session' limit set (default off); the 'Per page load' limit uses a window variable, not storage.

What it is for: Counts how many times a popup was shown in this session, for the 'Per session' limit.

brx_pp_{COOKIEHASH} TestedCookie10 daysNecessaryAccess to a page the visitor asked for (password, login or maintenance bypass): strictly necessary (ePrivacy art. 5(3), WP29 04/2012, 3.1).
When and what for

When: after submitting the password form of a password-protection template (option).

What it is for: Remembers that the visitor entered the password of a Bricks password-protection template; HttpOnly. Lasts: 10 days (filter bricks/password_protection/cookie_expires).

brx_use_wp_login TestedCookie5 minutesNecessaryAccess to a page the visitor asked for (password, login or maintenance bypass): strictly necessary (ePrivacy art. 5(3), WP29 04/2012, 3.1).
When and what for

When: only when ?brx_use_wp_login is in the URL and custom auth pages are set (bypass not disabled).

What it is for: Bypasses Bricks custom login-page redirects to reach the default WordPress login; HttpOnly, SameSite Strict. Lasts: 5 minutes (deleted at login).

What our tests found on Bricks

  • Before the choice · BricksBricks video with a preview image now waits for consent

    On a Bricks site, Cookie Rocks 2.11.7 holds the youtube.com/embed iframe that Bricks creates when the preview image is clicked, and shows its notice for held content instead. In our test, after Reject all a click loaded nothing from YouTube; after Accept all the video played. The preview image itself still comes from img.youtube.com, as Cookie Rocks leaves video thumbnails alone.

    Seen in our tests, 12 November 2026, Bricks.

  • A setting to know · Bricks, DiviBricks and Divi 5 Interactions can write keys you name yourself

    Bricks Interactions (Browser storage: Add or Count) and Divi 5 Interactions (effect Cookie) write a key whose name and value the site builder chooses: local or session storage for Bricks, a cookie of 365 days for Divi. Nothing is written unless the site uses such an interaction. As their purpose is unknown, Cookie Rocks treats them as needing consent.

    What to do: If the key only remembers a dismissed notice or a layout choice, keep it as a preference; if it counts visits for a promotion, class it as marketing. Reclassify it on Cookie Rocks' Cookies screen.

    Read in the code of Bricks, Divi 2.2, 5.11.1, 12 November 2026.

Questions

Does Bricks 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 Bricks 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.