-
Notifications
You must be signed in to change notification settings - Fork 0
Respecting data privacy 49dab2
So that you can respect user privacy and be in accordance with the regulations in different countries, the tracker allows you to disable user tracking.
This feature is available since version 5.11.0
Depending on the legislation in force, it may be necessary to indicate that the user has not yet consented to be tracked by our solutions via a cookie. To do this, simply set disableCookie to true when initializing the Tracker.
Hits will nonetheless be sent. Only the idclient variable enabling use tracking will contain the value “Consent-NO”
var tag = new ATInternet.Tracker.Tag({disableCookie: true});If your web site offers a page allowing the user to enable or disable statistical tracking, you can save this information via the global ATInternet.Utils.userOptedOut method.
Hits will nonetheless be sent. Only the idclient variable enabling use tracking will contain the value “OPT-OUT”.
To change this behavior, you can use the configuration key sendHitWhenOptOut available since version 5.14.0 of the Tracker. By passing the value to false (true by default), you will prevent the hits from being sent when the user is in “OPT-OUT” mode.
var config = {
sendHitWhenOptOut: false
};
var tag = new ATInternet.Tracker.Tag(config);
// Tracker is now preventing hit from being sent when the user is in "OPT-OUT" mode- Disabling user tracking
ATInternet.Utils.userOptedOut();
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();- Recovering user tracking status
var isOptedOut = ATInternet.Utils.isOptedOut(); // true or false- Re-enabling user tracking
ATInternet.Utils.userOptedIn();
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();Last update: 02/06/2020
-
Data API
- Data flow
- Advice optimizations data flow
- Error codes data flow
- Faq data flow
- General information data flow
- Technical information data flow
- Reporting API v3
- Getting started
- Methods
- Parameters
- Technical information
- REST API
- Campaigns
- Custom variables
- Getting started rest
- Methods rest
- Response structure parameters rest
- Fixed periods
- Parameters compatibility
- Relative periods
- Structure of the response
- “code” parameter
- “columns” parameter
- “evo” parameter
- “filter” parameter
- “include” parameter
- “lng” parameter
- “max-results” parameter
- “page-num” parameter
- “period” parameter
- “period” parameter: “H” v. “He” & “MN” v. “MNe”
- “retention” parameter
- “segmentdesc” parameter
- “segment” parameter
- “sep” parameter
- “sort” parameter
- “space” parameter
- Technical specifications rest
- Data flow
-
Data collection
- Android
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- Apple
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- General
- Cddc renew staging process
- Changelog
- Craft your hit
- Encoded parameters
- Server side cookie management
- Supported taggings
- Tagging deletion
- Utilisation of dispatch sdks
- JavaScript
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Partners javascript
- Users
- Piano Analytics
- Event tagging piano analytics
- Getting started piano analytics
- Piano analytics tagging
- Feeding piano analytics with as2 tagging
- Tagging custom properties sdk
- Android