Cookies with explicit consent: implementation guide

iAdvize has released a new feature on its JS Tag that enables businesses to better handle the visitor consent and cookie deposit.

The key benefits of this new solution for businesses are:

  • To propose conversational engagement to 100% of your visitors (even when they do not consent to iAdvize cookies)
  • To ensure compliancy to the latest CNIL recommandations

Once this new feature is activated by the Business, the iAdvize JS tag will no longer automatically place a cookie on the Visitor’s browser by default.

The consequence is that whatever the visitor's consent, they will always be eligible for iAdvize engagement and may be proposed to chat.

  • Visitors who opt-in will receive a Cookie immediately, and iAdvize will collect useful data concerning their browsing and potential purchase, as before.
  • Visitors who do not opt-in will not have a cookie deposited until they start a conversation and therefore iAdvize will not track any browsing or purchase data from them.

NB: As iAdvize won’t collect data from Visitors who do not opt-in, note that some targeting criteria won’t be functioning anymore for such population (number of page views, Browsing time on website, previous page, time elapsed since last visit, visits, referral, probability from Smart Targeting features, scoring criteria), as well as these visitors won’t be included anymore in any Incremental testing measures.





1. Technical implementation

Step 1: add the "explicit cookies consent” mode in the iAdvize tag

To benefit from the explicit cookie consent :

1.1. The implementation of the iAdvize tag must be reviewed on your website, in order to add an additional parameter useExplicitCookiesConsent with the value true.

The implementation below replaces the code you were currently using on your pages.

NB: The implementation is evolving, but the iAdvize code that will be loaded and its performance remain unchanged.

This implementation does not automatically drop cookies on your site anymore, so you must now drop this tag on all your pages, without worrying about the visitor's consent. This code must therefore be executed as soon as a new visitor arrives on the site.

T.src=i+'?'+Object.keys(e).map(function(x){return x+'='+e[x]}).join('&');
  sid: 9999,
  useExplicitCookiesConsent: true

⚠️ If your account is on the Standard platform, please replace "//" by "//"

⚠️ This is an example of a SID: 9999. Please fill in your SID.

Available parameters:

Default value
Your project / website ID
Language of the livechat used for the display of chat elements in a given language.
Browser language
If true, this tag will no longer automatically sets a cookie on the visitor’s browsers by default. The cookie  vuid  is only implemented after the visitor has provided his explicit content, when accepting the GDPR consent at the beginning of a conversation. 


1.2. Activating consent is highly recommended within the iAdvize administration


Thus, if a visitor refuses cookies from your site, he will still have access to information related to the cookies installed by iAdvize that are essential to start a conversation.


Step 2: set up an additional script to indicate the visitor consent on the cookie banner

In order to enable all visitor who have consented to the iAdvize cookie deposit, you will have to differentiate the audiences.

You will have to call a simple additional script when a visitor communicates its consent on the cookie consent banner of your website.

⚠️ You will need to add / run the following script each time the user sets or updates their consent.

When the
visitor gives his consent you must pass as second parameter true and when the visitor refuses to give his consent, you must pass as second parameter false :

Example with a visitor who gives consent:

// true or false depending on the visitor's consent
iAdvizeInterface('setVisitorCookiesConsent', true);



iAdvize sets an expiration date by default of 12 months for the cookie (renewable each time the visitor starts a chat on iAdvize). You can customize this expiration date by adding a third parameter expressed in seconds.


// Here an example for a year (3600*24*365)
iAdvizeInterface('setVisitorCookiesConsent', true, 31536000);


To go further :

  • As a visitor who already had an iAdvize conversation and now refuses cookies: the cookie will be cleaned and so, the visitor will lose access to its conversation history
  • There is no impact on the tag performance with this new parameter
  • Transaction tag: how it works? No difference
  • Custom data tag: how it works? Custom data present in the page will be available for the targeting engine, however, custom data on the previous pages for a visitor that did not consent won’t be available for the targeting engine
  • Duration of consent: starting a conversation extends the lifetime of the iAdvize cookie, to guarantee access to the conversation to the visitor
  • Duration is still 1 year

2. Admin setup for GDPR consent

2 sections have been added in the Settings > Privacy > GDPR tab to allow the visitor to specify that an iAdvize cookie will be set when accepting the GDPR banner at the start of the conversation.

Both sections are customizable.

Section 1: Personalize the message when opening the chatbox

Default message:
[ENG] "To support you to the best of our ability, we use a conversational cookie and keep a history of that conversation. We also have access to your site navigation."

Engagement > Setting > Privacy > Display of legal information



This message will be visible in the preview of the GDPR inside the chatbox.



Section 2: Enter your legal info

A section dedicated to cookie has been added “Cookie deposit” and can be customizable. 
To make it appear you will need to update the GDPR page.

Default message:

[ENG] The cookie (vuID) that we deposit on your browser is technically necessary for the display and provision of the chat service (exchange with an agent or a chatbot). It is also used to store the language used, the number of pages viewed, the browsing time and the time of connection, and the browser type, and their URL."