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 daily distinct cookies, summed over the window, and is the honest per-visitor number. Neither rate is guaranteed to be higher: active resolved visitors and throwaway bot or Safari cookies pull the cookie rate below the event rate, while crawlers and long-lived unresolved tabs pull the event rate down. The benchmark is addressable_human_rate: US traffic only, with bots, other automated visitors and cookieless requests removed. It is the Statistics page headline and the CSV summary's Addressable rate. Use addressable.rate only when addressable_human_rate is null; it still counts automated visitors, so it reads differently for the same dates.

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 website and Ads pixel in your organization (email pixels are never counted) over the last seven completed days. The dashboard's Statistics page opens on website pixels only, so send pixel_type=website to match it. The optional parameters below narrow it, always within your own organization.