By default, Clerk.io adds a 1st party cookie named visitor in Local Storage which contains an anonymous visitor ID.

The cookie is used for providing analytics in Clerk.io's Dashboards and for on-site functionality like "You Previously Visited" recommendations.

When informing and collecting cookie consent from consumers, we recommend that you put Clerk.io's cookie under "Necessary/Functionality".

This cookie can always be disabled, see below.

What we use the visitor cookie for

Dashboards, Analytics and Attribution

Clerk.io tracks all orders placed on the webshop, and compares the ones impacted by Clerk.io, with the orders not impacted.

Through the visitor cookie, we can track when a consumer clicks on a product in a Clerk.io element, and proceeds to place an order containing that product to allow for attribution.

On-site Functionality

Through the visitor cookie, we collect the IDs of products that a consumer browses and the searches they make.

This allows us to personalise recommendations on the webshop, including banners like "Our Recommendations For You" and "You Previously Saw" that show products related to browsing on the webshop.

AI Feedback

Our AI learns and grows by analysing the behaviour of visitors.

Through the visitor cookie, we receive feedback on metrics like:

  • Which products get the most clicks
  • Which products have the highest chances of causing a conversion
  • Optimal placements for products in banners and search results

This feedback is used to optimise results being shown to all consumers on each individual webshop.

How to classify Clerk.io's cookie

We recommend classifying it as "Necessary/Functionality" since it provides important functionalities to the consumer.

However, you are free to interpret its usage in other ways and classify it as other types.

Keep in mind that you will lose the above core functionalities if consumers do not consent with the cookie type you classify Clerk.io as.

The 'clerk-visitor-id' cookie and how it works

Clerk.io has been built with a privacy-first principle.

When a visitor enters the webshop for the first time, a unique, anonymous ID is assigned to them and saved in the 'visitor' cookie.

This ID can be considered as a device ID as it will have a unique value based on the device a consumer is browsing from.

Every call being made to Clerk.io after this point will contain the anonymous visitor ID so it can be used for the above purposes.

When a visitor writes their email address on the webshop and/or places an order, the Visitor ID is attached to their email address if sales-tracking is activated.

An email address in Clerk.io can contain multiple Visitor IDs which can be seen on the customers page in my.clerk.io:

Deactivating the 'visitor' cookie

Keep in mind, that if you deactivate the visitor cookie, you will lose all of the above functionality.

If you want to deactivate it, you simply need to set visitor: null either directly in your API calls, or by configuring Clerk.js.

Clerk.js

In setups using Clerk.js, add it to the Clerk.js code for that visitor:

API

If you are using direct API calls, include it as an argument:

curl -X POST \
-H 'Content-Type: application/json' \
-d '{"key": "yu0tX54BcDAIuBp8RkNoldtcir9Dwip8",
"limit": 30,
"labels": ["Bestsellers"]
"visitor": null}' \
http://api.clerk.io/v2/recommendations/popular

If you are have questions regarding visitor tracking, please don't hesitate reaching out to our Customer Success team through the live-chat in the lower right corner.

Did this answer your question?