Adds dynamic tags for Bricks Builder to fetch cookie values.
Cookie Bricks allows you to create dynamic tags in Bricks Builder that fetch cookie values.
Perfect for personalization based on user behavior or preferences stored in cookies.
Screenshots
Example of how to insert a cookie value into a text field.
Example of conditional display based on cookie value.
Example of a dynamic URL created with a cookie value.
Example of how to insert a cookie value into a code block.
How do I use the plugin?
Simply use the dynamic tag {get_cookie_value:cookie_name} in Bricks Builder, replacing cookie_name with the key of your desired cookie.
You can insert it in any field that supports dynamic tags, such as Heading, Text elements (basic, rich and variants), conditions, custom URLs, code blocks, etc.
For example, to obtain the value of a cookie named "liked_posts", write {get_cookie_value:liked_posts}.
Why not simply use values in custom fields (ACF, Metabox…) ?
Custom fields are very useful for storing manually entered values. But sometimes you need to use values that are dynamically generated according to user behavior, automatically calculated, or retrieved from other sources. This is where cookies come in.
Examples of use :
Recently consulted articles or products, date of last visit, time spent on a page, last page visited, filter parameters applied to a search, last step completed in a form, last button clicked, choice of theme (dark/light), and many others.
For each of these situations, it’s possible to use the value directly in a text field, or to use it for conditional display (e.g. for A/B testing).
What happens if the cookie doesn’t exist?
The tag will return “Cookie not found” by default.
How do I check the value of a cookie?
On your page, open the browser console with F12 (or CTRL+SHIFT+I), go to the “Applications” tab –> “Cookies” –> yourwebsite.com
⚠️ Currently, Cookie Bricks 1.0 can read the value of a cookie, but cannot create it. Make sure that the cookies you want to retrieve exist in the browser.
ChangeLog
See changelog.txt for details.
