Skip to main content

Privacy or cookies consent management

Configure cookie consent options through CRS functionality or integrate your existing website consent manager to maintain compliance while optimizing guest booking experiences.

M
Written by Michelle Normoyle
Updated over 3 weeks ago

Cookie consent management

Outlined below is the explanation of the cookie consent management.

The CRS provides two pathways for cookie consent management:

  • Option one: CRS built-in consent manager operates independently from the website, with visitor consent collected directly within the booking process.

  • Option 2: Website consent integration connects with your existing website consent manager to provide unified consent across both your website and booking engine.

Once visitors make their consent selection, each booking engine page displays the option for them to change these preferences.

CRS built-in consent manager

The consent popup takes on the booking engine branding for a cohesive experience and displays the cookie categories with specific permissions for different tracking types and details are outlined below.

Cookie categories:

  • Necessary cookies for essential booking engine functionality.

  • Functional cookies for enhanced user experience features.

  • Analytics cookies for booking performance measurement.

  • Advertising cookies for personalized marketing content

Visitor options:

  • Accept all cookie types.

  • Deny all non-essential cookies.

  • Manage individual category preferences.

  • Access detailed descriptions for each cookie type.

Steps to implement the CRS built-in consent manager

Follow the steps below to implement the built-in consent manager:

  1. Go to Property Description.

  2. Go to the Branding menu.

  3. From the list, click the Branding Name to add the cookie consent to and you will be brought to the Modify IBE Branding tab.

  4. Go to Cookie Consent Config and choose from the dropdown:

    1. CRS Hotel Level Cookie if this is a single property.

    2. CRS Chain Level Cookie if part of a group or chain – this extends the collection to multi-property booking engine pages so guests don't need to provide consent again when navigating to a specific property.

  5. Add your property's privacy policy URL in the Privacy Policy Link field to provide visitors with access to your data practices as part of the consent.

  6. Click to Save.


Website consent integration

Outlined below are the setup requirements for a website consent integration:

There are three compatible platforms:

  • OneTrust.

  • CookieBot.

  • Cookie Information.

Technical requirements

Website and booking engine must share the same top-level domain. The Cookie Management Platform must use JavaScript callback hooks to communicate consent decisions automatically.

Implementation

Contact our support team [email protected] to coordinate setup or implement custom URLs if domain alignment is needed.

Actions to prepare for the integration with your consent manager

This requires collaboration between the hotel’s team and our support team to set up communication with the consent manager and booking engine, open a support case for tracking [email protected]

⚠️Important:

  • Analytics impact: Guest consent choices directly affect booking engine tracking and reporting data quality.

  • Marketing consent: Cookie tracking consent is separate from marketing communication consent, which must still be collected through reservation confirmation or other touchpoints.

  • Ongoing control: Visitors can modify their consent preferences on any booking engine page after their initial selection.

Steps to activate the integration

Outlined below are the actions to implement the consent manager.

  • Hotel team cookie categorization within your Cookie Management Platform tool, categorize the CRS Booking Engine cookies as listed below. You can create a data processor named SHR CRS or booking engine for convenience.

πŸ“ŒNote: The * in cookie names below represent a wildcard or regex naming. If your CMP doesn't support this, contact our team to confirm full cookie names [email protected]

Necessary category cookies:

  • PrivacyPolicy.*.Consent

  • delegAuthLoginCheck.*

  • forceAuth.*

  • CrsID*

  • ASP.NET_SessionId (data-processor can also be "Microsoft, ASP.Net" if pre-existing in your CMP)

Functional category cookies:

  • MultiRoom_*

  • WsDispCurr_*

  • showQualifiedRate_*

  • alreadyShow_*

  • _MultiLanguage

  • SHR team JavaScript integration, once you complete the cookie categorization, our support team will embed the CMP JavaScript as the first script in the HTML to block all cookie types unless consent is granted by visitors as they arrive in the booking engine.

Steps to activate the integration with your consent manager in the booking engine

Below are the steps to implement the consent manager on to your booking engine:

  1. Go to Property Description.

  2. Go to the Branding menu.

  3. From the list, click the Branding Name to add the cookie consent to and you will be brought to the Modify IBE Branding tab.

  4. Go to Cookie Consent Config and choose your provider from the dropdown:

    1. Cookie bot.

    2. Cookie information.

    3. One trust.

  5. Add your property's privacy policy URL in the Privacy Policy Link field to provide visitors with access to your data practices as part of the consent.

  6. Click Save.

Did this answer your question?