When you enable cookie consent settings for progressive checkouts in ROLLER, it means that any guests using progressive checkouts must agree to the collection of tracking data in the form of cookies before they can proceed with their booking. This is to comply with regulations such as GDPR, which require user consent for data tracking.
But, if your website already asks guests for cookie consent, it can be disruptive for guests to be asked for their consent again when they reach a checkout to make a booking. To avoid this, you can transfer the cookie consent data you've already collected from your website to the checkout. This means guests won't encounter multiple consent requests, creating a smoother purchasing experience. It also means that this data is captured in Venue Manager for auditing purposes.
Implementing cookie transfer of guest consent to ROLLER checkouts is a technical process and will require a developer who has expertise in this area to implement. The method you use depends on whether you're using a direct link for a full-page checkout or integrating the checkout into your website as an overlay experience.
This article offers advice and information on how to implement cookie transfer to people with specialized knowledge in this area.
When using a direct link for a full-page checkout experience
If using direct links for progressive checkouts, and the checkout URLs use custom domains, UTM parameters can be used to transfer cookie consent data from your website to your checkouts. UTM parameters are frequently added to the end of website URLs to monitor the performance of marketing campaigns and capture guest behavior.
Because guest preferences for cookie consent can vary, and the referring link may change, it's essential for your web developer to dynamically generate the checkout URLs based on the guest's consent (or non-consent) obtained from your website. This ensures that the UTM parameters accurately represent the guest's preferences.
For cookie consent, the following UTM parameters are involved:
- Performance consent: Your website developer can pass through performance consent (or non-consent) by using the
isPerformanceGrantedflag. They should set this flag totrueorfalsebased on the consent provided by guests on your website. - Marketing consent: Similarly, marketing consent (or non-consent) can be passed using the
isMarketingGrantedflag. Again, your developer should set this flag totrueorfalseaccording to the guest's consent. - Referring website UTM parameter: A referring website link must also be included using the "ref" parameter.
Here’s an example of how these UTM parameters might look:
tickets.rollerworld.com/rollerworldonlinesales/en/products?isPerformanceGranted=true&isMarketingGranted=true&ref=rollerworld.com
In this example, both performance and marketing cookie consents are included based on the guest's preferences, and the guest's referral from "rollerworld.com" is noted.
When these consent and referring website UTM parameters are correctly transferred from your website to the progressive checkout, guests won't encounter an extra cookie consent request. However, if the progressive checkout doesn't detect these UTM parameters or if they are incomplete or invalid, the guest's consent (or non-consent) won't be transferred, and the checkout will prompt the guest to provide cookie consent again.
When integrating a checkout with your website for an overlay experience
To pass a guest's cookie consent to your overlay checkout experience, the following code will need to be included in the elements (buttons) on your website that trigger the progressive checkout overlay experience.
To do so, provide the following Java script element to your website developer if your overlay checkout opens at the checkout Products page:
onclick="RollerCheckout.show({ consent: {isPerformanceGranted: <boolean>, isMarketingGranted: <boolean> }})"
Your website developer will need to:
- Dynamically replace
<boolean>withtrueorfalsevalues depending on the level of consent provided by the guest. - Add the updated code to the button, or other element on your webpage, that you use to open the overlay checkout experience.
Provide the following Java script element to your website developer if your overlay checkout opens at a specific product:
onclick="RollerCheckout.showProduct({ productId: '<productid>', consent: {isPerformanceGranted: <boolean>, isMarketingGranted: <boolean> }})"
Your website developer will need to:
- Replace
<productid>with the individual product ID. The product ID is the number at the end of the end of the URL when the product has been selected in the checkout. Learn more - Dynamically replace
<boolean>withtrueorfalsevalues based on the level of consent already provided by the guest from your website. - Add the updated code to the button, or other element on your webpage, that you use to directly open the specific product in the checkout.