Information
| Description | This cookie assigns your device an anonymizing ID (session ID) for the duration of your visit. Multiple associated queries to the server can be bundled and assigned to one session. |
| Expiration Date | Session |
| Description | During newsletter registration, this cookie assigns your device an anonymizing ID (session ID) for the duration of your visit. Multiple associated queries to the server can be bundled and assigned to one session. |
| Expiration Date | Session |
| Description | This cookie stores a security token that protects the user session from access by unauthorized third parties. |
| Expiration Date | Session |
| Description | This cookie prevents the login dialog from being displayed again each time a page is visited. |
| Expiration Date | 1 year |
| Description | This cookie is used to restore the shopping cart. |
| Expiration Date | 2 years |
| Description | This cookie is used to restore the watch list. |
| Expiration Date | 2 years |
| Description | This cookie is used to restore the comparison list. |
| Expiration Date | 2 years |
| Description | This cookie is used to restore the sample list. |
| Expiration Date | 11 years and 5 months |
| Description | This cookie stores the consents given by a user. |
| Expiration Date | 1 year |
| Description | This cookie stores the last search term employed by the user. |
| Expiration Date | 10 years |
| Description | This cookie stores the server called by the user. This ensures that the data traffic and user data are transmitted to the correct locations in the event a website is hosted on multiple servers. |
| Expiration Date | Session |
| Description | This cookie stores information on whether the access comes from a WAGO IP address, in order to identify WAGO employees. |
| Expiration Date | 30 minutes |
| Description | This cookie is set by Cloudflare in order to identify the visitors to our website and deliberately block unwanted visitors. |
| Expiration Date | Session (expires after 30 days) |
| Description | This cookie is set in order to identify visitors who revisit our website. For instance, this can be used to resume an interrupted live chat smoothly. |
| Expiration Date | 3 months |
| Description | This cookie is set in order to ensure the original functionality of the live chat. |
| Expiration Date | Session |
| Description | This cookie is set in order to store further information about the activity status of the live chat. |
| Expiration Date | Session |
| Description | This cookie is set in order to store additional information on the live chat, which is not specified in more detail. |
| Expiration Date | Session |
| Description | This cookie is set in order to store information about the status of the live chat. |
| Expiration Date | Session |
| Description | This cookie is set in order to store information about the initialization of the live chat. |
| Expiration Date | Session |
| Description | This cookie is set in order to store the unique meta ID of the live chat. |
| Expiration Date | Session |
| Description | This cookie is set in order to store the number of messages sent to you by our employee during the live chat. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store information about the start of a chat slot. A live chat between a visitor to our website and one of our employees is referred to as a slot. An employee can be active in a maximum of ten chat slots at a time. |
| Expiration Date | Session |
| Description | This cookie is set in order to store the number of messages sent to you by our employee during the live chat. |
| Expiration Date | Session |
| Description | This cookie is set in order to store the email address you entered before the live chat. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store the unique ID of the live chat. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store the name you entered before the live chat. |
| Expiration Date | Session |
| Description | This cookie is set in order to store further information about the employee you spoke with in the live chat. Our employees in the live chats are also called operators. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store the unique ID of the employee you spoke with in the live chat. Our employees in the live chats are also called operators. |
| Expiration Date | Session |
| Description | This cookie is set in order to store the name of the employee you spoke with in the live chat. Our employees in the live chats are also called operators. |
| Expiration Date | Session |
| Description | This cookie is set in order to store the number of individual page views on our home page. The individual page views are also called “page impressions.” |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store the URL of the website through which you reached our website. This original website is also called the referrer. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store information on whether or not your Web browser supports cookies. |
| Expiration Date | Session |
| Description | This cookie is set in order to store the unique ID of the user of the live chat. This ID can be useful if a user temporarily leaves our website, for instance. |
| Expiration Date | Session |
| Description | This cookie is set in order to store the number of visits to our home page. A view of a website is also called a visit. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store settings for the graphic program window of the live chat. A graphic program window is also called a widget. |
| Expiration Date | Session |
| Description | This cookie is set in order to store a unique identifier of the graphic program window of the live chat. A graphic program window is also called a widget. |
| Expiration Date | Session |
| Description | These cookies enable Google Maps functionality. |
| Expiration Date | 1 minute |
| Description | This cookie is set in order to store the unique ID of the individual chat history. |
| Expiration Date | permanently |
| Description | This cookie is set in order to store the current session ID of the individual user. |
| Expiration Date | permanently |
| Description | Chat history |
| Expiration Date | permanently |
Statistics cookies help website owners understand how visitors interact with websites by anonymously collecting and reporting information.
| Description | This cookie is set in order to store a unique ID of the visitor and use it to identify the visitor on a subsequent visit to our website. |
| Expiration Date | 2 years |
| Description | This cookie is set in order to store your preferred settings for displaying the website, such as the language, region or number of search results per page. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store your consent to or rejection of Google cookies. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store a unique ID of the visitor and obtain information about user behavior on our website. |
| Expiration Date | 30 minutes |
| Description | This cookie throttles the Google request rate. |
| Expiration Date | 1 minute |
| Description | This cookie contains the Google Analytics account identification number or the website the cookie refers to. |
| Expiration Date | 2 years |
| Description | This cookie contains a token that can be used to retrieve a client ID from the AMP client ID service. |
| Expiration Date | 30 seconds to 1 year |
| Description | This cookie contains campaign-related information on the user. |
| Expiration Date | 90 days |
| Description | This cookie is used by Google Analytics to distinguish users and sessions. The cookie is created when the Javascript library is executed and no __utma cookies are present. The cookie is updated every time data is sent to Google Analytics. |
| Expiration Date | 2 years |
| Description | This cookie is set by Google Analytics and throttles the request rate. |
| Expiration Date | 10 minutes |
| Description | This cookie is set by Google Analytics for analysis of data traffic on our website. The cookie ascertains the length of a user’s visit and saves the start time of the visit. |
| Expiration Date | 30 minutes |
| Description | This cookie is set for interoperability with urchin.js. |
| Expiration Date | Session |
| Description | This cookie stores the source or campaign that describes how the user reached the website. The cookie is created every time the Javascript library is executed and updated every time data is sent to Google Analytics. |
| Expiration Date | 6 months |
| Description | This cookie stores variable user information in order to identify a user as part of a customer-specific user segment. |
| Expiration Date | 2 years |
| Description | This cookie is used by Google Analytics for aggregate analysis of website visitors. |
| Expiration Date | 1 month |
| Description | This cookie is set in order to store your consent to or rejection of Crazy Egg cookies. |
| Expiration Date | 1 year |
| Description | This cookie is set in order to store a unique ID of the visitor to our website. |
| Expiration Date | 30 minutes |
| Description | This cookie is set by the Crazy Egg service and tracks whether the user is a new user. |
| Expiration Date | 30 minutes |
| Description | This cookie contains the trbo user ID, which is randomly generated and anonymous. |
| Expiration Date | 33 years |
| Description | This cookie contains the user’s current session ID; a new session ID is collected each time. |
| Expiration Date | 30 minutes |
| Description | This cookie collects current user information, such as the number of sales, number of sessions, number of page views and length of stay. |
| Expiration Date | 30 minutes |
| Description | This cookie collects information on the current session, such as the start time, the number of page impressions in the session and the length of the stay in the session. |
| Expiration Date | 3 years |
| Description | This cookie is set in order to store information about user behavior on our website, including the time of the visit and the number of page impressions. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store information about user behavior on our website. |
| Expiration Date | 30 minutes |
| Description | The “Session ID Hashing and Query Parameters Matching a Session ID” cookie is installed when you start a survey session on the same browser on which you are working on another session. The cookie is used to store multiple sessions on the same browser. |
| Cookie value | Hash value of the session ID and query parameters associated with this session ID, e.g. pEUshJmmkmoqhFUWV9uNOhqJXuO%2FNbUoAtobPz4T3no%3D |
| Expiration date | Up to 1 year or when the session ends |
| Description | The QST cookie appears when the function “Avoid Participation Fraud” is enabled. It saves the conducted survey and prevents the user from conducting it again. |
| Cookie value | QST |
| Expiration date | 1 year |
| Description | The <SurveyID><StateData>-reloadSession cookie is intended for surveys that require a “SSO Authentication” This cookie tells Qualtrics which session to reload after the respondent leaves and returns. |
| Cookie value | <surveyid><statedata>-reloadSession |
| Expiration date | 15 minutes |
| Description | This cookie appears when you start a session with the “Save and Continue” option enabled. |
| Cookie value | FS_12345678~jfe2 |
| Expiration date | 5 minutes |
| Description | These cookies appear when you submit a survey session, even though the “Save and Continue” and “Avoid Participation Fraud” options are disabled in the survey options. |
| Cookie value | Survey ID (e.g., SV_12345678) |
| Expiration date | 6 months |
QST AND SESSION COOKIE BEHAVIOR: SURVEY WITH 2 OR MORE PAGES Whenever a survey is completed, a session cookie is installed with an expiration date that matches whatever is set for the “Partial Answers” in the survey options. For example, if my “Partial Responses” setting is set to 1 week, the survey will install a session cookie that expires one week after you click the survey link. This cookie allows Qualtrics to determine when a partial response should be saved as a response.
If the survey remains incomplete, this cookie will remain stored until it expires. However, when the survey is submitted, it will be converted into a QST (Qualtrics Survey Tracker) cookie. For surveys with 2 or more pages, the QST cookie will automatically expire 6 months after the survey start date.
QST COOKIE BEHAVIOR: ONE-PAGE SURVEY The QST cookie behaves slightly differently in a one-page survey. Since the survey consists of only one page, it is not possible to set a session cookie because the survey will be submitted. Therefore, the QST cookie that is installed after submission has a different expiration date than the one for surveys with two or more pages. Instead of a default date of 6 months after the survey started, the expiration date of the QST cookie corresponds to the setting for partial responses in the survey options. | |
| Description | This cookie tracks the URLs of the web pages a user has visited. The pages should contain the project deployment code for tracking to work properly. This cookie can be up to 2000 bytes in size, provided that no other value is set under “Maximum Cookie Size.” |
| Cookie value | QSI_HistorySessions |
| Expiration date | Duration of the browser session |
| Description | The cookie name is “QSI_S_{ZoneID}” and the value is {v|r}:{1}:{2},” where “v” stands for “Visitor Sampling” and “r” for “Request Sampling.” Variable 1 is the percentage (of individual visitors) and variable 2 is the number of website visits by the respective visitor. For example, {v:0:0} means that visitor samples are used and I was not included in the sample. {v:100:0} means that visitor samples are used and I am part of the sample. {r:10:45} means that request samples are used, 10% of the requests in the sample should be considered, and I have already started my 45th request. In this scenario, I should be sampled on my first visit and every 10th visit thereafter. |
| Cookie value | QSI_S_{ZoneID} |
| Expiration date | Persistent, 1 week |
| Description | This cookie tracks whether the intercept should be displayed on repeated visits by users. The format is QSI_SI_<id>_intercept (e.g., QSI_SI_5sPQdCDYVYwQRv_intercept). |
| Cookie value | QSI_SI_<id>_intercept |
| Expiration date | Persistent; expiration time according to intercept settings |
| Description | This cookie prevents too many windows from being opened. To do this, it first checks whether other pop-under are already displayed and prevents repeated display accordingly. This cookie has the QSIPopUnder_PopUnderTarget_SI_<id> format. Example: QSIPopUnder_PopUnderTarget_SI_1Y2DkewovNRaQRv. |
| Cookie value | QSIPopUnder_PopUnderTarget_SI_<id> |
| Expiration date | Session cookie (i.e., the cookie is removed after closing the browser or leaving the website.) |
| Description | If “Local Storage” is disabled, we store some other values in cookies. (see Support Page to the “Add/Modify Cookie” event). |
| Cookie value | These refer to the cookies created by the intercept. Therefore, the cookie name depends on the name defined in the settings. |
| Expiration date | Duration of the browser session |
Intercept Targeting
| Description | This value contains the Unix timestamp of all intercept impressions of the domain. These timestamps are used to decide whether or not to display another intercept when evaluating intercept logic. The value is a JSON object with a siid as the key and a timestamp as the value. |
| Cookie value | Q_INTER |
| Expiration date | Permanent – Q_INTER is only removed when the browser is reset or when the web page data is deleted. |
Updating the embedded data in the pop-under when leaving the website
| Description | This value contains the intercept ID of each pop-under opened by this intercept. When navigating, this ID is then used to update the embedded data of the pop-under (unLoad). |
| Cookie value | QSI_OptInIDsAndWindowNames |
| Expiration date | Duration of the browser session |
Marketing cookies are used in order to follow visitors on websites. The intention is to display ads that are relevant and appealing to the individual user and consequently more valuable for publishers and third-party advertisers.
| Description | This cookie is set in order to store a unique ID of the visitor. |
| Expiration Date | Session/3 months |
| Description | This cookie is set in order to identify the Web browser you are using, independent of the user who is signed in. It is used to enhance security. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to store a unique ID of the visitor and a unique ID of the Web browser. |
| Expiration Date | 3 months |
| Description | This cookie is set in order to store your chat status. |
| Expiration Date | Session |
| Description | This cookie is set in order to store your chat status. |
| Expiration Date | 30 minutes |
| Description | This cookie is set by Facebook. |
| Expiration Date | 1 day |
| Description | This cookie is set in order to store various information about the current session. |
| Expiration Date | Session/3 months |
| Description | This cookie is set by Facebook in order to distinguish individual visitors to our website, to detect their user behavior and to display targeted advertising on this basis. |
| Expiration Date | 3 months |
| Description | This cookie is set in order to monitor the use of embedded utility software. |
| Expiration Date | 1 year |
| Description | This cookie is set in order to monitor the use of embedded utility software. |
| Expiration Date | 1 day |
| Description | This cookie is set in order to store the website language you selected. |
| Expiration Date | 30 minutes |
| Description | This cookie is set in order to allow login via LinkedIn. |
| Expiration Date | 2 years |
| Description | This cookie is set in order to display ads that are even more specifically targeted to website visitors. |
| Expiration Date | 6 months |
| Description | This cookie is set in order to store a unique ID of the user and to use it to obtain information about user behavior. |
| Expiration Date | 1 year |
| Description | This cookie is set in order to obtain information about user behavior and use it to display targeted ads. |
| Expiration Date | Session |
| Description | This cookie is set in order to obtain information about user behavior and use it to display targeted ads. |
| Expiration Date | 16 days |
| Description | This cookie is set in order to display advertising at various locations on the Internet. IDE is a relevant cookie for ad preferences for websites which do not belong to Google. |
| Expiration Date | 1 year |
| Description | This cookie is set in order to link your activities to different devices and use it to display ads that are even more specifically targeted. |
| Expiration Date | 1 year |
| Description | This cookie is set by Google AdSense in order to optimize the efficiency of the displayed ads. |
| Expiration Date | 3 months |
| Description | This cookie is set in order to obtain information about user behavior on our website and use it to display targeted ads. |
| Expiration Date | 1 month |
| Description | This cookie is set in order to obtain information about user behavior on our website and use it to display targeted ads. |
| Expiration Date | 1 day |
| Description | This cookie is used for advertising on Google and exchanges data anonymously. |
| Expiration Date | 1 year |
| Description | This cookie is generally set by advertising partners, who use it to create a profile of the website visitor’s interests and show relevant ads on other websites. |
| Expiration Date | 2 years |
| Description | These cookies store the Google account ID and the user’s last login time in a digitally signed and encrypted form. They are meant to prevent fraudulent use of login information and protect user data against unauthorized access. |
| Expiration Date | 1–2 years |
| Description | These cookies are used to create a profile of the website visitor’s interests in order to show relevant personalized Google ads. |
| Expiration Date | 1–2 years |
| Description | This cookie is set by Baidu and is used to analyze our website, particularly the frequency of queries. |
| Expiration Date | Session |
| Description | This cookie is set by Baidu and assigns a unique ID to your device for the duration of your visit in order to obtain information about user behavior on our website. |
| Expiration Date | 30 minutes |
| Description | With your consent, we share some data with SAP Marketing Cloud about your user behavior on our website in order to allow individualized experiences. This lets us offer personalized campaigns based on your needs. |
| Expiration Date | Until consent is revoked |
| Description | This cookie is used to store some details about the user, such as the unique visitor ID. |
| Expiration Date | 13 months |