Definition
Until consent is given (opt-in), visitors have ‘opt-out’ status, excluded from general traffic, anonymised and visible only in the Privacy analysis under the ‘opt-out’ category.
Once opt-in status is obtained (consent), all data may be transmitted.
An additional marking method prevents any hits from being sent when visitors have opt-out status. This may be used when you do not wish your visitors to see information in their browser console.
However, you will not obtain any anonymised measurement.
Important
This setting can be applied to any site with audience measurement, provided that you inform users of the implications of opt-in status when displaying this choice.
Advantages
The ‘opt-out by default’ setting implies that visitors are not duplicated prior to consent.
Risks
The ‘opt-out by default’ setting implies that visitors are not measured prior to consent, and thus the first pages visited or bounce visits are not taken into account.
As the visit source is contained in the first event, you will not be able to collect this data for the first visits on the site (until opt-in).
This may imply that a lot of visits will be classified as direct access source.
Furthermore, in the Privacy analysis, you will not be able to separate traffic with visitors who explicitly requested not to be tracked (opt-out) from those who have not yet given their consent.
In this regard, the "no-consent by default" method is more appropriate.
Expected behaviour
To comply with your users’ wishes, you must be able to modify the state of consent at any time of the visit.
| Step | Description | |
|
Arrival on the site |
All cookies are defined with the OPT-OUT value. |
|
|
Visitor chooses |
Visitor identification is authorised and dedicated cookies may be placed (idrxvr,atidx,atid or atuserid) |
|
Tag configuration
The ‘opt-out by default’ method will use the Tag Composer Privacy plug-in available in the Javascript 5.24.0 version.
Note
This plug-in and its methods will apply solely to client-side visitor identification, it will impact first-party cookies only.
Tagging
Opt-Out
var tag = new ATInternet.Tracker.Tag();
tag.privacy.setVisitorOptout(); // Visitor set under Opt-Out
tag.page.set({
name: 'pageName',
});
tag.dispatch();It is possible not to send information by using the false setting of Tracker sendHitWhenOptOut.
Only these hit parameters will be filled in:
| s | idclient | vm | vc | ts | type | click |
| site number | visitor identifier | visitor mode | visitor consent | hit timestamp | hit type | click type |
These parameters will feed the AT Internet Privacy analysis, allowing you to get an anonymous and quantitative view of your traffic generated by users refusing tracker deposit. More details in our developer documentation.
Opt-In
var tag = new ATInternet.Tracker.Tag();
tag.privacy.setVisitorOptin(); // Visitor set under Opt-In
tag.page.set({
name: 'pageName',
});
tag.dispatch();Properties
The ‘opt-in by default’ setting uses two dedicated consent properties:
-
Consent properties
The new Privacy plug-in methods add 2 properties to your hits:
- Visitor mode : visitor_privacy_mode / &vm to filter events based on the consent status (optin/optout)
- Consentement visiteur : visitor_privacy_consent / &vc to directly identify consented traffic when ‘true’
Explorer
Once the tagging is implemented, and hits have the properties, you will only see events for which the visitor mode is set to "opt-in".
You do not need to filter the 2 properties; we will do this for you. (See below).
Privacy analysis
In Explorer you can reach Audience > General Traffic > Privacy to see the number of events considered as opt-out.
When the visitor has opt-out status, their hits serve only to feed this analysis and are not associated with other events.
Data Query / Data Flow
You may add the Visitor mode and Visitor consent properties to your data sets.
You will be able to analyse opt-in visitor mode only, given that opt-out events feed the Privacy analysis exclusively.
