Cookie Policy

Used to determine whether or not a user has seen the cookie preference management banner.

Used to determine whether or not a user has interacted with the cookie preference management module.

Used to determine whether or not a user has given consent for the different categories of cookies.

Remembers rules set by an administrator to hide a chat invite button after a visitor has accepted or rejected it. Without the cookie, the button appears repeatedly when triggered.

Captures a unique pseudonymous identifier when a user requests a chat during an active session. The agent will not know if a user browses to offer specific advice without the cookie.

Captures where the user requests a chat from during an active session. Without this cookie, the agent will not know where a user is browsing to offer tailored advice.

Counts a user's distinct browsing sessions on your website after previous sessions have been closed. Without this cookie, the agent will not see this information.

Captures how visitors come to your website from search results or affiliate links. This information will not be available to agents without the cookie.

Links a single visitor's previous chats and transcripts. For chats without this cookie, new LiveChatVisitor records or a new LiveChatTranscript are created each time for the same visitor.

Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in.

Stores the last utm_campaign query parameter.

This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. Moer info on Hotjar cookies can be found at https://help.hotjar.com/hc/en-us/articles/115011789248-Hotjar-Cookies

This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.

This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.

This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.

Used to distinguish users (in the anonymised sense of the term, i.e. a web browser (like Google Chrome) and not a real person)

Used to distinguish users (in the anonymised sense of the term, i.e. a web browser (like Google Chrome) and not a real person).

Allows you to keep the session state.

Contains campaign information. If you have linked your Google Analytics and Google Ads accounts, conversion tags on Google Ads websites read this cookie unless you have disabled its use. More info: https://support.google.com/google-ads/answer/7521212

Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.

Used to throttle request rate when Google Analytics is deployed via Google Tag Manager.

Ce cookie enregistre le nombre de points dans le nom de domaine de premier niveau, à savoir «2» pour www.volkswagen.fr et «3» pour www.volkswagen.co.uk.

Ce cookie stocke des informations sur l'utilisateur - par exemple une chaîne d'identification d'utilisateur générique, l'étape de désactivation du suivi, etc... - et est utilisé pour identifier les visiteurs qui reviennent.

Ce cookie stocke "1" pendant la session active.

Ce cookie est défini et lu par le code JavaScript pour déterminer si les cookies sont activés (simplement mis à "true").

Ce cookie stocke si l'utilisateur visite le site pour la première fois; les valeurs sont vraies ou fausses.

Ce cookie est défini et lu par le code JavaScript lorsque la fonctionnalité ClickMap et la fonctionnalité Activity Map sont activées; il contient des informations sur le lien précédent sur lequel l'utilisateur a cliqué.

Ce cookie stocke un horodatage et le numéro de visite.

Ce cookie stocke le nom de la page précédente.

Le cookie conserve un certain nombre de valeurs pour gérer la façon dont l'expérience utilisateur fait des campagnes comme un identifiant de session et un identifiant de navigateur semi-permanent.

Effectue le suivi du serveur périphérique Adobe Target actuellement utilisé.

Ce cookie stocke une chaîne d'informations comme un identifiant de visiteur générique, l'étape de désactivation du suivi, etc. Les informations de ce cookie seront copiées dans le cookie de première partie "AMCV_ *" pour reconnaître les paramètres de l'utilisateur pour sa prochaine visite.

Ce cookie stocke l'horodatage du dernier appel de synchronisation avec le service "Demdex".

Ce cookie stocke les informations qu'un identifiant d'utilisateur a été demandé.

Ce cookie est défini par le domaine du client une fois le cookie AMCV défini par le client. Le but de ce cookie est de permettre le suivi persistant des identifiants dans l'état de première partie et est utilisé comme identifiant de référence si le cookie AMCV a expiré. 

UUID to identify a user.

Tracks the number of user sessions in the browser.

Timestamp indicating when the user logged in.

Number between 0-1 used for user targeting percentage.

Indicates whether an interception was presented in the session.

Timestamp indicating when the page was loaded. Used for time-on-page targeting.

Tracks the number of pages viewed by the user in the session.

Instructs Medallia code to add debug logs to the browser console.

Used to distinguish users (in the anonymised sense of the term, i.e. a web browser (like Google Chrome) and not a real person)

Used to distinguish users (in the anonymised sense of the term, i.e. a web browser (like Google Chrome) and not a real person)

Stores technical user data.

Stores Session Replay data.

Stores user consent on use of session data use within replays (not masked vs. full masked).

Stores the URL-encoded custom variables from the session.

When set, the user is excluded from tracking.

When set, the user is opted-out from tracking.

Checks if the browser supports cookies and sets flags.

Check if the browser supports the SameSite flag.

Stores the URI-encoded main domain name of the site.

 Enables/disables specific behavior of the Tag for debugging purposes.

This is a unique user ID token. WEBSITE_ID is dynamic and corresponds to the ConvertFlow website ID of the installed ConvertFlow script.

This is the winning variation of the CTA split test. WEBSITEID is dynamic and corresponds to the ConvertFlow website ID of the installed ConvertFlow script. CTA_ID is dynamic and corresponds to the CTA campaign.

Indicates when the visitor's tracking record was last retrieved from our tracking database.

Locally stored visitor tracking record.

Forces CF to retrieve the visitor's tracking record from the tracking database on the next visit to the page.

Indicates that the CTA has been closed so that it can be deleted for the set number of days.

Timestamp of when we stored the CTA information in local storage after loading it from our CDN.

Visitor tracking record stored locally.

This cookie carries out information about the ad being clicked to attribute conversions outside of a landing page.

This cookie 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.

This cookie is used to link user activity across devices if he has previously signed in to his Google Account on another device to coordinate the ads he sees across devices and measure conversion events. More info can be found at https://policies.google.com/technologies/ads and https://support.google.com/admanager/answer/2839090?hl=en#

This cookie 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.

This cookie is used to link user activity across devices if he has previously signed in to his Google Account on another device to coordinate the ads he sees across devices and measure conversion events. More info can be found at https://policies.google.com/technologies/ads and https://support.google.com/admanager/answer/2839090?hl=en#

This cookie 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. More info can be found at https://policies.google.com/technologies/ads and https://support.google.com/admanager/answer/2839090?hl=en#

This cookie contains a unique ID Google uses to remember your preferences and other information. More info can be found at https://policies.google.com/technologies/ads and https://support.google.com/admanager/answer/2839090?hl=en#

This cookie is used by Bing to determine what ads should be shown that may be relevant to the end user using the site.

This cookie is used by Bing to determine what ads should be shown that may be relevant to the end user using the site.

Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.

This cookie is used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.

TFPSI stands for Teads First Party Session ID. It allows to correlate all the events of a user to form a session (regardless of whether the user comes from a Teads ad or not). This cookie allows for a more accurate and reliable measurement and helps us improve our session statistics (qualified visit rate, pages viewed, etc.). It also helps us to capture and categorize traffic in a better way. It is automatically generated and has a lifespan of 30 minutes. It can be renewed for 30 minutes.

TFPAI stands for Teads First Party Auction ID. It allows a user's click on an ad to be correlated with their visit to a website. The CLICK ID (AuctID) is transferred to the site via URL decoration and its value is stored in a cookie.

This cookie is installed by Outbrain in order to measure the use of the website for internal analytics.

This cookie is installed by Outbrain to set up attribution of the visits of the user in order to measure Marketing campaigns.

This cookie is installed by Outbrain to set up attribution of the session of the user in order to measure Marketing campaigns.

Outbrain conversion tracking.

Used by LinkedIn Insight Tag to enable in-depth campaign reporting and discover new business demographics by layering LinkedIn data to website visitors data

Used by LinkedIn Insight Tag to enable in-depth campaign reporting and discover new business demographics by layering LinkedIn data to website visitors data.

Used by LinkedIn Insight Tag to enable in-depth campaign reporting and discover new business demographics by layering LinkedIn data to website visitors data

Used by LinkedIn Insight Tag to enable in-depth campaign reporting and discover new business demographics by layering LinkedIn data to website visitors data

Used by LinkedIn Insight Tag to enable in-depth campaign reporting and discover new business demographics by layering LinkedIn data to website visitors data.

Used by LinkedIn Insight Tag for Browser Identifier

Used by LinkedIn Insight Tag for Browser Identifier

Permet de mesurer les résultats des campagnes.

Permet de mesurer les résultats des campagnes 

Sécurité et publicité

Permet de mesurer les résultats des campagnes

Permet de mesurer les résultats des campagnes.

Permet de mesurer les résultats des campagnes.

Permet de mesurer les résultats des campagnes

Permet de mesurer les résultats des campagnes.

Permet de mesurer les résultats des campagnes. 

Permet de mesurer les résultats des campagnes.

Permet le suivi des utilisateurs afin de diffuser de la publicité.

This cookie is created when a campaign objective is triggered. This cookie, once created, will always have a value of 1.

This cookie is created to detect whether or not cookies are enabled on the visitor's browser. It also helps in tracking the number of browsing sessions completed by a visitor. The value of this cookie is always 1.

This cookie is created when a visitor is chosen for a particular variation of a test. This cookie ensures that visitors see the same variation when they revisit the page in the future. Here, the control has a value of 1, variation #1 has a value of 2, variation #2 has a value of 3, and so on.

This cookie is created when a visitor has been excluded from a test campaign due to traffic percentage specifications. The value is always 1.

This cookie tracks the session created for a visitor, i.e. the number of times the browser was closed and reopened. The value is >=1, followed by a vertical bar sign. For example, the value 2 indicates that the visitor restarted the browser once while 3 means twice.

This cookie tracks the session created for a visitor, i.e. the number of times the browser was closed and reopened. The value is >=1, followed by a vertical bar sign. For example, the value 2 indicates that the visitor restarted the browser once while 3 means twice.

This cookie generates a unique ID for each visitor and is used for the reporting segmentation functionality in VWO, and it also allows you to view the data in a more refined way.

This cookie is created for each cross-domain campaign. It generates a unique ID for each visitor and is used for reporting segmentation functionality in VWO. It also allows you to visualize the data in a more refined way.

This cookie stores persistent visitor-level data for VWO Insights.

This cookie stores information at the session level.

This cookie calculates unique traffic to a website.

This cookie stores the chosen combination. This is a temporary cookie that is deleted when campaign changes are applied.

This cookie stores the chosen combination. This is a temporary cookie that is deleted when campaign changes are applied.

This cookie is a jar of all cookies. It is currently created only for the Safari browser. In the future, it would replace all cookies. The actual expiration of a cookie does not matter because it stores the expiration of cookies set there and continues to expire them.

This cookie is retained when a visitor unsubscribes from vwo across all websites in a given browser.

This cookie is used for testing purposes and is only created on sites using the HTTP protocol. This is used to check whether VWO can set cookies on them, after which this cookie is deleted.

This cookie is created when a campaign objective is triggered. Once created, this cookie always has the value 1.

This cookie is created when a campaign objective is triggered. Once created, this cookie always has the value 1.

This cookie is created when a visitor is chosen for a particular variation of a test. This ensures that visitors see the same variation when they revisit the page. Here, the control always has the value 1, variation #1 always has the value 2, variation #2 has the value 3, and so on.

This cookie is created when a visitor has been excluded from a campaign due to traffic percentage specifications. The value of this cookie is always 1.

This cookie is created when a visitor has been excluded from a campaign due to traffic percentage specifications. The value of this cookie is always 1.

This cookie is created when one of the variations is chosen for the visitor, but the visitor is not yet redirected to the variation page. With this, VWO verifies that the variant page matches the chosen variant after landing on the page. The value will always be >=2 because it will not be created if the control is chosen.

This cookie is created for each cross-domain campaign. It generates a unique ID for each visitor and is used for reporting segmentation functionality in VWO. It also allows you to visualize the data in a refined way.

This cookie stores the chosen combination. This is a temporary cookie that is deleted when campaign changes are applied.

This cookie is retained when a visitor unsubscribes from vwo across all websites in a given browser. 

This cookie is created when a test campaign objective is triggered. This cookie, once created, will always have the value 1.

This cookie is created to detect whether or not cookies are enabled on the visitor's browser. It also helps in tracking the number of browsing sessions completed by a visitor. The value of this cookie is always 1.

This cookie is generated when you switch variations in preview mode

This cookie is created when a visitor is chosen for a particular variation for a test. This cookie ensures that visitors see the same variation when they revisit the page in the future. Here the Control always has the value of 1, Variation #1 always has the value of 2, and Variation #2 has a value of 3, and so on.

This cookie stores referral info allowing VWO to identify the original Traffic source in case of the Split URL campaign.

This cookie persists the selection by the person using previews.

This cookie is created when a visitor has been excluded from a Test Campaign due to the traffic percentage specifications. The value is always 1.

This cookie is created when one of the variations is chosen for the visitor, but the visitor is not yet redirected to the variation page. It exists so that VWO can verify that the variation page corresponds to the chosen variation after landing on the page. The value is >=2. As 1 corresponds to control and it’s not created if control is chosen.

This cookie generates a unique id for every visitor and is used for the report segmentation feature in VWO, and it also allows you to view data in a more refined manner.

This cookie stores persistent visitor-level data for VWO Insights. 

This cookie stores session-level information

This cookie stores the chosen combination. It’s a temporary cookie that gets deleted when the campaign changes are applied

The Criteo ID cookie; it contains the unique user identifier (UUIDv4) on the Criteo network.

The opt-out cookie; if present the user will not be tracked and retargeted by Criteo in that browsing session.

The pass-back loop detection cookie; it contains a counter of the times the user is passed on one specific zone.

The external ID cookie; it contains the user ID of our partners. It is used for the reselling of PUMP inventory.

Opt out advertiser or publisher or temporary. We continue on tracking users on the other advertisers/publishers.

Cookie used for Identification on Safari < 11.2.

This cookie helps Criteo better manage the tracking solution.

Created only when the User graph is activated for the client, it helps Criteo's tracking solution. 390 days

This cookie helps Criteo better manage the tracking solution.

This cookie helps Criteo better manage the tracking solution.

Assigns a unique user ID that Taboola uses for attribution and reporting purposes, and to tailor recommendations to that specific user.

Ogury is used for storing clicks data and their propagation in post-click events.

Used to indicate whether a user’s cookie ID has been synced with advertising partners, enabling data sharing for targeted advertising.

Helps control ad frequency and relevance by storing how often and recently ads have been shown to a user.

Part of a Chrome Privacy Sandbox test, this cookie tracks user participation in experimental groups and will be phased out after the experiment.

Stores unique identifiers that help Prebid Server partners recognize devices for ad targeting and performance tracking.

Indicates whether a user’s ID is synchronized with advertising partners to support cross-platform ad targeting.

Assigns a unique ID to browsers/devices to support interest-based advertising and performance tracking, including data matching with external sources; replaced with “-1” if a user opts out of behavioral ads.