Read published GA4 facts with exact interval provenance

Requires analytics:read and site access. Uses contract_version 2 and the same canonical storage as the original GA4 endpoint. Window defaults to 30 completed property-local days. Query accepts window, limit (1-500), offset, and a pinned report_set_id. A missing interval returns pending, never zero or a live fallback. POST to the same path with a JSON object containing window, limit, offset and optional report_set_id to prepare missing data on the regular async worker. Retain report_set_id for stable exact-range pagination; daily sessions_over_time and audience_funnel use dates and offsets without a report_set_id. New dataset names include pages, pages_engagement, acquisition, manual_campaigns, event_totals, and manual_campaign_totals. Collection job IDs can be polled at /sites/{site_id}/ga4/jobs/{job_id} using analytics:read.

More context and worked examples are in the developer guide.

Example request

curl --fail-with-body \
  'https://satelliteai.io/api/v1/sites/123/ga4/store/reports/sessions_over_time' \
  -H "Authorization: Bearer $SATELLITE_API_KEY"

Replace the example IDs with values returned by the discovery endpoints. Example values are placeholders, not real records.

Parameters

Unknown or repeated query parameters return 400.

Data dictionary

Typed columns and rows plus dates, binding, coverage and quality metadata.

202: Report preparation or collection pending

[] marks an array element. nullable means the value can be null; treat it as unknown, not zero. always present means the key is always included in the object.

Response metadata

Error responses

Errors return {"error": {"code", "message", "request_id"}}. See error handling for retry guidance.