Understanding tracking with Cookiedatabase.org

_sp_ses*

Summary

Cookie is placed by:

The functionality is:

The purpose is:

This period shows the length of the period at which a service can store and/or read certain data from your computer by using a cookie, a pixel,  an API, cookieless tracking, or other resources. 

This describes if this specific cookie , localStorage or other resource is responsible for sharing, collecting or storing direct or indirect personal data.

You can use this data to update your cookie policy, screen services that set specific cookies or contribute to our effort in creating internet transparency.  Data passport: To see this, just click on the name of the service.

This is the number of times a website requested information from cookiedatabase about this particular “cookie” used on their website.  

One Response

  1. A detailed description shared by the author on: https://github.com/snowplow/snowplow/wiki/1-General-parameters-for-the-Javascript-tracker

    “Called _sp_ses.{{DOMAIN HASH}} by default, the only purpose of this cookie is to differentiate between different visits. Whenever an event is fired, the session cookie is set to expire in 30 minutes. (This value can be altered using setSessionCookieTimeout.)

    If no session cookie is already present when an event fires, the tracker treats this as an indication that long enough has passed since the user last visited that this session should be treated as a new session rather than a continuation of the previous session. The visitCount (how many times the user has visited) is increased by one and the lastVisitTs (the timestamp for the last session) is updated.”

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Complianz.io

The Privacy Suite for WordPress. With Cookiedatabase.org API
Sponsored