Source
Consent & visitor tracking — found from sitemap — Clerk.io
Checked for Clerk.io on 17 Nov 2026
- Page
- https://docs.clerk.io/docs/visitor-tracking
- 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:e619673b2f9fbee169bd9468a6d8037898b98c03b31ae5019251413eac968684
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Visitor tracking setup steps Report an error
“There are 4 things that need to be set up for the tracking to function: A unique visitor ID must be set for each device visiting the site. That ID must be sent as the visitor parameter for each API request made to Clerk.io on behalf of the visitor. Click tracking must be added to all products returned from Clerk.io. Sales / Order tracking must be set up on the order success page.”
-
Tracking purpose Report an error
“Tracking visitor behavior is an essential feedback-loop for Clerk.io. Tracking allows us to accurately determine how much Clerk.io affects your stores sales and provide you with better results, as tracking feedback is actively used by our algorithms.”
-
Visitor ID format Report an error
“We recommend generating an 8 character string from the set [a-zA-Z0-9] eg. aR9Km32l.”
-
Visitor ID device scope Report an error
“A visitor ID should only be unique to the device. Cross-device association is handled automatically by Clerk.io if we detect that a customer identifier is used with multiple visitor IDs.”
-
API visitor parameter Report an error
“Every time you make an API request you must send the visitor ID of the visitor you make the request on behalf of. This should be sent as the visitor parameter for the API request.”
-
API labels parameter Report an error
“You should also add a tracking label for each location. This is used in Clerk.io's reporting to attribute where the sale came from as the labels parameter.”
-
Click tracking endpoint Report an error
“This is done by calling the endpoint log/click when someone clicks on a product shown by Clerk.”
-
Click tracking rule Report an error
“Click tracking makes sure we only track a sale of a product via Clerk.io if the customer actually clicked on the presented product.”
-
Sale tracking endpoint Report an error
“This is done with the log/sale endpoint.”
-
Default setup automation Report an error
“By using any default Clerk.io setup all of the following will automatically be handled by Clerk.js.”
-
API base URL Report an error
“https://api.clerk.io/v2/log/sale”
-
Session attribution data Report an error
“From this data, we can determine exactly how Clerk.io affected this session, present this in your dashboards, and use as feedback for our algorithms so that they get smarter with every order.”
Scores citing this record
- The CRO Consultant Statistical method & guardrails
- The CRO Consultant Snippet performance & flicker
- The CRO Consultant Analytics, data export & integrations
- The Data Protection Officer Consent & visitor tracking
- The Data Protection Officer Snippet performance & flicker
- The Data Protection Officer Analytics, data export & integrations
- The E-Commerce Manager Snippet performance & flicker
- The E-Commerce Manager Analytics, data export & integrations
- The Growth Lead Consent & visitor tracking
- The Growth Lead Snippet performance & flicker
- The Product Engineer Statistical method & guardrails
- The Product Engineer Consent & visitor tracking
- The Product Engineer Snippet performance & flicker
- The Product Engineer Analytics, data export & integrations
- The Skeptic Statistical method & guardrails
- The Skeptic Snippet performance & flicker