FEB uses cookies to improve the interactivity and content of its website and the quality of its services.
What are cookies?
Cookies are small information files that are sent to your browser by the website you are connecting to. Your browser retains each cookie for a specific period of time. Every time you return to the same website, your browser sends the cookie(s) back to it. This enables the website to recognise your browser. Cookies can be used for different purposes, for example to remember your language preference, to ensure the good graphical appearance of the website or the correct functioning of a web application, to trace your navigation for statistical and advertising purposes, etc.
Duration
Cookies generally have an expiration date. For example, some cookies disappear automatically when you close your browser (session cookies), while others stay on your computer for longer, sometimes even until you delete them manually (persistent cookies).
Types of cookies
Internal cookies (these cookies are installed for and/or by FEB)
The FEB website installs three types of cookies in your browser:
- Technical cookies
Technical cookies are needed for purely technical reasons in connection with using the website. These cookies are installed as soon as you connect to the FEB website. - Functional cookies
Functional cookies ensure that the FEB website functions optimally. You can reject them or eliminate them via the settings in your browser, but your navigation experience will be noticeably degraded. - Analytical cookies
Analytical cookies are used to analyse certain characteristics, such as the number of visits to the website, to a specific page or to an advertising message. We use this information solely to improve the content of our website or to launch a new campaign on a certain topic that attracts a lot of interest.
The use of analytical cookies requires your prior authorisation. In other words, you can refuse to allow these cookies to be installed on your device.
Third-party cookies to improve website interactivity
The FEB website uses features offered by third parties such as Google, YouTube, LinkedIn and Facebook. These features use third-party cookies which may be installed directly by these services when you visit the FEB website. You will find more information on the various third-party cookies in the list of third-party cookies.
Set and manage your cookie preferences
When you first visit www.feb.be, a banner will inform you of the presence of cookies and will invite you to indicate which cookies you accept or refuse. Functional, analytical and third-party cookies are only installed if you accept them.
You can consult and modify your preferences for our site at any time via the Cookie Management page, a link to which you can find at the bottom of every page on our website.
List of cookies installed for and/or by FEB
Technical cookies
These cookies are installed in any case when you visit the FEB website.
Name | Expires after | Purpose | Information source |
ASP.NET_SessionId | end of browsing session | Used to uniquely identify a browser with session data on the server. | Link |
__zlcmid | 1 year | Store visitor’s machine-id for the Chat widget’s authentication. | Link |
CookieLevelAccepted | 1 year | Keep track of the cookie choice of a visitor. | Not applicable |
Functional cookies
These cookies improve your user experience on the FEB website. They are only installed with your consent.
FEB does not currently install any functional cookies itself (first party). Functional cookies that may be installed by third parties with your consent are listed under the heading third-party cookies.
Analytical cookies
Cookies enable FEB to analyse certain aspects (described in detail below for each cookie). They are only installed with your consent.
Name | Expires after | Purpose | Information source |
cusid | 30 minutes | This cookie is used to establish and continue a user session with the site. When a user views a page on the site, the script code attempts to update this cookie. If it does not find the cookie, a new one is written and a new session is established. Each time a user visits a different page on the site, this cookie is updated to expire in 30 minutes, thus continuing a single session for as long as user activity continues within 30-minute intervals. This cookie expires when a user pauses on a page on the site for longer than 30 minutes. | Link |
Cuvid | 2 years | This cookie is typically written to the browser upon the first visit to the site from that web browser. If the cookie has been deleted by the browser operator, and the browser subsequently visits the site, a new __cuid cookie is written with a different visitor unique ID. This cookie is used to determine unique visitors to the site and it is updated with each page view. Additionally, this cookie is provided with a unique ID that the application uses to ensure both the validity and accessibility of the cookie as an extra security measure. | Link |
Cuvon | 30 minutes | Used to signal the last time a visitor viewed a page. | Link |
Gdyn | 4.5 years | The file contains the expression hit.gemius.pl and protects internet users against overscheduled displays of the questionnaire for research purposes as described above. After appropriate modification of the expression included in the file, it is used to block displays of the questionnaire. NOTE: the blockage is not effective if the file is removed. | Link |
netpanel_path | 4.5 years | The file is saved on your computer upon filling in the questionnaire. It is used to enable correct access to the netPanel software to those internet users who are invited and decide to take full part in our Research and install the software on their computers. | Link |
UAAddOn | 4.5 years | The file contains the expression hit.gemius.pl, a unique number of Research participant and netPanel serial number (if installed). It is used to identify the origin of data; it is absolutely impossible to establish any personal data of Research participants based on these numbers. | Link |
__utma | 2 years | Used to distinguish users and sessions. The cookie is updated every time data is sent to Google Analytics. | Link |
__utmb | 30 minutes | Used to determine new sessions/visits. The cookie is updated every time data is sent to Google Analytics. | Link |
__utmc | end of browsing session | This cookie operates in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. | Link |
__utmt | 10 minutes | Used to throttle request rate. | Link |
__utmv | 2 years | Used to store visitor-level custom variable data. The cookie is updated every time data is sent to Google Analytics. | Link |
__utmz | 6 months | Stores the traffic source or campaign that explains how the user reached your site. | Link |
_ga | 2 years | Used to distinguish users. | Link |
_gat | 1 minute | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. | Link |
_gid | 24 hours | Used to distinguish users. | Link |
List of third-party cookies
Functional third-party cookies
Name | Expires after | Name of third party (cookie owner) | Purpose | Information source |
1P_JAR | 1 month | Google DoubleClick / Google Ads | Carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website. | Link |
CONSENT | 18 years old | Google DoubleClick / Google Ads | Carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website. | Link |
HSID | 2 years | YouTube | Collect user information for videos hosted by YouTube. | Link |
SSID | 2 years | YouTube | Collect user information for videos hosted by YouTube. | Link |
Third-party analytical cookies
Name | Expires after | Name of third party (cookie owner) | Purpose | Information source |
_fbp | 3 months | Helps deliver advertising to people who have already visited the website when they are on Facebook or a digital platform powered by Facebook Advertising. | Link | |
__gac | Google DoubleClick / Google Ads | Serve purposes such as measuring interactions with the ads on that domain and preventing the same ads from being shown to you too many times. | Link | |
__gads | 2 years | Google DoubleClick / Google Ads | Serve purposes such as measuring interactions with the ads on that domain and preventing the same ads from being shown to you too many times. | Link |
__gcl | 3 months | Google DoubleClick / Google Ads | Help advertisers determine how many times people who click on their ads end up taking an action on their site (e.g. making a purchase). | Link |
__gfp_64b | 2 years | Google DoubleClick / Google Ads | Advertising across the web. | Link |
ANID | 1 year | Google DoubleClick / Google Ads | Advertising across the web. | Link |
APISID | 2 years | Google DoubleClick / Google Ads | Used to build a profile of the website visitor’s interests and show relevant ads on other sites. | Link |
DSID | 2 weeks | Google DoubleClick / Google Ads | Advertising across the web. | Link |
IDE | 6 months | Google DoubleClick / Google Ads | Advertising across the web. | Link |
NID | 6 months | Google DoubleClick / Google Ads | Helps customize ads on Google properties, like Google Search. | Link |
SID | 2 years | Google DoubleClick / Google Ads | Helps customize ads on Google properties, like Google Search. | Link |
_guid | 3 months | Browser Identifier for Google Ads. | Link | |
bcookie | 2 years | Browser ID cookie. | Link | |
BizographicsOptOut | 10 years | Determine opt-out status for 3rd party tracking. | Link | |
bscookie | 2 years | Secure Browser Cookie. | Link | |
lang | end of browsing session | Sets default locale/language. | Link | |
li_fat_id | 1 month | Member indirect identifier for conversion tracking, retargeting, analytics. | Link | |
li_sugr | 3 months | Browser Identifier. | Link | |
lidc | 1 day | Used for routing. | Link | |
li-oatml | 1 month | Member indirect identifier for conversion tracking, retargeting, analytics. | Link | |
U | 3 months | Browser Identifier. | Link | |
UserMatchHistory | 30 days | LinkedIn Ads ID syncing. | Link | |
SAPISID | 10 years | YouTube | Collect user information for videos hosted by YouTube. | Link |
How can I see which cookies have been installed on my device and how can I delete them?
If you want to know which cookies are installed on your device or if you want to delete them, you can use a setting in your browser. Follow the links below to find explanations on how to do this for various browsers.
Changes to this cookie policy
FEB reserves the right to change this cookie policy at any time, in accordance with the General Data Protection Regulation. This cookie policy was last changed on 27 November 2023.
We have only limited content available in English.
You are viewing the English version of the VBO/FEB site.
If you are interested in our full content (economic news, publications, …), we advise you to visit the Dutch or French version of our site.
What do you want to do?
- Continue in English for limited content.
- Ga verder in het Nederlands voor alle inhoud.
- Continuer en français pour le contenu complet.