GET /reporting/metrics is the single, day-grain endpoint for delivery rollups and CSV exports. GET /advertisers/{advertiserId}/events/summary is the hour-grain endpoint for raw event counts. For the full model — the hierarchy, available metrics, CSV export, and how delivery data lands in the reporting pipeline — see the Reporting overview guide.
Reporting preserves the channel group
that compiled into each media buy. Summary responses return channelGroup on
each media buy, time-series responses return channelGroupId and
channelGroupName on each row, and CSV exports append both fields. Legacy or
ungrouped buys return null in JSON and blank CSV fields; Apostra does not
infer a group from delivery. REST callers can filter with channelGroupId.
To group an agent-side campaign-delivery report, use V3 get_delivery with the
channel_group dimension and optional filters.channelGroupId.
For a buyer agent using the V3 get_delivery query, campaign delivery can also
group rows by an account-owned label axis with dimensions: ["labels.<key>"]. The row uses the current labels on the campaign and its
advertiser; when neither has a value for that dimension it is grouped as
"Unlabeled". Labels are resolved when the report is read, so changing a
label reorganizes the full delivery history rather than only future delivery.
An unknown, retired, or inapplicable key is rejected with the account’s
available dimensions.
All requests use the base URL https://api.apostra.com/api/v2/buyer and a Authorization: Bearer $SCOPE3_API_KEY header.
Task Reference
Get reporting metrics
GET /reporting/metrics — hierarchical or time-series delivery metricsGet event summary
GET /advertisers/:id/events/summary — hourly event counts by typeReporting overview guide
The hierarchy, metrics, CSV export, and delivery flow
All reporting tasks
Per-operation reference