CODEWITHSUNDEEP
session-cookiesaemadobe-analyticsweb-analytics
Pankaj - Web Analytics Lead
Pankaj - Web Analytics Lead

Reputation: 1

s_sess cookie not storing the value from query string parameter cid

Does anyone has any information about s_sess cookie. All I can find is that it's a performance cookie.

The issue here is : My client has 2 websites, one of them is storing the value of query string parameter "cid" in s_sess cookie while the other site is not. Both of them has same adobe analytics code and both sites are on third party cookies.

Upvotes: 0

Views: 1476

Answers (1)

CrayonViolent
CrayonViolent

Reputation: 32517

Many of Adobe's plugins make use of the s.c_r() and s.c_w() (legacy H code) or s.Util.cookieRead() and s.Util.cookieWrite() (AppMeasurement) functions, which are for reading/writing cookies, respectively. Out of the box, you specify a cookie name and it writes to that cookie namespace.

However, Adobe also has a "combined" cookie plugin. With this plugin, all cookie reading/writing with the above functions are instead written to one of two cookies:

  • s_sess - This cookie is for session scoped "cookies"
  • s_pers - This cookie is for "cookies" that persist longer than session

So for example, let's say on the following page:

http://www.yoursite.com/index.html?cid=some_code

And in your AA code, you have the following:

// look for cid= param to put into campaign variable
s.campaign = s.Util.getQueryParam('cid');
// use getValOnce plugin to make sure duplicate values do not pop it again
s.campaign = s.getValOnce(s.campaign, 'cid', 0);

Without the combined cookies function, you will see a cookie named "cid" in document.cookies with value of "some_code" set to expire on Session.

But with the combined cookies function, you will not see a cookie named "cid". Instead, you will see a cookie named "s_sess" with a value like this: 

// encoded
%20cid=some_code%3B
// unencoded
 cid=some_code;

Or, if you use a plugin that makes use of s.c_w or s.Util.cookieWrite for longer than Session, you will instead see the s_pers cookie populated the same way, but with a timestamp value thrown into the mix, e.g. 

// encoded
%20cid=some_code%7C1519759520136%3B
// unencoded
 cid=some_code|1519759520136;

Multiple "cookies" are separated by (unencoded) "; " (similar to document.cookie)

But why do I see it on one site but not the other?

Assuming your implementation is in fact identical, my guess based on what you posted vs. common implementations is you have code similar to my example above: You grab cid= param for campaign tracking and make use of getValOnce or some other plugin that pushes the value to a cookie, and you went to siteA page with a campaign code (cid= param) but not siteB.

Upvotes: 4

Related Questions