On this page

Jump to any section using the links below

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

What are consent declarations

A consent declaration represents a set of terms that your customer can consent to. For example, a customer may consent to:

• General Terms and Conditions
• Processing of Personal Data (GDPR)
• Receiving marketing emails
• Newsletter subscriptions
• SMS notifications

A granted consent uniquely identifies the granting customer through an identifying key (typically email address, phone number, or customer ID).

Accessing consent declarations

Go to Account → Consent declarations. You will see a table showing existing declarations with columns for Name, Declaration slug, Created date, Linked to campaigns, and Consents obtained.

What consent data is stored

The stored consent consists only of:

• The value of the identifying key (e.g., email address)
• The declaration it belongs to
• Information on where and when the consent was obtained

No other personal data is stored with the consent itself, ensuring minimal data retention.

Creating a new consent declaration

Click New Declaration to open the configuration dialog. You will configure:

• Name: A friendly identifier for internal use
• Description / Checkbox label: The text displayed to customers (supports HTML formatting)
• Document URL: Link to the full agreement/terms document

The description field supports HTML and placeholders, allowing you to create rich consent text with links to full terms documents.

Understanding declaration slugs

Each consent declaration automatically generates a slug based on the name. This slug is used in placeholders throughout Hubhus to reference the specific declaration. For example, a declaration named "Consent" gets the slug "consent".

Linking declarations to campaigns

Click the yellow edit icon in the "Linked to campaigns" column to open the campaign linking dialog. Here you can link the declaration to specific campaigns by checking the "Linked" checkbox next to each campaign.

When a declaration is linked to a campaign, you can use simplified placeholders without specifying the identifier, as the campaign's default identifier is used automatically.

How to obtain consent from customers

Consents can be obtained in different ways:

Consent checkbox in forms: Add a consent checkbox to any campaign form or booking form using:

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

The slug identifies the declaration, and the identifier uniquely identifies the customer. If no identifier is specified, the value falls back to the campaign's default identifier.

Standalone iframe form: Embed a standalone consent form using:

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

Customer consent management URL: Generate a URL where customers can view and change their consents:

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

Mandatory vs optional consent

By default, consents are optional when submitting leads from Campaign Forms and Booking Forms. To make a consent required, add the required attribute:

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

When marked as required, form submission will be rejected if the consent checkbox is not checked.

Checking if a customer has consented

There are multiple ways to verify consent:

Using placeholders: Check if a customer has given consent to a specific declaration:

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

This placeholder returns true/false and can be used in conditional logic with @if statements.

Using the API: Look up consents programmatically through the Hubhus API.

In campaign tables: Display consent status directly in campaign entity tables by activating consents for the campaign.

Simplified placeholders for linked campaigns

When a consent declaration is linked to a campaign with a default identifier configured, you can use simplified placeholders without specifying the identifier:

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

The system automatically uses the campaign's configured identifier placeholder.

Tracking consents in campaigns

When a consent declaration is activated for a campaign, you can:

• See consent status directly in the campaign's entity table
• Filter leads based on consent status
• Export consent information along with other lead data
• Monitor how many customers have granted consent

This provides full visibility into consent compliance within your campaign workflows.

Managing consents through API

Consents can be managed programmatically through the Hubhus API. This allows you to:

• Create consents from external systems
• Verify consent status before sending communications
• Revoke consents when customers opt out
• Integrate consent management with your own applications

See the API documentation for detailed endpoints and examples.

Viewing consent statistics

In the consent declarations table, the "Consents obtained" column shows how many customers have granted consent to each declaration. This helps you monitor adoption and compliance across your customer base.

Editing and deleting declarations

For each declaration in the table, you can:

• Edit: Click the yellow edit icon to modify the name, description, or document URL
• Link campaigns: Click the edit icon in the "Linked to campaigns" column
• Search consents: Click the search icon to view all granted consents
• Delete: Click the red delete icon to remove the declaration (be careful, as this affects existing consents)

Best practices for consent management

When working with consent declarations:

• Use clear, simple language in consent descriptions
• Always link to full terms documents via the Document URL field
• Make consent optional by default, require only when legally necessary
• Provide easy ways for customers to withdraw consent (using consent URLs)
• Track consent timestamps for audit purposes
• Link declarations to campaigns for simplified implementation
• Use API integration for complex consent workflows
• Regularly review consent statistics to ensure compliance
• Test consent forms thoroughly before deploying
• Document your consent processes for legal compliance

GDPR compliance considerations

Consent declarations help with GDPR compliance by:

• Providing clear, explicit consent mechanisms
• Storing minimal identifying information
• Allowing customers to manage their own consents
• Tracking when and where consent was obtained
• Enabling easy consent withdrawal

However, ensure you also:

• Have a lawful basis for processing personal data
• Provide transparent privacy policies
• Honor consent withdrawals promptly
• Maintain records of consent for compliance audits
• Consult legal counsel for your specific requirements

Summary

Consent declarations provide a complete system for obtaining and managing customer consent across your Hubhus account. Create declarations with clear descriptions and terms links, embed consent checkboxes in forms, link declarations to campaigns for simplified implementation, verify consent status through placeholders or API, and track consent statistics for compliance monitoring. This ensures transparent, compliant customer relationships while meeting GDPR and privacy requirements.

Related articles

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