In addition to the various methods presented in the Privacy Centre, certain options can be activated according to your needs.
Exclusion of non-cookied traffic
Comply with the choice of your users who have specifically refused the placement of cookies. You are reminded that obtaining consent for the placement of audience measurement cookies is the norm in the Europe (GDPR).
In the case where the placement of cookies is refused, our solution operates a default recognition of the user via an association of the IP address and its User Agent.
This association is a form of fingerprinting.
In this framework, AT Internet provides an option to exclude such non-cookied traffic so that it does not enter into your analyses. This option may be activated for ‘organisation’ or for ‘site’.
Contact your support centre (‘Help’ button on the bottom right) to activate this option or request further details.
Non-cookied traffic is excluded from your analyses intended for cross-referencing and segmentation.
You will find indicators in your Explorer analyses enabling you to count the number of pages seen relative to this excluded traffic (under the ‘no consent’ value).Le trafic non-cookisé est exclu de vos analyses de navigation, croisables et segmentables.
Anonymisation of the IP address
Ensures enhanced anonymity of your users in terms of their geo-tracking.
Please note that, in all cases, the IP address is never available in Piano Analytics.
This IP address anonymisation is not a requirement in the framework of the GDPR, but it is, for example, compulsory for the processing of personal data of citizens residing in Germany.
Contact your support centre (‘Help’ button on the bottom right) to request the activation of this option to anonymise the last octet of the IP address (last 3 digits).
It will be possible to observe potential accuracy losses relative to:
- Your users’ geo-tracking (Cities and ‘Organisations’ in particular)
- The detection of robots
- The detection of ‘operators (internet connection)’
Some IP exclusions configured in your interfaces will have to be reconfigured.
Indeed, the exclusions set to 4 bytes will no longer be functional, the last byte is no longer available due to anonymization.
Be sure to reset these exclusions, taking into account that you will completely exclude the last range (4th byte).
Mobile user ID hashing
- iOS: https://developers.atinternet-solutions.com/apple-universal-en/users-apple-universal-en/respecting-data-privacy-apple-universal-en/#hashing-user-id_3
- Android: https://developers.atinternet-solutions.com/android-en/users-android-en/respecting-data-privacy-android-en/#hashing-user-id_3
The Data Manager application was launched with a simple objective in mind: to help you maintain control of your marking and uploaded data.
Create rules in order to rectify or add information which is not present in the marking of your site.
To demonstrate ways in which you can use this tool, we have provided several client cases:
- Rectification of an error in the marking of campaigns
- Data enrichment via a customised object
- Recovery of data present on the URL of your page
- Exclusion of undesired traffic
In the framework of your bringing into compliance, Data Manager may be used to rectify, exclude or modify collected data, enabling fine-tuned management of your personal data.