Return aggregate resolution-rate statistics for your organization,
rolled up across all of its pixels over the recent reporting window.
The headline number depends on which unit you look at. The event
rate counts pixel fires; the visitor (cookie) rate counts unique
people and is the honest per-visitor number, always lower because
resolved visitors generate many events while every bot or Safari hit
mints a throwaway cookie. The addressable rate excludes traffic that
can never resolve (bots, cookieless, and non-US visitors) and is the one
to benchmark against.
The funnel breaks the unresolved remainder into priority-ordered,
mutually exclusive buckets; Safari events that did resolve are counted
under resolved, not safari, so the buckets sum to total_events.
first_touch splits the rate by first-time vs returning visitors (the
most actionable view: returning visitors resolve far higher because
identity binds a cookie to a person over repeat visits).
Sections that need counters your data predates are omitted rather than
reported as zero.
By default the response aggregates every pixel in your organization over
the last seven completed days. The optional parameters below narrow it,
always within your own organization.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
400Invalid parameters (e.g. a malformed date, an incomplete date range, both project_id and pixel_id, or a partial/future end_date).
401Missing or invalid API credentials (X-Api-Key and/or X-Api-Secret).
404The requested project_id or pixel_id does not exist or does not belong to your organization.
503Resolution statistics are temporarily unavailable.
