Resolution statistics

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 is measured against
US traffic only, excluding bots and cookieless requests, and is the one
to benchmark against.

Non-US traffic sits outside that benchmark but is mostly still eligible
for resolution. A visitor on a non-US IP can and does resolve, usually at
a lower rate, whenever their identity is already known to the graph. Use
the ip_country field on the events endpoints to scope results by
visitor country.

The exception is the EEA, the UK and Switzerland. Visitors on an IP in
those 32 countries are never resolved, because their law requires opt-in
consent for the profile data we would attach. Their events are still
collected and returned; only the identity is withheld. See "Where we do
not resolve visitors" in the event field catalog for the country list.

The funnel partitions all events into priority-ordered, mutually
exclusive buckets, so the buckets sum to total_events. Priority, not
resolution alone, decides the bucket: Safari events that did resolve
are counted under resolved, not safari, and international holds
every non-US event, resolved or not, because resolved counts only
addressable (US) resolutions.
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.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
uuid

Limit to a single project (workspace) you own. Returns 404 if the project does not exist or does not belong to your organization. Mutually exclusive with pixel_id.

uuid

Limit to a single pixel you own. Returns 404 if the pixel does not exist or does not belong to your organization (a malformed pixel_id returns 400). Mutually exclusive with project_id.

date

Start of a custom window (YYYY-MM-DD, UTC, inclusive). Must be sent together with end_date. When omitted, the default seven-day window is used.

date

End of a custom window (YYYY-MM-DD, UTC, inclusive). Must be a completed day (yesterday or earlier) so the counters have finished filling, and on or after start_date. The window counts both dates and may span at most 92 days (so end_date is at most 91 days after start_date); e.g. with start_date 2026-08-01 the latest accepted end_date is 2026-10-31, and 2026-11-01 returns 400.

Responses

400

Invalid parameters (e.g. a malformed date, an incomplete date range, both project_id and pixel_id, or a partial/future end_date).

401

Missing or invalid API credentials (X-Api-Key and/or X-Api-Secret).

404

The requested project_id or pixel_id does not exist or does not belong to your organization.

503

Resolution statistics are temporarily unavailable.

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json