Read on below the fold for:
- Tracking users granting, and withdrawing, consent to have their personal data processed for specific purposes
- Form tracking with more control
- Start new sessions client-side
- Updates and bug fixes
- Documentation and help
1. Tracking users granting, and withdrawing, consent to have their personal data processed for specific purposes
Against the backdrop of the incoming GDPR and ePrivacy regulations, this release adds new events to track when users give their consent to, and withdraw their consent from, having their personal data processed for specific purposes.
We envision that many digital businesses will want to track the consent of their users against relatively fine-grained “bundles” of specific data usecases, which we model in Snowplow as consent documents.
The two new consent tracking methods are:
Each consent event will be associated to one or more consent documents, attached to the event as contexts.
Here is an example of a user opted into data collection per a specific consent document
2. Form tracking with more control
Form tracking now offers the ability to transform form field data with a callback function,
For example, use this to hash the field data before sending it for collection:
Documentation can be found here.
3. Start new sessions client-side
Documentation is found here.
4. Updates and bug fixes
Other updates and fixes include:
identifyUseras an alias for
- Make the
newDocumentTitlevariable local (#580)
- Enforce that
geolocation.timestampis an integer (#602)
- Bump the
semverdependency to 4.3.2 (#625)
respectOptOutCookiefrom the Tracker function comments (#605)
The tracker is available to use here:
As always, we encourage you to self-host your own copy of the tracker.
There are no breaking API changes introduced with this release.
6. Documentation and help
The v2.9.0 release page on GitHub has the full list of changes made in this version.