Privacy consent

Foreword

In order to respect the privacy of users and follow regulations different countries, tracker allows you disable user tracking.

This feature is available since version 5.16.0

Management of the client idclient before consent

Since version 5.16.0, the tracker has had a global method ATInternet.Utils.consentReceived  enabling a specific user data processing mode on the first page of the site (or consent page). Enabling this mode causes the generation of a hit containing a idclient correctly formatted (guid) and it not being saved on the browser. In this way, we guarantee that the data will not be tracked while keeping a useful identifier for the measurement.

Three scenarios are thus possible:

• The user leaves the site on the first page:
  • When the first page is loaded, a hit containing idclient is sent without the information being stored on the browser.
  • If the user returns later to the site, a new idclient will then be generated.
• The Internet user continues to navigate:
  • When the first page is loaded, a hit containing idclient is sent without the information being stored on the browser.
  • The generated idclient can be retrieved using the function tag.clientsideuserid.get() and then added as a parameter in any URL leading to navigation on the site (clicking on a link, etc.).
  • After retrieving the parameter from destination page, it can be saved using function tag.clientSideUserId.set(idclient) to ensure the continuity of the measurement. See Unique visitor identification for more details.
• The Internet user gives his consent on the first page (banner, etc.)
  • It is possible to force the storage of idclient after obtaining user consent by using the function tag.clientSideUserId.store()

Examples

1. Mode activation

   ATInternet.Utils.consentReceived(false);
   var tag = new ATInternet.Tracker.Tag();
   tag.page.set({
       name:'pageName',
       customObject: {
           MyPageLabel:'my_page',
           MyChapters: {level1:'my_chapter1', level2:'my_sub_chapter1', level3:'my_sub_chapter2' }
       }
   });
   tag.dispatch();

2. Recovering the client idc

   var idclient = tag.clientSideUserId.get();
   

3. Forced storage of the client idclient after consent

   tag.clientSideUserId.store();