Skip to main content

Run stats

Stats are scoped to a completed run.
fillRates includes public result fields exposed by the run results endpoint. Examples below use BASE, API_KEY, AUDIENCE_ID, and RUN_ID from Build and export an audience.

Direct CSV download

Use the direct CSV endpoint when you want to stream a completed run as a CSV file immediately. The export is capped at 300,000 rows. Save and inspect X-Export-Truncated, X-Export-Row-Cap, and X-Export-Result-Count response headers before treating the file as a complete export. If it is truncated, use paginated results to retrieve the remaining population.
Check the HTTP status in audience-headers.txt before importing audience.csv; an error response can also be saved to that file.

Stored CSV exports

Use stored exports when you need a reusable export record and a signed download URL.
List stored exports:
Refresh a signed URL for a specific export:

Export behavior

  • Stored export URLs expire; call the export detail endpoint for a fresh URL.
  • POST /exports creates or reuses a CSV export for the completed run.
  • CSV rows are tied to the run snapshot identified by runId.

Next steps

  • Read Examples for a complete topic-to-export workflow.
  • Return to Audience runs to queue or inspect another snapshot.