User Tracking & Privacy
  • 7 minutes to read

User Tracking & Privacy


Important Note
As part of building user profiles, Cxense does not collect any personally identifiable information, follows all applicable data collection laws and honors industry standards. Please also see our privacy policy

Identifiers

In order to be able to reliably track and count the number of unique users visiting your site and build user profiles, Cxense makes use of cookies and local storage as ways to store information. All cookies and local storage used by Cxense only store non-personally identifable information, such ad random identifiers or carrying some state, like timestamps or, for the case of segment matching, segment IDs the user identifier is related to.

Two first-party site-specific cookies are set on the domain of the site, and are used to identify the user on your site both within a session and across sessions. These cookies are named cX_S and cX_P respectively. The corresponding localStorage entries are also set, named _cX_S and _cX_P respectively. The identifiers can be accessed both on the client side or the server side. On the client side, cX_P can be read out via the cX.getUserId() function call. On the server side, the cookies can be read via standard mechanisms, such as cX.getCookie("cX_P")

In addition, and if the client supports and allows it, two third-party cookies are set to enable the building of session and cross-session user profiles that span all sites in the Cxense network. These are named gcks and gckp respectively.

A cX_T cookie can in some rare cases be seen. It is only set briefly, and then immediately deleted. This cookie holds a random value and is just used to find the top-level domain of the site. For example, we use this cookie to find out that ibm.com is the top-level domain of www.ibm.com and that bbc.co.uk is the top-level domain of www.bbc.co.uk

Additional service-specific cookies

The above cookies are always set when using Cxense services. In addition, when using particular services or particular features of those services, some additional cookies can be set:

When using DMP segments for ad targeting with third-party systems, the current segment identifiers that the current user is a member of is cached on the client using one local storage token:

_cX_segmentInfo

Name Type Lifetime Object Domain
cX_S Cookie Session Site specific user session – single session First
cX_P Cookie 365 days Site specific user session – across sessions First
cX_G Cookie & Local Storage 365 days Global ID mapping different ids together into one ID First
gcks Cookie Session For building session information across all sites in the Cxense network Third
gckp Cookie 365 days For building user profile information across all sites in the Cxense network Third
cX_cons Local Storage No expiry For recording consent First
_cX_segmentInfo Local Storage 365 days When using DMP segments for ad targeting with third-party systems - the list of segment identifiers First
cX_T Cookie Temporary Set briefly, and then immediately deleted. This cookie holds a random value and is just used to find the top-level domain of the site First
_cX_S Local Storage Session Corresponding to the first party cookie cX_S First
_cX_P Local Storage 365 days Corresponding to the first party cookie cX_P First
cX_lastP1Time Local Storage Temporary For non-Safari browsers, we record third-party IDs once per week. This represents the next time it should load after First
cX_lastLocalCstTime Local Storage Temporary For Safari browsers, we record third-party IDs once per week. This represents the next time it should load after First
_cX_SA Session Storage Temporary For session annotations First
cX_lst Local Storage 365 days Records a third-party token for cross-site tracking Third
cx_partner Session Storage Temporary Keeps a log of how many cookie syncs were executed for each partner, in the form of <partner>=<# of hits> for each partner First
_cX_expires Local Storage No expiry Intended to expire local storage. Local Storage does not expire by default. Local storage tokens match cookie expiration times First
cstp Cookie Temporary Used to throttle cookie syncs with ad partners. Optional (will be removed soon<) First
cX_LSS Cookie 365 days Optional tool to keep track of session start times First
cX_LSP Cookie Temporary Records previous session time (similar to cX_LSS) First

Page view event parameters

The cx.js script collects various pieces of data, builds up a URL that encodes this information, and sends this back to the Cxense platform by making a standard HTTP request to the Cxense servers. This HTTP API can also be invoked directly by clients. The URL currently encodes the following parameters:

Parameter Required Sample Value Description
ver Yes 1 To which version of the API is this requested targeted
typ Yes pgv What type of event is this? The value pgv denotes a page-view event.
acc No 0 The Cxense account identifier.
sid Yes 1234567890123 The Cxense site identifier.
loc Yes http://www.yoursite.com/news/1 The URL of the page. Must be a syntactically valid URL, or else the event will be dropped.
ref No http://www.yoursite.com/ The URL of the referring page.
gol No The Cxense goal identifier. For future funnelling purposes.
pgn No The page name.
ltm No 1473837694457 The local time on the client.
tzo No -120 The client's timezone.
res No 1920x1080 The screen resolution. The format is "res=<width>x<height>", e.g. "res=1024x768"
ws No 1395x282 The initial browser window size: The format is "wsz=<width>x<height>", e.g. "wsz=544x365".
col No 24 Device color depth.Typically read from window.screen.colorDepth in a browser.
dpr No 1 Device pixel ratio (the ratio between physical and virtual pixels). Typically read from window.devicePixelRatio in a browser.
rnd Yes it2kwr95mv0uxmh3 A random number, for cache-busting purposes and to uniquely identify a page-view request.
jav No 0 Is Java enabled?
bln No en-US The client's browser language.
cks No it2kw3ldnxjc The Cxense site-specific session cookie. Must be at least 16 characters long. Allowed characters: A-Z, a-z, 0-9, "_", "-", "+" and ".".
glb No cx:pbad80kwtao0l1qyfh5vv7q7:2vaqowu49edjp The global id that uniquely identifies the user in relation to other ids (ckp, etc.)
chs No UTF-8 The document's character set.
fls No 1 Is Flash enabled?
flv No Shockwave Flash 22.0 r0 Which version of Flash, if relevant?
new No 0 Hint to indicate if this looks like a new user. Values: 0 or 1, e.g. "new=1" to indicate a new user.
cp_<name> No Set a custom parameter "name=value" by adding a URL parameter with a "cp_" prefix and the same name and value as the wanted custom parameter. E.g. if you want to set " premiumPage: true", you add the URL parameter "cp_premiumPage=true". See the documentation for for more details on setting custom parameters. The recommended practice is to use for your parameter names. E.g. your customer prefix is "xyz", then add the URL parameter " cp_xyz-premiumPage=true ".
cp_u_<name> No Set a user profile parameter "name=value" by adding a URL parameter with a "cp_u_" prefix and the same name and value as the wanted user profile parameter. E.g. if you want to set "sportsFan: true", you add the URL parameter "cp_u_sportsFan=true". See the documentation for more details on setting custom parameters.
eid0 No The value of the first optional external user id, used for linking external user ids to Cxense users. 64 characters max length.
eit0 No The type of the first optional external user id, used for linking external user ids to Cxense users. 10 characters max length.
eid1 No The value of the second optional external user id (etc..)
eit1 No The type of the second optional external user id (etc..)
ptim No Position time.
plat No Position latitude.
plon No Position longitude.
pacc No Position accuracy.
palt No Position altitude.
paac No Position altitude accuracy.
phed No Position heading.
pspd No Position speed.
amo No 1473634205 (for 2016-09-11T22:50:05Z) If the web page has a <meta> tag with a property of 'article:modified_time', the 'content' is parsed and converted into seconds.
con No y, pv, segment Consent. A comma separated list with the following values: y- Required, set if this event was obtained and may only be processed with the user's consent; pv - Page view tracking, DMP event tracking and browsing habit collection to understand a user’s interests and profile; recs - Personalisation of content recommendations and suggested content based on user interests and browsing habits; segment - Audience segmentation, processing of browsing habits and first party data to include users in specific audience segments; ad - Targeting advertising based on browsing habits and audience segmentation.
Was this article helpful?