Comment on page
kd-lynx-v1.jsfile uses a cookie to identify users interacting with your web store across browsing sessions. This is a first-party, one-year expiration time cookie.
We identify users in one of the following ways:
kdCustomerId. If present, the value assigned to
kdCustomerIdis stored in the browser's cookie and used to identify users returning to your website. This is intended to be a known identifier for a user (
userId) provided by the website owner/library user.
- 2.A user can be identified using the
setCustomerIdcommand. For example, this command can be issued when a user logs into your web store.
We recommend using a unique user identifier that won't change for your
userId(for example, an ID from your organization's internal systems).
Before being saved in Kickdynamic's databases the value of
kdCustomerIdis hashed using the SHA-256 algorithm.
Until a user is not identified via one of the ways mentioned above, its interaction with your web store will be tracked using a randomly generated identifier (guid). As soon as a user is identified, all her previously tracked data is updated and linked to the
The following table shows the default cookie attributes set by
A LYNX cookie may look like this:
The cookie value consists of four parts separated by a dot ('.'):
- 1.The first field is the cookie version number (KD1).
- 2.The second field is a randomly generated identifier (guid) that LYNX uses to track the behavior of not yet identified users.
- 3.The third field is the value that identifies your user, and that is set reading the
kdCustomerIdparameter from the page's URL, or that is set invoking the
setCustomerIdcommand. When a user is not yet identified, the value of this field is set to the fixed
customerIdstring. Once a user is identified, this value is replaced with the hashed value of your user's unique identifier.
- 4.The fourth field can contain Kickdynamic's tag ID for attributing a purchase.