Managing consent declarations

Modified on Tue, 5 May at 6:58 PM

Managing consent declarations

Consent declarations allow you to obtain, track, and verify customer consent for terms, data processing, marketing, and other agreements. Essential for GDPR compliance and transparent customer relationships.

TL;DR

Go to Account → Consent declarations. Create a declaration with a name, checkbox label, and optional document URL. Link it to campaigns. Embed in forms using <hh-consent.checkbox declaration="slug" />. Add required attribute to make it mandatory. Check consent status with <hh-consent.exists declaration="slug" identifier="%lead_email%" />.

Get started in 4 steps

Create a consent declaration

Go to Account → Consent declarations → New Declaration. Enter a name (internal), a description/checkbox label (the text shown to customers — supports HTML), and optionally a document URL linking to your full terms. The slug is auto-generated and used in placeholders.

Link to campaigns

Click the edit icon in the "Linked to campaigns" column. Check the campaigns where this declaration applies. When linked, you can use simplified placeholders without specifying the identifier — the campaign's default identifier is used automatically (typically lead email).

Embed consent checkbox in forms

Add the consent checkbox to a campaign form or booking form:

<hh-consent.checkbox declaration="slug" />

To make consent required before form submission:

<hh-consent.checkbox declaration="slug" required />

Check and use consent status

Verify if a customer has consented (returns true/false — usable in @if conditionals):

<hh-consent.exists declaration="slug" identifier="%lead_email%" />

Generate a URL where customers can manage or withdraw their consent: <hh-consent.url declaration="slug" identifier="%lead_email%" />

Read more⌄

Standalone iframe consent form

Embed a standalone consent form (outside a booking form) using:

<hh-consent.iframe-form declaration="slug" />

What consent data is stored

Only minimal data is stored: the identifying key value (e.g. email address), which declaration it belongs to, and where/when the consent was obtained. No other personal data is attached to the consent record.

API and tracking in campaign tables

Consents can also be managed via the Hubhus API — useful for external systems creating or revoking consents programmatically. See the API documentation.

When a declaration is linked to a campaign, consent status is visible directly in the campaign's lead table — you can filter and export by consent status.

Common searches

consent declaration • GDPR consent • consent checkbox • hh-consent • marketing consent • opt-in • terms and conditions • consent tracking

Configuring data deletion settings
Setting up anonymization rules
Managing trusted IP addresses
Setting up two-factor authentication (2FA)