Matching

Definition

When a visitor lands on your website or mobile application, a random value is attributed to the ‘client ID’ setting of the hit, enabling the generation of a ‘visitor ID’ and the creation of a visit for this user in your interfaces.

At this stage, no consent has been given. Cookies are not written and the data is not stored.

Having received no consent, the subsequent downloaded pages must be excluded from general traffic via the ‘no-consent’ method.

Nevertheless, on each of these pages, the ‘client ID’ of the entry page will be transported via the URL (or other method) and will not enable data storage, simply its transfer.

This method enables compliance with the user’s right to give consent at any time of the visit, while allowing you to recover the entry page (containing the source, for example) in the case of consent.

The visitor’s cookie IDs shall not be placed until the user has consented. Once consent is obtained, the cookie value will be placed with a unique value corresponding to the visitor ID of the entry page.

Advantages

When the visitor chooses opt-in status, the identifier passed from page to page is reused for the subsequent events.

Reusing the identifier generated on the entry page of the visit enables this event to be grouped with subsequent events.

The source will thus be associated with the whole visit.

Risks

All pages downloaded between the entry page and the consent page must be excluded from your analyses.

The visit which appears in the interface will therefore not be exhaustive.

Expected behaviour

To comply with your users’ wishes, you must be able to modify the state of consent at any time of the visit.

Tagging configuration

The ‘matching’ method will use the Tag Composer Privacy plug-in available in the Javascript 5.24.0 version.

Tagging

To handle visitor consent in the marking of the configuration, you simply need to add a line of code at the beginning of your tagging.

Then, just move from one state to another depending on the consent expressed by the visitor.

For more details, please read our article on developer documentation.

Non-cookied random ID

var tag = new ATInternet.Tracker.Tag();
tag.privacy.setVisitorRandomID(); // Visitor set under no-consent 
tag.page.set({
    name: 'pageName',
});
tag.dispatch();

The ‘setVisitorRandomID’ enables the attribution of a visitor ID without placing a cookie.

You can then pass the ID from page to page and store this visitor ID in a cookie once consent is obtained. You must follow the methods described in the developer documentation.

Only these hit parameters will be filled in:

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();

Opt-Out

var tag = new ATInternet.Tracker.Tag();
tag.privacy.setVisitorOptout(); //  Visitor set under OptOut 
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:

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.

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 the properties have been added to the events, you will be able to add to your Explorer analyses with the ‘Combine’ button above each table. You will then be able to filter property values (visitor mode: opt-in, visitor consent: true).

Privacy analysis

In Explorer you can reach Audience > General Traffic > Privacy to see the number of events considered as excluded under ‘no-consent’ or ‘opt-out’.

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 and no-consent events (with option) feed the Privacy analysis exclusively.