Generates an export of an experience's performance report in either CSV (aggregated or daily) or PDF format.
A synchronous export returns a downloadable link in data.download_url.
A routed breakdown returns an export id in data.jobId instead.
Useful for offline analysis or sharing with stakeholders.
The Knowledge Base article "Experiment Report" (Export & Download section) describes this.
Optionally, attribution_breakdown splits the export by the discovered values of a single
attribution dimension. The two non-tabular report types repeat one section per value.
The two tabular types, csv_aggregated_tabular and csv_daily_tabular, are flat CSVs with no
section header. They carry the attribution value in a column next to Goal.
Three dimensions are shipped and populated: campaign
(raw utm_campaign), content (raw utm_content, the ad-creative identifier), and
source (Convert's derived five-value traffic-channel class — campaign | search | referral | direct | ai_tool — not the customer's raw utm_source string). Three are
permanently unavailable and refused with 422 if requested: medium and term (captured
client-side but never stored anywhere in the reporting path) and utm_source (captured
client-side but dropped before transmission, so Convert never stores it). See
AttributionDimension for the full six-entry set and AttributionDimensionAvailability
for the shape a dimension picker can use to render all six with their availability.
A breakdown includes every discovered value, up to 5000 per experiment, selected top-by-volume.
The report's live segmentation uses the same cap and ordering.
When the cap cuts the list, the export states in its own content that it kept the top 5000 values and that further values exist.
The reporting store keeps campaign and ad-creative values without a length limit.
The breakdown therefore lists an over-long value like any other value.
A breakdown request takes one of two paths.
The synchronous path renders the export during the request and returns download_url and expire_at.
It never cuts a breakdown by value count or by time.
The request routes to the async path in two cases.
In the first case, the number of discovered values exceeds the current routing threshold.
The server configures that threshold per report type, and it is a routing rule, not a cap.
In the second case, a synchronous run reaches its time deadline, currently 120 seconds and configured server-side.
The async path queues the work, and the report worker renders the breakdown for the same report types.
The worker emails a download link to the requester.
The 200 response then carries the export id in data.jobId, with no download_url and no expire_at.
The async path includes every value up to the 5000 cap.
The reporting store keeps utm_content for every account.
Requesting any breakdown value at all requires the advanced-segmentation plan entitlement.
A request without it is refused with 403, and sudo users bypass this check.
A routed breakdown takes this endpoint's own plan gate.
It does not require the experience_raw_export plan function that export_raw_data requires.
A routed breakdown is throttled the way export_raw_data is, under its own budget.
That budget is separate from the export_raw_data budget, so a routed request can receive 429.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||