Skip to main content
GET
A tracking site is the top-level configuration object for Conversion Tracking — it groups the domains, API keys, funnels, and QR Codes that belong to one tracked property.
Requires the account’s CONVERSION_TRACKING quota. Creating a site additionally requires the SHARED_USER_CAN_ADD_CONVERSION_TRACKING permission and an active plan.
string
required
Display name for the site.
string
A stable 64-character random identifier for the site, generated on creation — this is the value the Conversion Tracking browser SDK/server API is configured with, not id.
boolean
Read-only, derived from verified_ontrue once you’ve verified ownership of at least one of the site’s domains.
The list response uses a slimmer shape than a single-site fetch — it omits domains/api_keys/qrs, which the Retrieve a tracking site endpoint includes.

Authorizations

Authorization
string
header
required

Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.

Response

200 - application/json

Paginated list of tracking sites.