Export raw tracking data for an experience

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.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
integer
required

ID of the account that owns the retrieved/saved data

integer
required
≥ 1

ID of the project to which save/retrieved data is connected

integer
required

ID of the experience

Body Params

Parameters for requesting an export of raw, event-level tracking data. Requires:

  • events: List of event types to include (e.g., 'view_experience', 'conversion', 'transaction').
  • goals: (Optional) List of goal IDs to filter conversion/transaction events.
    Also supports start_time, end_time, utc_offset, and segments. The export is typically delivered via an emailed link.

Base Parameters needed to drill down the reports.

events
array of objects

List of events to export

events
Allowed:
goals
array of integers | null

A list of goal Id's for which to return the tracking data.

If no ID is provided, the list of goals attached to the experience is being used.

goals
integer
-43200 to 50400
Defaults to 0

The time offset from Coordinated Universal Time (UTC) in seconds.
For example, UTC-5 (EST) would be -18000. UTC+2 would be 7200.
Used for interpreting or displaying date/time information according to a specific timezone.

number | null
0 to 4294967295

Unix timestamp (seconds since epoch) for the beginning of the reporting period. If null, data from the experience start is typically used. Should be interpreted with utc_offset.

number | null
0 to 4294967295

Unix timestamp (seconds since epoch) for the end of thereporting period. If null, data up to the current time is typically used. Should be interpreted with utc_offset.

segments
object

Conversion custom dimensions are stored only on conversion (hitGoal) and transaction (tr) events.
Each conversion_custom_dimension_N filter is applied when counting those events and is not applied
to visitor or bucketing (viewExp) events.
Website transactions recorded before the tracking script copies these dimensions onto the
transaction carry none, so filtered revenue for that period counts those transactions as zero.
Within one dimension, an event matches when it carries any listed value. Dimensions combine with AND.
Revenue and product counts are those of the whole matching transaction, not of the dimension value alone.
Requires the advanced segmentation plan function, the same as campaigns and custom segments.
Each value is matched exactly and is stored truncated to 32 characters.

stats_engine_processing

Overall settings for the statistical engine processing results for this experience.

Responses

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json