Consent-first script loading and per-script gating
Consent-first script loading makes your Webstore ask each guest which kinds of cookies they accept, and then load your third-party scripts β Google Tag Manager, FullStory, Contentsquare and similar β only after the guest has accepted the cookie categories those scripts use. Zenoti collects the consent, enforces it, and keeps a record of every guest's choice, so you do not need a separate cookie consent product for your Zenoti booking site.
Why it matters. Privacy laws in the EU and the UK require a website to get consent before it sets non-essential cookies, and other regions are adding similar rules.
Audience: Webstore administrators who manage third-party scripts and cookie consent. It matters most if you have guests in the EU, the UK or another region with cookie consent laws, or if you want consent records kept in Zenoti. Your Zenoti CSM can help with setup.
On this page
- Before you begin
- How scripts are gated
- Steps
- What guests see
- Things to know
- Tips
- Troubleshooting
- Related articles
Before you begin
- Enable consent-first script loading is off by default. Nothing changes on your Webstore until you turn it on.
- The Cookie Policy field is for an external consent tool. It is deprecated and appears in the settings only when it already holds a value. Consent-first loading and the Cookie Policy field cannot be used together: with both set, the page shows a configuration-conflict warning and Publish is blocked. If you use an external tool today and want to switch, clear that field first. If you keep your external tool, it continues to work unchanged.
- Gather all your third-party scripts, including FullStory. The separate FullStory field no longer exists β FullStory now goes in the Third Party Scripts (Google Tag Manager etc) field with every other script.
- Know which category each vendor's cookies belong to: Functional, Analytics, Performance or Advertising. Zenoti suggests categories for Google and Facebook Pixel cookies; cookies from other vendors you classify yourself.
- Optional: have the address of your privacy policy page ready, so the cookie banner can link to it.
How scripts are gated
A script loads only when the guest has accepted the categories its own classified cookies belong to. Each script is judged on its own cookies; one script's categories never affect another.
| Script | Loads when the visitor accepts |
|---|---|
| Google Tag Manager | Any one of the categories its cookies belong to |
| Every other script (FullStory, Contentsquare, and so on) | Every category its cookies belong to |
| A script with no classified cookies | Never β it does not load at all |
Google Tag Manager gets the relaxed rule because it is a container: blocking the whole container for one declined category would also block tags in categories the guest did accept. Zenoti applies Google Consent Mode v2 itself β it sets the consent defaults when the page loads and sends an update whenever the guest's choice changes β so tags inside your Tag Manager container are suppressed for declined categories automatically. You do not need to configure Consent Mode inside Tag Manager. Other scripts have no consent layer of their own, so they need every category.
Enforcement defaults to deny: only cookies and storage keys that are both classified and consented to are kept, and anything unknown or unconsented is removed automatically.
Worked example
Google Tag Manager sets Functional, Analytics and Performance cookies. FullStory sets Analytics and Performance cookies. Contentsquare sets Analytics cookies only.
| Guest's choice | Google Tag Manager | FullStory | Contentsquare |
|---|---|---|---|
| Accept all | Loads | Loads | Loads |
| Analytics only | Loads | Blocked | Loads |
| Performance only | Loads | Blocked | Blocked |
| Functional only | Loads | Blocked | Blocked |
| Reject all | Blocked | Blocked | Blocked |
With Analytics only, FullStory stays blocked because its cookies span two categories and the guest accepted only one, while Google Tag Manager β which needs any one of its categories β still loads.
When a guest changes their choice. If a guest later accepts a category that an already-running script needs, the page reloads once so that script runs again with the wider consent. A script that had not run yet loads without a reload. If a guest withdraws Analytics or Advertising consent, the page also reloads, so trackers that were already running stop.
Steps
Turn on consent-first script loading
- Navigate to Configuration > Online booking > Online booking settings and select the Webstore V2 tile.
- Open the Analytics section.
- If the Cookie Policy field is shown and holds a value, clear it.
- Turn on Enable consent-first script loading β the first setting in the Analytics section.
- Paste all your third-party scripts into Third Party Scripts (Google Tag Manager etc). One field, FullStory included.
- Select Scan Scripts and wait for the results.
- Confirm or correct the category of every cookie and storage key in the list, and add any the scanner missed. The next section explains the list.
- Optional: enter your privacy policy page address in Third-party cookie policy page URL, so the banner links to it.
- Select Publish. Publishing is blocked until every item has a category.
- Test in a private or incognito browser window. Accept only some categories and check which scripts load.
Repeat steps 6, 7 and 9 whenever you change a script or add a tag to your Google Tag Manager container.
Classify what the scanner finds
Scan Scripts lists every cookie and browser-storage key your scripts set, in the Cookie & Storage Classification panel. The panel appears only while consent-first loading is on, the Cookie Policy field is empty and the Third Party Scripts (Google Tag Manager etc) field has content.
Each item under Configured cookies/keys shows a Category (Functional, Analytics, Advertising or Performance), a Type (Cookie, Local Storage or Session Storage), and how sure the scanner is:
| Label | Meaning |
|---|---|
| High confidence β detected active on your site | Seen being set when your scripts ran. |
| Low confidence β may not fire; safe to delete if unsure | Found in the script code, but may never be set. |
The scanner is not exhaustive, and you are the final authority on every category. Add anything it missed under Add new cookies/keys.
Deleting an item moves it to Previously deleted cookies/keys. Select Add there to move it back to the configured list. A later scan does not bring back an item deleted from the same script.
The scan is a snapshot of what your scripts set at that moment. If you change a script, or add a tag to your Google Tag Manager container, scan again and classify the new items. Until you do, they stay blocked.
Publish is blocked while any of these is true:
- the Third Party Scripts (Google Tag Manager etc) field has changed since the last scan;
- any item has no category (the panel shows "All cookies must be assigned a category before saving.");
- the Cookie Policy field holds a value.
What guests see
Zenoti's cookie banner appears on your Webstore. It shows only the categories in use on your site β if nothing sets an Advertising cookie, there is no Advertising choice. Zenoti's own trackers count too: Analytics appears when Zenoti's Google Analytics is active, and Advertising appears when a Facebook Pixel ID is set.
When you have entered a Third-party cookie policy page URL or classified any third-party cookies, the banner shows Third party cookie policy with a View link. If you entered a URL, the link opens your page. If not, it opens a list titled Third-party cookies used on this site, giving each cookie's Name, Category and Type, so the notice stays complete without a written policy.
Every guest's choice is saved in Zenoti. See Cookie Consent Audit Logging.
Things to know
- Unknown cookies are blocked. Only cookies and storage keys that are both classified and consented to are allowed; anything else is removed automatically. A new tag added to your Google Tag Manager container stays blocked until you scan, classify it and publish.
- A Google Tag Manager container loads whole. Zenoti cannot load part of a container. Consent Mode v2 stops Google tags in declined categories, and a cleanup sweep removes any declined-category cookie that still appears. A non-Google tag inside the container that ignores Consent Mode may set a cookie briefly before the sweep removes it.
- Zenoti can only remove cookies on your own domain. It cannot remove a cookie a vendor sets on the vendor's domain, and it cannot withdraw a tracking request that has already been sent. That is why scripts are blocked up front rather than cleaned up afterwards.
- Browser storage is enforced on classified keys only. Zenoti's own storage is never touched.
- Do not run your own consent tool alongside. Consent-first loading works correctly only if you are not running your own consent tool through the Third Party Scripts (Google Tag Manager etc) or custom script fields. The settings page warns about this but cannot prevent it.
- Category suggestions cover Google and Facebook Pixel cookies only. Cookies from every other vendor need manual classification.
Tips
- Scan again whenever a vendor updates its script or SDK β vendors can add new cookies without notice.
- If you also use the Read and Honour Global privacy control setting, note that it is a separate signal: it decides whether the Webstore honours a browser-level opt-out, while consent-first loading decides whether scripts run before a guest makes a choice. Both can be on together.
- Check your classified cookie list against your published privacy policy, and update the policy if the scan finds cookies it does not describe.
Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
| Publish is blocked after turning on Enable consent-first script loading | The Cookie Policy field holds a value. | Clear the field, then publish. |
| Publish is blocked | A cookie or storage key has no category, or the scripts changed since the last scan. | Select Scan Scripts again and classify every item. |
| The Cookie & Storage Classification panel does not appear | Consent-first loading is off, the Cookie Policy field holds a value, or the scripts field is empty. | Turn the setting on, clear the Cookie Policy field, and add your scripts. |
| A script never loads, whatever the guest accepts | It has no classified cookies, or it was changed after the last scan. | Scan again, classify its cookies, and publish. |
| Google Tag Manager does not load even though a category was accepted | None of its cookies are classified, or the accepted category is not one of them. | Scan again and check its cookies and their categories. |
| A script other than Google Tag Manager does not load | The guest did not accept every category the script's cookies belong to. | Expected. Check the script's categories and correct them only if the classification is wrong. |
| A new Google Tag Manager tag is not firing | Its cookies were added after the last scan, so they are blocked. | Scan, classify and publish. |
| A cookie appeared even though the guest declined | A non-Google tag in Google Tag Manager ignored Consent Mode (the sweep removes it), the cookie sits on a vendor's own domain, or a third-party consent banner is pasted in the scripts field. | Remove any pasted banner. The other two are known limitations. |