Statement on cookies
Update: 19-12-2024
TUI Belgium uses cookies in order to provide maximum assistance. In addition to functional cookies, which are necessary for the proper operation of our website, we also install analytical cookies to measure the use and quality of the website. We also like to install cookies for a better user experience. These cookies enable us to display personalised and relevant offers and create social media links, and third parties to monitor your internet behaviour and display customised ads (so-called tracking cookies).
What are cookies?
A cookie is a small text file that is sent to and saved on your computer when you visit a website. TUI Belgium can install its own cookies, as well as cookies of third parties, on websites or apps of which the content is managed by TUI Belgium. By using cookies, we can ensure that you don’t receive or need to enter the same information every time you visit the TUI Belgium website, or that the website remembers your preferences.
There are different types of cookies. TUI Belgium installs cookies that are necessary for features of the TUI Belgium websites to function properly. They will for instance enable you to add products and services to your shopping cart and to view the contents of the shopping cart. We use non-essential cookies to collect information about your use of the website and retain your preferences as to our products and services, for instance the pages you visited and the duration of a user session. These cookies can also be transferred to our sister companies. The purpose of these cookies is to improve the services offered on our websites.
Overview of cookies used
Below is an overview of the cookies used by TUIFLY.be. It will give you an idea of the cookies used by TUI Belgium, the purpose of these cookies and the consequences of removing them.
Essential and functional cookies
Functional cookies help to improve the usefulness of a website by enabling basic features such as page navigation and access to secured parts of the website. Without these cookies the website cannot function properly.
| Name | Domain | Duration | Description | |
|---|---|---|---|---|
| cookie-agreed | tuifly.be | 16 days | Saves the cookiestatus of the current session | |
| has_js | tuifly.be | Session | Registers whether or not the user has activated Javascript in the browser | |
| NSC_# | cdn.tui.be | Session | Used by the netscaler in order to control the load-balancing | |
| SSESS# | tuifly.be | Session | Stores session identification in Drupal | |
| recent_searches | tuifly.be | 1 year | Saves the recent searches that is shown on the homepage | |
| view_step1 | tuifly.be | 1 month | Saves the view type of the search result list | |
| apiDomain_# | eu1.gigya.com, login.tui.com | 1 year | The shared domain API calls for all sites in a group should be sent to | |
| _gig_llu | tuifly.be, jetair.be | 1 year | Last login provider username for Login "Welcome back" screen | |
| _gig_llp | tuifly.be, jetair.be | 1 year | Last login provider name for Login "Welcome back" screen | |
| gig_bootstrap_# | gigya.com, tui.com | 1 year | Internal cookie for the Gigya WebSDK | |
| gig_hasGmid | gigya.com, login.tui.com | 1 year | Internal cookie for the Gigya WebSDK | |
| hasGmid | gigya.com, login.tui.com | 1 year | Internal cookie for the Gigya WebSDK | |
| gig_loginToken_# | .cdns.eu1.gigya.com | 1 year | Gigya's Single Sign On (SSO) group login token, that's making it possible to have one TUI account for all TUI websites | |
| gig_loginToken_#_visited | .cdns.eu1.gigya.com | 1 year | Used to keep track of visited sites within the same SSO group | |
| gig_loginToken_#_revoked_tokens | .cdns.eu1.gigya.com | 1 year | In SSO scenarios, indicates to the Gigya WebSDK that the current token was revoked, so as to log the user out | |
| ucid | gigya.com, login.tui.com | 13 months | Unique computer identifier used for generating reports, and used by the Gigya WebSDK to get saved response | |
| gmid | gigya.com, login.tui.com | 1 year | Used to identify the logged in user, you can't login without | |
| gig_canary | .account.tuifly.be, .cdns.eu1.gigya.com | 1 year | Indicates whether the client is using the canary version of the Gigya WebSDK | |
| gig_canary_ver | .account.tuifly.be, .cdns.eu1.gigya.com | 2 years | The version name of the Gigya WebSDK's canary version | |
| _ga | tuifly.be | 2 years | Registers a unique ID to distinguish users, that is then is used to generate statistical data on how users use the website | |
| mytui.uid | tuifly.be, tuifly.fr, tuifly.ma | Session |
Cookie associated with your logging into your account |
|
| mytui.session | tuifly.be, tuifly.fr, tuifly.ma | Session or 400 days | Cookie associated with your logged in status |
Analytical cookies
Google Analytics
To analyse the use of our website, we use Google Analytics. A cookie from Google is stored for this purpose. Google does not share data with third parties. For more information, read Google's privacy policy.
Analytical cookies help us understand how visitors use our website by collecting data anonymously and reporting them.
| Name | Domain | Duration | Description |
|---|---|---|---|
| _gid | tuifly.be | 1 day | Registers a unique ID to distinguish users, that is then used to generate statistical data on how users use the website |
| PageCount | tuifly.be | Session | Saves the amount of pages a user visits |
| directverkeer | tuifly.be | Used to determine whether the session is direct traffic | |
| _hjid | tuifly.be | 1 year | The cookie is set when the user lands on a page where the Hotjar cookie is active, and is used to research how users use the website |
| s_ecid | tuifly.be | 2 years | Contains a copy of the Experience Cloud ID (ECID) or MID |
| AMCV_ | tuifly.be | 2 years | The Experience Platform ID Service uses JavaScript to store a unique visitor ID |
| s_cc | tuifly.be | Session | This cookie is set and read by the JavaScript code to determine if cookies are enabled |
| s_sq | tuifly.be | Session | This cookie is set and read by the JavaScript code when the SelectMap functionality or the Activity Map functionality are enabled |
| s_vi | tuifly.be | 2 years | Unique visitor ID time/date stamp |
| s_fid | tuifly.be | 2 years | Fallback unique visitor ID time/date stamp |
| appsflyer_id | appsflyer.com | Session | Tracks conversions during the current session. Sets a unique ID to track users who make a purchase |
| ga_id | tui.be | Session | Tracks conversions during the current session. Captures visitor's ad ID or IDFV to track Android and iOS users who make a purchase |
Marketing cookies
Marketing cookies are used to follow users when they visit several websites. Their purpose is to display customised ads that are relevant for the individual user. This way, these ads become more valuable for publishers and external advertisers.
Google Ads
For marketing purposes, we use Google Ads. A cookie from Google is stored for this purpose. For more information, read Google's privacy policy.
DoubleClick
For marketing purposes, we use DoubleClick. A cookie from Google is stored for this purpose. For more information, read Google's privacy policy.
| Name | Domain | Duration | Description |
|---|---|---|---|
| _fbp, fr | tuifly.be | 3 months | Used by Facebook to deliver a series of advertisement products |
| rsa | raptorsmartadvisor.com | 1 year | Used to provide personalised content based on the users click behaviour |
| 5882rsa | tuifly.be | 1 year | Reports the click behaviour of the personalised content |
| MUID | bing.com | 1 year | Used by Microsoft as a unique identifier, to link data from Bing to the behaviour of users on the website |
| MUIDB | bing.com | 1 year | Used by Microsoft as a unique identifier, to link data from Bing to the behaviour of users on the website |
| IDE | doubleclick.net | 1 year | Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads to |
| _gcl_au | tuifly.be | 3 months | |
| PushSubscriberStatus | tuifly.be | 1 year | Used to get the status of the push notifications subscriber |
| peclosed | tuifly.be | 1 year | Stores the value when subscription optin was closed |
| cck | tuifly.be | 5 years | Used to identify unique users and to provide more personalised content |
| _pinterest_ct_rt | ct.pinterest.com | 1 year | Registers which destinations and hotels a user views, to show relevant ads on Pinterest |
| _pinterest_sess | pinterest.com | 1 year | Registers which destinations and hotels a user views, to show relevant ads on Pinterest |
We might also use techniques such as pixels, which we don't refer to as cookies because they don't store information on your device. A pixel is an electronic file embedded into an email which allows us to see if the message was delivered, if and when you read it, and what you clicked on. We sometimes place these in marketing emails and newsletters. We use similar technology to get the same information about push notifications we send you, too.
We use Server-to-server tracking by generating and storing a unique identifier when you click a tracking link or are shown an advertisement. When you later make an action such as a website visit or a purchase, the unique identifier is matched. This allows us to monitor the effectiveness of our advertisement.
The following data points are shared with our partners Facebook and Google via server-to-server tracking to improve our marketing tracking and capabilities:
| Key Type: Key Name | Description |
|---|---|
| Email:em | An email address in lower case. Example joe@eg.com |
| Phone:ph | A phone number. Include only digits with country code, area code and number. Remove symbols, letters and any leading zeros. In addition, always include the country code as part of the customer phone number, even if all the data is from the same country, as the country code is used for matching. For example, the number 1 must always precede a phone number for the united states. Example 16505551212. |
| Last name:ln | A last name in lowercase. Example: smith. |
| First name:fn | A first name in lowercase. Example: joe. |
| Client IP adress: client_ip_address | The IP address of the browser corresponding to the event (HTTP headers) |
| Client user agent: client_user_agent | The IP address of the browser corresponding to the event. Note: this information is automatically added to events sent through the browser/ pixel, but must be manually configured to events sent through server. |
| Click ID:fbc | The Facebook click ID value stored in the _fbc browser cookie under your domain. See managing fbc and fbp parameters for how to get this value, or generate this value from a fbclid query parameter. |
| Browser ID:fbp | The Facebook browser ID value stored in the _fbp browser cookie under your domain. See Managing fbc and fbp Parameters for how to get this value. |