Data

Visitors

Inspect and debug a single visitor's activity using the Visitor Log in my.clerk.io.
Visitors

Overview #

The Visitor Log lets you look up everything Clerk recorded for one visitor and is useful for debugging searches, recommendations, and page views. Each entry shows what was called, which inputs were used, what the API returned, and the context used to make the decision.

Where to find it #

  • Go to Data > Visitors in my.clerk.io.
  • Paste a Visitor ID and choose Search Visitor.

Get a Visitor ID #

Use the Visitor ID endpoint to retrieve the ID for the browser you want to inspect:

  • Open the store in the same browser where Clerk is active.
  • Visit https://api.clerk.io/v3/misc/visitor_id or call the Visitor ID endpoint. It returns an 8‑character ID such as SBWLDWSi.
  • Paste that ID into Data > Visitors.
The Visitor ID reflects an anonymous session as described in Data > Cookieless. If you change device, browser, or network, the Visitor ID may be different.

What the log shows #

For each recorded action, you will see a row with these columns:

  • API: The endpoint that was called (for example search/omni).
  • Labels: Any labels attached to the call (for example the UI surface such as “Omnisearch”).
  • Input: Parameters sent to the endpoint. Examples include the search query, a product ID the recommendations are based on, or a category/page identifier.
  • Output: IDs returned by endpoints that produce results (for example Recommendations like Popular, Category, or Alternatives). Calls that do not return a result list will have this empty.
  • Metadata: Context used for the call such as language, URL, filters, template IDs, pinned/excluded items, and synonym settings.
  • Time: When the event happened, newest first.

Typical uses #

  • Debug Search: Inspect recent search/omni calls to see the query, filters, and language used, and whether results were returned.
  • Verify Recommendations: Confirm which input (product/category/page) produced which result IDs, and review any filters or pins.
  • Validate Page Views: Check page- or template-related metadata to ensure the right context is sent.

Tips #

  • If Output is empty, look in Metadata for filters, language, or other settings that may explain why nothing matched.
  • Use the exact Visitor ID from the browser/session where you observed the behavior; different sessions will show different logs.
  • Ensure Clerk.js is installed on the page you are testing—no calls means nothing will appear in the log.