A unique visitor is a website visitor with a certain set of parameters: cookies, browser, OS, etc.
The system remembers such visitor. During their next sessions, this visitor is not considered as unique in a current accounting period.
If visitors go to your website after they:
- cleared cookies
- did not visit the site for more than 150 days (cookies are stored for 150 days)
- entered from another device (and didn't share their contact details so that the system could merge them with the existing lead card)
- reinstalled the browser or OS
they will be considered as a new unique visitor.
The service recognizes visitors' cookies, but this can be customized so that a visitor with unrecognizable cookies would be merged with a user Dashly already knows. This can be accomplished by assigning this visitor with a user id (this should be done on your side) and sending user ID into the service. Afterwards, Dashly will be able to recognize this visitor when they authorize on your site, even if they come with different cookies (or via different devices) or after the interval of 150 days (after the cookies storage period for cookies expires).
You can merge visitors by user ID if your site has sign up functionality.
We’re using “User ID” to merge visits from different devices. Once the visitor is authorized in your system, you need to send his ID to Dashly, using this method:
First argument is User ID. Second - hash HMAC SHA 256 (). The text for hashing is User ID, the key is User Auth Key, which you can find it in the Admin panel.
Example in PHP:
$userId = '...';
$hash = hash_hmac('sha256', $userId, 'User-Auth-Key' );
echo "dashly.auth('".$userId."', '".$hash."')"
More details can be found here.