Explicitly prepare missing stored GA4 datasets

Ask the user before calling. Explicitly queue missing stored GA4 datasets for a granted site, with confirm=true. datasets is one to eight comma-separated names from get_ga4_datasets. Requests are deduplicated by the store; collection uses the manual analysis queue and Google quota. Does not spend Satellite credits, change schedules, or start other analyses. Poll the returned job/coverage rather than repeatedly preparing. The documented form sends query parameters on an empty-body POST. JSON is also accepted by the API, but do not mix it with query parameters. Work is deduplicated on analysis_queue and does not change schedules or charge Satellite credits. Poll GET /sites/{site_id}/ga4/jobs/{job_id}, then reread the report; do not poll by repeatedly preparing.

More context and worked examples are in the developer guide.

Example request

curl --fail-with-body --request POST \
  'https://satelliteai.io/api/v1/sites/123/ga4/store/prepare?window=previous_month&confirm=true' \
  -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

Ready, unsupported or empty-period preparation result. Inspect data.status. Explicit manual preparation. Equivalent work is deduplicated; schedules are unchanged. Fields can be absent depending on status.

202: Stored collection is queued; read coverage or the returned job status.

[] 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.