[object Object] Icon

Encoding
Learn how to create, start, manage and modify Encodings

[object Object] Icon

Player
Learn how to create, start, manage and modify Players

[object Object] Icon

Analytics
Learn how to create, start, manage and modify Analyticss

Docs Home
User shortcuts for search
Focus by pressing f
Hide results by pressing Esc
Navigate via   keys

Thu Aug 13 2020

Cookies in Bitmovin Analytics

Thu Aug 13 2020

Cookies in Bitmovin Analytics are used to a unique identifier on the viewer’s device to re-identify a specific viewer as a unique user, when she returns to watch another video.

Setting this cookie enables the metric Unique Users in Bitmovin Analytics. Without a unique identifier specified in the cookie, the number of Plays will equal the number of Unique Users.

We only set a first-party cookie that stores information that is only readable by Bitmovin Analytics on your domain. We don’t engage in any cookie matching or similar cross-site tracking.

Cookies by default are set without a domain but it is possible to specify the cookie domain as per the HTML specifications for cookies: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies

To configure the cookie domain you can use the cookieDomain setting in the config property of the analytics collector:

1let analyticsConfig = {
2 config: {
3 cookiesDomain: 'bitmovin.com'
4 }
5};

This will result in a cookie being written with: Domain=bitmovin.com

This is useful if you want to share cookies across subdomains of your main domain as per default subdomains of your domain are not allowed to read the cookie set for your domain. So the above example enables all subdomains of bitmovin.com to read the cookie set for bitmovin.com.

You can read more on Cookie Domains at MDN

Cookies in Bitmovin Analytics can be fully disabled. There are two methods to disable cookie tracking for a specific user.

Method 1: Disabling Analytics completely at the root level (no cookie will be set here):

1let playerConfig = {
2 // player configuration stuff
3 analytics: false
4}

Method 2: Disabling cookies in the analytics config using cookiesEnabled:

1let playerConfig = {
2 // player configuration stuff
3 analytics: {
4 config: {
5 enabled: false/true, // this controls whether or not the collector is enabled / will report data
6 cookieEnabled: false // this will only disable the cookie - the collector could still be enabled/disabled
7 }
8 }
9}

Note: If you set enabled: false the cookie will be initialized regardless if you don’t set the cookieEnabled setting specifically.

Give us feedback