Source
Consent & visitor tracking — found from sitemap — Clerk.io
Checked for Clerk.io on 17 Nov 2026
- Page
- https://help.clerk.io/platform/data/cookieless-solution/
- Checked
- 17 Nov 2026, 12:15 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:58961710b7e79fdd833a83621270a4e0705cb7a894f10dd357866348e50b69f0
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Cookieless default Report an error
“Cookieless tracking is built into Clerk.js and is activated by default.”
-
Knowledge graph Report an error
“At the heart of Clerk’s AI is the “Knowledge Graph” technology, which connects all your products, categories, articles, orders, and (if enabled) customers to one another.”
-
AI order data Report an error
“The Knowledge Graph operates without requiring website data like clicks, searches, and other browsing activity. Instead, Clerk has always relied on order data as the main source of truth for the AI.”
-
Session tracking method Report an error
“Clerk tracks visitors through anonymous session IDs, which are generated each time a browser makes a request to https://api.clerk.io.”
-
Session hash inputs Report an error
“We compute a hash using the IP address, User Agent, and a unique store salt. The store salt is unique to each store using Clerk and is rotated every 30 days, making long-term tracking virtually impossible.”
-
Session ID format Report an error
“This identifier ensures that shopping sessions remain anonymous. It does not contain any personal data, does not store anything on users’ devices, and prevents long-term tracking beyond 30 days.”
-
Privacy modes count Report an error
“There are 4 privacy modes, explained below.”
-
Privacy mode default Report an error
“Clerk.js uses anonymous sessions as described above, per default.”
-
Privacy mode persistent Report an error
“This mode generates the same unique ID and stores it as a long-term identifier in the visitor’s browser localStorage, forming the basis for tracking. This can be used for visitors that give consent to being tracked.”
-
Visitor ID name Report an error
“Name: clerk-visitor-id.”
-
Visitor ID lifetime Report an error
“Lifetime: Long-term, until browser data is cleared or the identifier is replaced.”
-
Privacy mode private Report an error
“In this mode, no data about the visitor is collected for any reason.”
-
Privacy mode private limitations Report an error
“Additionally, any sales made through our services will not be attributed to Clerk in the dashboard, which may result in underreporting in your statistics.”
-
Privacy mode custom Report an error
“You can configure custom visitor IDs that you generate yourself, allowing full control over the type of ID assigned to each visitor or session. This option is typically used for integration with external tools.”
-
Cookieless stats Report an error
“In short, we don’t track who a visitor is but rather what happens in a session. To achieve this, we identify sessions to tie past events and clicks to an order before computing aggregated statistics.”
Scores citing this record
- The CRO Consultant Consent & visitor tracking
- The Data Protection Officer Experiment types & delivery
- The Data Protection Officer Consent & visitor tracking
- The Data Protection Officer Snippet performance & flicker
- The E-Commerce Manager Experiment types & delivery
- The E-Commerce Manager Consent & visitor tracking
- The Growth Lead Experiment types & delivery
- The Growth Lead Consent & visitor tracking
- The Growth Lead Snippet performance & flicker
- The Product Engineer Experiment types & delivery
- The Product Engineer Consent & visitor tracking
- The Skeptic Experiment types & delivery
- The Skeptic Consent & visitor tracking
- The Skeptic Snippet performance & flicker