Analytics

Tracking health

Where ad platforms and the CRM disagree, and how each contact was (or wasn't) matched.

GEThttps://traceeai.com/api/v1/analytics/tracking-health

CLI:tracee analytics tracking-health·MCP:analyticsaction tracking_health

Authorizations

Authorizationstringheaderrequired
Bearer <key>: a personal key (tracee login or Settings → Personal keys), a workspace key, or an MCP client's OAuth token. See Authentication.

Headers

Tracee-Workspacestring
For a personal key or OAuth token that reaches several workspaces: the workspace id to act on. Workspace keys don't need it.
uuid

Query parameters

daysintegerdefault: 30
Window in days, ending today
1–365

Response

Errors

200Done.
The action's result, exactly as the MCP tool returns it to agents. A next field, when present, names the endpoint that follows up.

{ "window": { "from": "2026-10-13", "to": "2026-11-11", "days": 30 }, "platforms": [], "attribution": { "contacts": 0, "byMethod": {}, "explanation": { "tracee_post": "First page view carried a Tracee post's utm_campaign tag", "utm_campaign": "utm_campaign matched a campaign's name or ID", "hubspot_source": "HubSpot's paid-source detail matched a campaign", "unmatched_no_source": "HubSpot recorded no UTM tag or paid source for the contact", "unmatched_no_campaign": "Had a UTM tag, but it matches no synced campaign or post", "unmatched_ambiguous": "UTM tag matches more than one campaign; not guessed", "not_processed": "Synced before source tracking existed; re-sync HubSpot to attribute" } } }