-
Notifications
You must be signed in to change notification settings - Fork 0
Respecting data privacy d515bb
So that you can respect user privacy and be in accordance with the regulations in different countries, the tracker makes two features available:
- Disabling user tracking
- Hashing user IDs
If your application offers a screen allowing the user to enable or disable statistical tracking, you can save this information via the static doNotTrack method of the Tracker class.
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 2.12.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.
Tracker tracker = ATInternet.getInstance().getDefaultTracker();
tracker.setSendHitWhenOptOutEnabled(false, null, true);
// Tracker is now preventing hit from being sent when the user is in "opt-out" mode- Disabling user tracking
@Override
public void onClick(View v) {
// < 2.9.0
Tracker.doNotTrack(true);
// >= 2.9.0
Tracker.optOut(true);
// >= 2.9.1
ATInternet.optOut(this, true);
}- Recovering user tracking status
@Override
protected void onResume() {
super.onResume();
// < 2.9.0
boolean doNotTrack = Tracker.doNotTrackEnabled();
// >= 2.9.0
boolean optOut = Tracker.optOutEnabled();
// >= 2.9.1
boolean optOut = ATInternet.optOutEnabled(this);
}The SDK allows for the automatic addition of user ID in your hits (Android ID, Advertising ID). You may also add your own user ID via the tracker’s setParam method.
To ensure visitor anonymity, all while keeping their identification in your analyses, it is possible to hash the unique ID (SHA-256). To do this, use the tracker’s setConfig method as follows:
@Override
protected void onResume() {
super.onResume();
tracker.setConfig("hashUserId", true, new SetConfigCallback() {
@Override
public void setConfigEnd() {
Log.d(null, "User ID will now be hashed");
}
});
}You can configure where the offline hit are saved with the static method setDatabasePath of the ATInternet class.
If the path is incorrect, the database won’t be initialized and the offline hits will be lost
// Before any Tracker usage !
ATInternet.setDatabasePath("myCustomPath");Last update: 13/03/2019
-
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