Digital Analytics cookie logic does not interfere with the setting of existing non-Digital Analytics cookies.

Prior to setting cookies, Digital Analytics checks to determine whether setting cookies would cause the maximum cookie length or number limit for the browser to be exceeded. In such cases, Digital Analytics libraries do not set additional cookies, preventing loss of other non-Digital Analytics cookies previously set under the domain.

The standard Digital Analytics cookies set for most implementations are as follows:

Session cookies

• "Session" ID cookie and session-expiration cookie, where '99999999' is the assigned Digital Analytics Client ID). Expiration: at end of the session.
• New Sessions: Current® browsers do not begin a new Digital Analytics "session" when a new window or new tab is opened in the same browser. Browsers such as Safari running in iOS are exceptions to this rule and do start a new session with each new instance of the browser that is running in the device.
• Session Inactivity Timeout: The default inactivity timeout for Digital Analytics "session" cookies is 30 minutes. If no tags are received for a period of greater than 30 minutes, the next tag received associated with this session causes the session cookies to be reset and a new session cookie(s) set. This and the following tag data are associated with the new session.
  • 99999999_clogin (Client Managed) or 99999999_login (Acoustic Managed) - stores a numeric ten-digit "session ID". The Client-Managed cookie additionally stores separate "e=" and "l=" subkey values, replacing the 99999999_expires cookie used by 'Acoustic Managed' implementations. The l= subkey value is the 10-digit 'session ID'. Set under the 'Cookie Domain' for 'Client Managed' implementations, or the 'Data Collection Domain' for Acoustic -Hosted implementations.
  • Acoustic Multisite: By default, the _clogin or _login session cookie contains the fully qualfied GlobalID|SiteID value: 59990000|SITEID-1_clogin/login and 59990000|SITEID-2_clogin/login. This results in separate sessions for each Site ID.
  • Acoustic Multisite Global ID Sessionization: To set a common session cookie across all Site IDs for a given Global ID, the following statement can be called to enable 'Global ID Sessionization' for Client Managed 1st party implementations:

    cmSetupOther({"cm_JSFEAMasterIDSessionCookie":true});

    To switch 'Acoustic Managed' implementations from the default Site-ID sessionization to Global ID sessionization, please submit a request to Acoustic Support.
  • 99999999_reset: Acoustic Managed 'Timeout' cookie timestamp value. Set under the ‘Data Collection Domain’ specified in parameter 3 of the cmSetClientID(...) call.
• Utility Cookies: Expiration: at end of the session.
  • cmTPSet: Used to determine when extra JavaScript-based technical properties data has been collected for the session. Set by eluminate.js 4.1.2 and later. Set under the 'Cookie Domain' value specified in parameter 4 of the cmSetClientID(...)call.
  • TestSess3: Acoustic Managed session cookie used to determine if the browser is accepting cookies. Cookie always contains the same value as the 'CoreID6' cookie described in the following section.
  • cmRS: 'Resend' cookie - used to persist automatically-collected 'Link Click' data to destination pages. Not set until the visitor clicks on an instrumented link. Set under the 'Cookie Domain' (typically the 2nd level site domain). The cmRS cookie is set in the eluminate versions prior to 4.8.5H and after 4.23.167.

Persistent cookie (1)

• Set under the specified 'Cookie Domain' for 'Client Managed' implementations, or the 'Data Collection Domain' for 'Acoustic Managed' implementations.
  • CoreID6: Persistent cookie that stores a VisitorID value. Expiration: 15 years from date set. When set by Client Managed 1st party implementations, this cookie also includes one or more &ci=subkey values that specify the Client IDs to which this Visitor ID applies.

  Cookie Limit Setting

  • The cm_CookieLimit setting allows override of the default limit of "50" cookies per domain. This value indicates the maximum number of cookies allowed before the eluminate.js tag library will no longer attempt to set Digital Analytics cookies in a given domain. This limit prevents accidental roll-off of existing customer cookies.
  • The cm_CookieLimit variable should be set immediately after your cmSetClientID statement and prior to any cmCreate* tag function calls. This variable can be set by calling cmSetupOther(...):

    cmSetClientID("99999999",true,"data.coremetrics.com","site.com");
    cmSetupOther({"cm_CookieLimit":"80"});

  Manually reset client-managed, first-party cookies

  You can manually reset Client-managed visitor and session cookies for a public kiosk or other shared workstation scenarios.

  When multiple users visit tagged pages with the same browser client, all the users are tracked as a single visitor in reporting. If the activity is continuous such that at least one tag is sent every 30 minutes, all the users during this period are also tracked as a single session in reporting. To associate users of a common browser client with unique visitor IDs in reporting, delete the 'CoreID6' Visitor cookie. To associate users of a common browser client with unique Session IDs in reporting, delete the '<clientid|siteid>_clogin' session cookie.

  Note: The following example uses the eluminate tag library 'CC' cookie deletion function, but you can use any standard JavaScript to delete the client-managed cookies.

  You cannot delete Acoustic-managed cookies. If you need local access to Digital Analytics cookies consider switching to client-managed 1st party data collection.

  Example HTML and JavaScript Code

  <HTML>
  <HEAD>
  <script type="text/javascript" src="//libs.coremetrics.com/eluminate.js"></script>
  <script type="text/javascript">
  cmSetClientID("99999999",true,"data.coremetrics.com","thesite.com");  // true = 
  Client Managed cookies
  </script>
  </HEAD>
  <BODY>
  <script>
  // set by kiosk at end of a 'visit' (current user logged off or timed out 
  kiosk session, etc)
  var kioskSessionEnded = true;
  </script>
  <script type="text/javascript">
  // check condition and reset Visitor and/or Session cookie prior to sending 
  the next tag for the new Visitor and/or Session.
  if(kioskSessionEnded) {
  // delete Acoustic DA visitor ID cookie
   CC("CoreID6",cm_JSFPCookieDomain);  
  // delete Acoustic DA session ID cookie
   CC(cm_ClientID + "_clogin",cm_JSFPCookieDomain);
  }
  </script>
  <script type="text/javascript">
  cmCreatePageviewTag("KOISK Page ID","KOISK PageCategoryID");
  </script>
  </BODY>
  </HTML>