Client-managed first-party collection requires minimal setup effort and has no recurring cost or administrative overhead. In most cases, no additional effort is required when implementing this form of first party data collection.
In initial planning, you need to inventory the unique 2nd level domains for the sites where client-managed first-party is to be implemented. For domains with a country code top-level domain (ccTLD) such as thesite.co.uk, reference the 3rd level domain value thesite.co.uk.
Activate multisite global sessionization
If you have a multisite implementation, the Site ID value can change during a visit to a single, client-managed cookie domain. To ensure the visitor is associated with a single session, implement multisite global sessionization. A multisite implementation refers to any HTML web site sending tags directly to a native multisite Global ID+SiteID in the format 5xxx0000|<siteid>. A native multisite Global ID starts with a '5' and ends in four zeroes. Legacy 9-series IDs migrated to multiisite cannot use or benefit from multisite global sessionization.
To activate this feature for client-managed first-party multisite implementations, set the
variable cm_JSFEAMasterIDSessionCookie to a Boolean value of true immediately
after the eluminate.js tag library and before any tag function calls. The
cmSetupOther function provides a convenient way to set this and other optional
eluminate.js variables. For example,
Setting the cookie domain value
configuration step is to update the
cmSetClientID(...) function call to enable
client-managed first-party and set the appropriate cookie domain value.
Change the data
collection method parameter to
true (the default is
data collection domain parameter remains
data.coremetrics.com. Then, change the
cookie domain parameter to match the appropriate 2nd or 3rd level domain value of the website where
cmSetClientID is called.