Consent and cookie management
About cookies used by Splio trackers
At this moment the tracker supported by Splio Predictive CDP is the Snowplow opensource browser tracker. Therefor the cookie definition is part of the standard Snowplow tracker behavior.
The Snowplow Opensource browser tracker is able to exploit up to 3 different 1st party cookies (note that Splio does not use any 3rd party cookie).
For Splio Predictive CDP configuration, as we don’t require the activation of session tracking, only one cookie will be used : _sp_id with a default lifespan of 2 years. The session cookie _sp_ses will be initialized by the tracker (without content) but will not be used by the endpoint, nor any session identifiers which are stored in _sp_id
Main cookie content
The cookie _sp_id is a 1st party cookie : it is seen as a cookie of your website. It may be blocked by Ad blockers but it is possible to setup a custom name to avoid it to be blocked
Note that the content of the cookie is defined by the opensource Snowplow tracker technology. The predictive CDP will only use a subset of its content
The cookie content is an aggregated chain of properties, described here :
| Property | Content | Used by Splio Predictive CDP ? |
|---|---|---|
| domainUserId | unique identifier (generated anonymous UUID) for each user. | Yes, as column anon_user_id in data model |
| createdTime | 1st visit of user | No |
| visitCount | Total count of visits for domainUserId | No |
| nowTime | last event time | Duplicates the event_time available in data model technical data |
| lastVisitTime | previous visit time | No |
| sessionId | Current session identifier | No |
| previousSessionId | Previous session identifier | No |
| firstEventId | Tracking of events to push (used by tracker to push multiple events when the tracking endpoint is unreachable) | No |
| firstEventTsInMs | Tracking of events to push (used by tracker to push multiple events when the tracking endpoint is unreachable) | No |
| eventIndex | Tracking of events to push (used by tracker to push multiple events when the tracking endpoint is unreachable) | No |
Note that the name of the cookie can be configured in integration configuration
What if the cookie cannot be setup in my website or if it is blocked by an Ad Blocker ?
The cookie _sp_id is used to identify Anonymous traffic which can be then conciliated with identified traffic (through column anon_user_id ). If the anonymous identifier anon_user_id cannot be setup, then you will not be possible to conciliate anonymous activities with your identified user activities.
About consent management
We recommend to always enable consent management on your website.
- If you are using a Tag Manager (like Google Tag Manager) and a CMP (Consent Management Platform) the consent will already be taken into account: no analytic traffic or cookie can be enabled if the consent is not given first by the end user.
- If you prefer to use a custom integration of the tracker (without a tag manager), the Snowplow Browser tracker plugin can take into account the consent status before sending any tracking event. The integration of a CMP is possible without tag manager and will help you to gather and manage the consent of your end users.
If you need help on Consent Management Integration, we can recommend a partner which can advice you and implement a solution conform with GDPR
Please read more about our consent recommandations in this article.
Updated 5 months ago