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.

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

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
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

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

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

A collection of filters used to segment experience report data based on various visitor attributes and traffic sources. Applying these filters allows for deeper analysis of how different user groups interact with experience variations. Knowledge Base: "Using Basic and Advanced Post segmentation".

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