Hi,
Cookiebot is detecting the cookie sppb_user_timezone before user consent.
I checked the page source and it appears that SP Page Builder automatically creates this cookie using:
Intl.DateTimeFormat().resolvedOptions().timeZone
and then:
document.cookie='sppb_user_timezone='...
My Joomla website timezone is already set to Zagreb.
Is there an option in SP Page Builder to disable the sppb_user_timezone cookie on the frontend?
If it cannot be disabled, could you please clarify what this cookie is used for and whether it is technically necessary for SP Page Builder functionality?
Cookiebot also detects sppbActiveColorMode in localStorage before consent. Is there a way to disable this as well when no color modes are being used on the website?
Thank you!
cookie sppb_user_timezone=
3 replies
Hello,
Thank you for contacting us, and we apologize for the inconvenience this has caused with your Cookiebot setup.
Here is what each item is used for:
sppb_user_timezone (cookie)
This cookie stores the timezone of the visitor's browser (for example, "Europe/Zagreb") for 12 hours. It is used by the Dynamic Content feature. When a collection is filtered by a Date-Time field against the "current date", SP Page Builder uses this value so that "today" is calculated in the visitor's own timezone. It is separate from the timezone in your Joomla Global Configuration, which is why setting your site to Zagreb does not affect it.
sppbActiveColorMode (localStorage)
This entry stores the name of the active color mode, so the Color Switcher can remember a visitor's choice between page loads.
You are right about the behavior you noticed. The sppb_user_timezone cookie is currently set on every frontend page, even when no Dynamic Content date filter is used anywhere on the site. In the same way, sppbActiveColorMode is saved even when the Color Switcher is not in use. At the moment, SP Page Builder has no option to disable either of them.
I have reported this behavior to our development team, and it will be improved in a future update.
We appreciate your patience and understanding. If you have any further questions, please feel free to let us know.
Best regards
Hello,
Thank you very much for the clear explanation. This answers my questions and explains exactly what Cookiebot was detecting.
I appreciate you reporting this to the development team. I’ll leave the current setup as it is and look forward to the improvement in a future update.
One additional suggestion for Helix Ultimate: it would be very useful to have an “After <head>” custom code field, in addition to the existing “Before </head>” field.
This would allow scripts such as Cookiebot, which need to load as early as possible in the <head> and before other frontend scripts, to be added properly without modifying template files.
Perhaps this could be considered for a future Helix Ultimate update as well.
Best regards,
Jasna
Thank you for your valuable suggestion. I have forwarded your request for an “After <head>” custom code field in Helix Ultimate to our development team for consideration in a future update.
We appreciate you taking the time to share this feedback, and we’ll certainly keep it in mind for future improvements.
Best regards