Visitor tracking and analytics
Visitor tracking and analytics
GET Get visitor page history — Returns tracked page history for one visitor in the current organization.GET Get visitor statistics — Returns aggregate visitor statistics for the current organization.Was this page helpful?
Update visitor profile
Partially updates operator-managed visitor contact details. Omitted fields remain unchanged; null or blank values clear a field without replacing unrelated visitor metadata. Authenticate with an organization API key sent in `X-API-Key` or as a Bearer token and carrying the exact `visitors:write` scope. API-key access also requires the Automation & API module (`automation_api`). Authorized dashboard sessions remain supported where the route already permits them. The request is isolated to the authenticated organization. Resource and site/project identifiers must belong to that organization; out-of-scope identifiers are not disclosed. Only supplied profile fields are changed. Updating identity or contact fields may refresh search indexes, realtime views, and downstream webhook payloads after commit. Retry behavior: Repeating the same request converges on the same resource state, but a retry may return a conflict or not-found response after the first request succeeds.
Get visitor page history
Returns tracked page history for one visitor in the current organization. Visitor tokens can only read their own history, while operators can read any visitor in the organization. `totalPages` is the number of entries returned in `pageHistory`. Authenticate with an organization API key sent in `X-API-Key` or as a Bearer token and carrying the exact `tracking:read` scope. API-key access also requires the Automation & API module (`automation_api`). Authorized dashboard sessions remain supported where the route already permits them. The request is isolated to the authenticated organization. Resource and site/project identifiers must belong to that organization; out-of-scope identifiers are not disclosed. Organization API keys and operator sessions can read an organization-owned visitor. Visitor bearer tokens remain limited to their own visitor identity by the route's explicit ownership check. Retry behavior: This read-only operation is safe to retry.