When someone lands on a Zenario-powered site for the first time, the very first thing they may encounter—before the page has even finished loading its content—is a cookie notice. This isn't an afterthought bolted on by a third-party plugin; it's a native part of Zenario, designed to help site owners meet data protection legislation such as the UK GDPR and PECR.
What the visitor actually sees depends on how the site has been configured (more on that below), but broadly there are two possible experiences:
If the visitor followed a link containing a page anchor (e.g. a link to a specific section of a page), Zenario is careful not to lose that anchor once the visitor has clicked through the cookie prompt—so they land exactly where they expected to.
Until a choice is made (in explicit consent mode), Zenario deliberately withholds any JavaScript that's been flagged as cookie-issuing, so nothing like analytics or embedded third-party content (e.g. an iframe) fires prematurely.
The cookie configuration lives in the site-wide settings area of Organizer.
To find it:


Inside this panel you'll find three tabs: Cookie policy, reCaptcha policy, and Timeouts. The most important one is Cookie policy, which is where the overall consent mode is set via the "Cookie policy" dropdown.
The Cookie policy dropdown in the Cookie control panel offers three options. Each strikes a different balance between simplicity and legal compliance, so it's worth understanding what each one actually does before choosing.
This is the default option on a freshly installed site, and the one recommended for best legal compliance. It works as a sequence of two popup boxes:



Here, Zenario displays a simple "Continue" button on the first page a visitor sees, referencing the site's use of cookies and linking to the privacy policy. The visitor isn't required to actively accept anything—clicking "Continue" (or simply carrying on browsing) is treated as consent.
It's a lighter-touch approach, and not likely to be legally adequate for many jurisdictions. The site owner should check the policy is satisfactory. They must also make sure the link to privacy policy is set up correctly.

In this mode, Zenario places cookies on a visitor's browser silently, with no warning or banner at all. Because most data protection regimes (GDPR/PECR in the UK and EU, for instance) require some form of notice or consent before non-essential cookies are set, this mode should really only ever be used during early development, never on a live site.
Regardless of the mode chosen, a small number of functional cookies are used by the core system:
| Cookie | Purpose |
|---|---|
z_session_id |
Essential session cookie; always set |
z_cookies_accepted |
Records that the visitor has accepted cookies |
z_admin_last_username |
Stores the administrator username after logging in |
z_admin_2fa_1 |
Set once an administrator passes two-factor authentication |
z_admin_login_shown |
Set when an administrator logs in with "remember me" enabled |
For most live sites, explicit consent is the setting to choose: it gives visitors real control, holds back non-essential cookies until they've made a choice, and keeps the site on the right side of GDPR/PECR requirements. To achieve this better compliance the site owner must make sure any cookie-issuing JavaScript is added via the "Cookie-creating HTML/JS" option rather than the general head/body code areas, so it's properly withheld until consent is given.