Cookie Consent Audit Logging
When a guest interacts with the cookie consent banner on the Webstore, Zenoti records the consent choice in a backend audit trail. This article explains what the audit log captures and how your organization can use it to demonstrate compliance with privacy regulations.
Audience: Organization administrators and compliance teams responsible for maintaining records of guest consent choices.
On this page
- Before you begin
- How consent audit logging works
- What the audit record contains
- Tips
- Troubleshooting
- Related articles
Before you begin
- Your organization must have the Webstore active and accessible to guests.
- The cookie consent banner must be enabled for your Webstore. If guests are not seeing a consent banner, contact your administrator to verify the consent configuration.
- No staff permissions are required to view consent audit data in the backend system β access is managed at the organization level by your Zenoti account team.
How consent audit logging works
Each time a guest makes a choice on the cookie consent banner β accepting, rejecting, or adjusting cookie preferences β the Webstore posts a consent audit event to the Zenoti backend. This happens automatically; no configuration is needed to enable the logging itself.
The audit event captures three pieces of information:
- The consent state β whether the guest accepted, declined, or partially accepted cookies
- The consent-management platform source β which consent management system surfaced the banner to the guest
- A browser context identifier β a value derived from the Zenoti browser context cookie that links the consent record to the specific browser session in which the guest made their choice
This approach ensures that your organization retains a timestamped, session-linked record of every consent decision made on the Webstore, supporting regulatory audit requirements without relying on guest account data alone.
Note: Consent audit records are created at the point of guest interaction. If a guest does not interact with the consent banner β for example, if they close the browser before responding β no audit event is recorded for that session.
What the audit record contains
The following information is captured in each consent audit event.
| Field | Description |
|---|---|
| Consent state | The choice the guest made: accepted, declined, or a partial selection of cookie categories |
| Consent-management platform source | Identifies the consent management system that presented the banner |
| Browser context identifier | A session-level identifier derived from the Zenoti browser context cookie, linking the record to the specific browser session |
Important: The browser context identifier is derived from a browser cookie, not from the guest's account. If the guest clears their cookies after consenting, the identifier from that session remains in the audit log but will not link to any future sessions from the same device.
Worked example
A guest visits the Webstore for the first time. The consent banner appears, and the guest selects the option to accept all cookies. Zenoti records an audit event with:
- Consent state: Accepted all
- Consent-management platform source: The consent platform configured for your organization
- Browser context identifier: A unique value such as
ctx_a1b2c3d4e5f6tied to that browser session
The guest returns the following week from the same browser. If the cookie is still present, the consent banner does not reappear, and no new audit event is created. If the guest has cleared their cookies, the banner reappears, and a new audit event is recorded with a new browser context identifier.
Tips
- Retain audit records according to your jurisdiction's requirements. Privacy regulations vary by region. Work with your legal team to determine how long consent records must be kept and whether the Zenoti audit log meets your retention obligations.
- Cross-reference browser context identifiers with session data if needed. Because the browser context identifier is session-based rather than account-based, it is most useful for confirming that a consent interaction occurred at a given point in time, not for identifying a specific guest.
- Enable the Global Privacy Control toggle for California consumers. If your organization serves guests in California, enable the Read and Honour Global privacy control setting (under PRIVACY CONTROL) at Configuration > Online booking > Online booking settings > CX V3 to ensure that guests whose browsers signal a GPC preference have their tracking automatically restricted, independent of the consent banner interaction. This toggle is off by default.
Tip: For broader Webstore compliance configuration, including the consent banner appearance and privacy policy links, see Compliance and consent.
Troubleshooting
The consent banner appears but no audit record is created.
Verify that the guest completed an interaction with the banner β dismissing the page or scrolling past the banner without responding does not trigger an audit event. The event fires only when the guest makes an explicit choice. If guests are regularly dismissing without interacting, consider adjusting the banner's design or placement through your consent management platform.
The browser context identifier does not match across sessions for the same guest.
This is expected behavior. The identifier is tied to the browser context cookie, which changes if the guest clears their cookies, uses a different browser, or opens a private browsing session. Each session produces its own identifier. The audit log does not deduplicate across sessions.
Audit records are present but do not reflect a recent consent interaction.
Webstore configuration changes can take up to 30 minutes to propagate due to cache invalidation. If you recently updated consent banner settings, allow 30 minutes before verifying audit behavior in a test session.