Full documentation

Concept changes

Implicit (configuration)Auto-grant for reservation

Went from granting a pending consent on every user that gets a relation to the property → To only automatically granting either pending or implicit consent when a user makes a reservation. Pending if it requires confirmation, implicit if not. One can also specify rules that the reservation or user profile must pass in order to get the consent. Implicit will from now on only refer to the status of a user consent

Implicit (status) → Pending & Implicit

Previously pending and implicit was the same thing. (I know…)

Pending status will now never be valid

Implicit status only appears through auto-grant without confirmation and will be valid if you specify it in the campaign To note:

We assume that consents coming in through external sources are explicit The only practical relevance of implicit and explicit statuses are for safety measures and for “documentation”

Require confirmation

Could previously only be added to implicit consent

→ Can now be added to all consents, removing the need for the newsletter consent to be implicit.

All consents with require confirmation will be pending until confirmed

Consent configurations

In bold are things that have changed

Previous configuration

Created in Bookboost:

NEWSLETTER → implicit

IMPLICIT_WOLRD legacy

PROMO legacy

Created through PMS:

For each property

DOI → to be deleted in shiji

EXP → to be deleted in shiji

IMP → to be deleted in shiji

CBDP → not in use

LOYAL → not in use

MOBIN → not in use

MOBPR → not in use

NEWSL not in use

PROMO → Used for mobile messages

New configuration

Created in Bookboost:

NEWSLETTER →

implicit Require confirmation Will have multiple sources

We no longer need the consent configuration to be implicit (now called auto-grant) to support double opt-in. Any consent with “require confirmation” will be pending (triggering the DOI) until confirmed Read more in Full documentation

IMPLICIT_WOLRD to be deleted

PROMO to be deleted

Created through PMS:

For each property

DOI → to be deleted in shiji

EXP → to be deleted in shiji

IMP → to be deleted in shiji

CBDP → not in use

LOYAL → not in use

MOBIN → not in use

MOBPR → not in use

NEWSL

Used for syncing newsletter subscribers from Synxis

Will have “Require confirmation” in order to support double opt-in To be changed to NEWSLETTER in Shiji

PROMO

***Used for mobile messages Will have auto-grant + rules to add implicitly to Synxis bookers***

Mobile messages

The PROMO consent will now have 2 sources

Shiji & Auto-grant

The ones coming from Shiji will be seen as explicit (no changes here)

The ones coming from auto-grant will be implicit

Therefore we will need to change the sms campaigns to allow for implicit consents (In this case, this can be done safely at any time)

image.png

Newsletter