Skip to content

tracking_reports_event_volume

Traffic for a date range as TWO headline figures plus a data-quality block.

Tool

tracking_reports_event_volume

Traffic for a date range as TWO headline figures plus a data-quality block.

Traffic for a date range as TWO headline figures plus a data-quality block. totalEvents counts events. visitorsDeduplicatedPerUtcDay counts PEOPLE, over both populations at once: consenting and no-banner visitors by anonymous_id, cookieless visitors by server-derived daily_visitor_key. It is one COUNT DISTINCT, not a sum of two figures, and there is no second set of numbers to add to it. READ THE FIELD NAME LITERALLY — the daily key rotates every UTC midnight, so a returning cookieless visitor is counted again. From the rollout, that key also appears as anonymous_id = d:<daily key> on the event: a one-day graph person, never a toolkit profile. These visitors enter funnels, person counts and retention as separate people each day. Weekly and monthly uniques are OVERSTATED for this traffic; filter consent_statistics = true for consented-only figures and always for retention, returning-visitor, frequency and loyalty analysis. dataQuality.visitorsOverstated tells you whether the over-count applies to this window, and dataQuality.utcDaysInRange gives its UTC-day span. dataQuality describes how COMPLETE the two headline figures are and contains no metric of its own — never present anything inside it as a headline number and never add it to anything. cookielessShare and noBannerShare are the fractions of events from cookieless visitors and from sites with no banner. consentGrantedEvents + cookielessEvents + noBannerEvents = totalEvents. noBannerEvents (nobody was ever asked) stays distinct from cookielessEvents (denied or undecided). identifiedEvents counts only non-cookieless events carrying an anonymous_id, excluding d: rows; never add it to the consent buckets.

Behavior

HTTP
GET /tracking/reports/event-volume

Arguments

Name
Type
Required
Description
to
string
—
End of the range to count, inclusive (ISO 8601). Optional — defaults to the moment of the call.
from
string
—
Start of the range to count, inclusive (ISO 8601). Optional — defaults to 30 days back, the start of that UTC day.
domain
string
—
Count only this site. Omit to count every site the product sends from.

Response

Field
Type
Always
Description
to
string
•
End of the range the figures cover, echoed back (ISO 8601, UTC).
from
string
•
Start of the range the figures cover, echoed back (ISO 8601, UTC).
domain
string
•
Site the figures were restricted to; null when every site of the product is included.
computedAt
string
•
When this report was computed (ISO 8601, UTC).
dataQuality
object
•
How COMPLETE the two headline figures above are. Contains no metric of its own — never present a field of it as a headline number and never add it to anything. consentGrantedEvents + cookielessEvents + noBannerEvents = totalEvents.
totalEvents
number
•
How many events arrived in the range, across every consent state.
visitorsDeduplicatedPerUtcDay
number
•
How many PEOPLE those events came from: one COUNT DISTINCT over consenting visitors (by anonymous id) and declining visitors (by a daily key destroyed each UTC midnight) at once. Over a range longer than one UTC day this is an OVER-count of the declining half — read `dataQuality.visitorsOverstated` before reporting it.

Try it

Traffic for a date range as TWO headline figures plus a data-quality block.

When to use

Traffic for a date range as TWO headline figures plus a data-quality block. totalEvents counts events. visitorsDeduplicatedPerUtcDay counts PEOPLE, over both populations at once: consenting and no-banner visitors by anonymous_id, cookieless visitors by server-derived daily_visitor_key. It is one COUNT DISTINCT, not a sum of two figures, and there is no second set of numbers to add to it. READ THE FIELD NAME LITERALLY — the daily key rotates every UTC midnight, so a returning cookieless visitor is counted again. From the rollout, that key also appears as anonymous_id = d:<daily key> on the event: a one-day graph person, never a toolkit profile. These visitors enter funnels, person counts and retention as separate people each day. Weekly and monthly uniques are OVERSTATED for this traffic; filter consent_statistics = true for consented-only figures and always for retention, returning-visitor, frequency and loyalty analysis. dataQuality.visitorsOverstated tells you whether the over-count applies to this window, and dataQuality.utcDaysInRange gives its UTC-day span. dataQuality describes how COMPLETE the two headline figures are and contains no metric of its own — never present anything inside it as a headline number and never add it to anything. cookielessShare and noBannerShare are the fractions of events from cookieless visitors and from sites with no banner. consentGrantedEvents + cookielessEvents + noBannerEvents = totalEvents. noBannerEvents (nobody was ever asked) stays distinct from cookielessEvents (denied or undecided). identifiedEvents counts only non-cookieless events carrying an anonymous_id, excluding d: rows; never add it to the consent buckets.

Example

Ask your agent something like this:

Traffic for a date range as TWO headline figures plus a data-quality block.

The agent will invoke tracking_reports_event_volume with these arguments:

{}

Esc

Start typing to search the docs.

↑↓navigate↵select