Developers
Search…
User Identification
The kd-lynx-v1.js file uses a cookie to identify users interacting with your web store across browsing sessions. This is a first-party, one year expiration time cookie.

How are users identified?

We identify users in one of the following ways:
    1.
    LYNX's JavaScript traking code checks the page's url to find a parameter named kdCustomerId. If present the value assigned to kdCustomerId is stored in the browser's cookie and will be used to identify users returning to your website. This is intended to be a known identifier (userId) for a user provided by the website owner/library user.
    2.
    A user can be explicitly identified using the setCustomerId command. For example this command can be issued when a user logs into your web store.
We recommend that you use a unique user identifier that won’t change for your userId, for example a database ID from your organization’s internal systems.
Before being saved in Kickdynamic's databases the value of kdCustomerId is hashed using the SHA-256 algorithm.
Until a user is not identified via one of the aforementioned ways, its iteraction with your web store will be tracked using a randomly generated identifier (guid). As soon as a user is identified, all her previuosly tracked data is updated and linked to the kdCustomerId value.
The following table shows the default cookie attributes set by kd-lynx-v1.js:
Attribute
Type
Value
Name
string
_kd
Domain
string
The kd-lynx-v1-js sets the _kd cookie on the highest level domain possible.
Expiration
date
One-year expiration
A LYNX cookie may look like this:
1
KD1.e84a8a62-971a-4b7a-9943-c9515e610dc5.customerId.origin
Copied!
or
1
KD1.7e945931-4a0c-4968-9fbc-4a27193e32cc.c96526f1abb5764769c19c002a480915e6345f70c45364983406628c28d422fb.origin
Copied!
The cookie value is made up of three 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 behaviour of not yet identified users.
    3.
    The third field is the value that identifies your user and that is set reading the kdCustomerId parameter from the page's url or that is set invoking the setCustomerId command. When a user is not yet identified, the value of this field is set to the fixedcustomerIdstring. Once a user is identified this value is replaced with the hashed value your user's unique identifier.
    4.
    The fourth field can contain Kickdynamic's tag ID for attributing a purchase.
Last modified 6mo ago