Marketing consent has to come from somewhere before Bookboost can act on it. This article covers the three routes into the platform: a consent form you build in Bookboost, a form embedded in a campaign, or a push from an external system through the API. Double opt-in sits on top of any of them.
Work out where your consent comes from
Before setting anything up, answer two questions about your own environment.
Do you collect consent through your PMS, an external form, or a custom integration?
Does your PMS track marketing consent at all? Some do not. If yours does not, Bookboost has to be where consent is collected and stored.
Creating a consent form in Bookboost
Go to Settings > Consent Forms.
Create or edit a form.
Define the consent name and purpose, any confirmation settings, and the consent scope and expiration.
Name the source in the description. Bookboost cannot detect where a consent originated, so if you collect from several places, put the source in each form's description. Without it, nobody on your team can tell which form fed which record, and a GDPR request becomes guesswork.
Embedding a form in a campaign
Open the campaign editor and scroll to the bottom of the message editor.
Select Guest App > Consent.
Select the form token you want.
The token is inserted into your message.
This is the straightforward way to collect single opt-in consent inside messages guests already receive, such as a booking confirmation or check-in email.
Pushing consent in through the API
When consent is collected outside Bookboost, on your website, in your PMS, or in a booking engine, send it in through the API.
Update User. Requires the UUID of an existing profile.
Store User in List. Takes an email, matches the first existing profile with that address or creates a new one, and adds the user to a list.
Add User to List. The same as Store User in List, but requires the UUID of an existing profile.
List and consent UUIDs can be read from the interface once your API key has been issued. User UUIDs are best retrieved programmatically with Index Users, though the interface works for one-offs and troubleshooting.
Adding double opt-in
If you need explicit confirmation, which is what GDPR expects for marketing, turn on double opt-in. It is most useful when consent is first collected somewhere else, because it makes the guest confirm in a channel you control.
Bookboost receives the consent, from the API or the PMS.
In the consent configuration, enable Require Confirmation. The consent is stored as pending.
Build a Journey campaign using the trigger after double opt-in has been requested, asking the guest to confirm.
When the guest clicks the confirmation link, the status becomes granted.
Only guests who confirm end up in your marketing audience.
What this does not do
Bookboost cannot detect the source of a consent. If you do not record it in the form description, it is not recorded anywhere.
Not every PMS supports consent. If yours does not, no amount of syncing will produce it, and you need to collect it in Bookboost instead.
Pending is not consent. A guest who never clicks the confirmation link cannot be marketed to, whatever your external system recorded.
What to do next
See Consent management essentials for the statuses and how campaigns check them, and Consent configurations for the fields and toggles on a consent definition.
Getting help
Open Help at the bottom of the left menu and choose Talk to Us, or email support@bookboost.io.