Initiates a job to export the raw, event-level tracking data for a specific experience.
This data includes individual visitor bucketing events, conversions, and transactions.
The export is typically delivered as a link via email due to potential size.
Useful for in-depth custom analysis or importing into external data warehouses.
The Knowledge Base article "Experiment Report" (Export & Download section) mentions this.
Each event's attribution is now carried alongside its existing browser, country, and device
context: the output gains a Campaign column (raw utm_campaign) and a Channel Class column
(Convert's derived five-value traffic-channel class, not the customer's raw utm_source
string) for every account that also holds the advanced-segmentation plan entitlement — see
below. This surface takes no breakdown parameter — unlike export_report's opt-in
attribution_breakdown — so these columns are present on every row whenever populatable and
entitled, never behind a request-level opt-in. A Content column (raw utm_content, the
ad-creative identifier) is included only when the exported event rows carry content values.
The raw-data read does not carry utm_content today. The Content column is therefore
omitted from the output entirely and is never emitted as an always-blank column. See
AttributionDimension and AttributionDimensionAvailability. Campaign values have no
length limit in this export.
All three attribution columns (Campaign, Channel Class, Content) additionally require the
advanced-segmentation plan entitlement (sudo users bypass this check): an account that holds
this endpoint's own experience_raw_export restriction but not advanced-segmentation still
receives its export — with the request, throttle, and every non-attribution column
unaffected — but with all three attribution columns omitted entirely from both the header
and every row, never emitted blank, the same convention already used above for the
Content column. This is a separate, additional gate layered on top of
experience_raw_export, neither replacing nor bypassing it: an account missing
experience_raw_export is still refused this endpoint's 403 regardless of its
advanced-segmentation entitlement, and the reverse is never true — advanced-segmentation
alone never unlocks this endpoint.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||