Export experience data

Export order-level or line-item-level data for an experience (A/B test) as a CSV file.

POST /analytics/experience/{experienceId}/export

Returns a presigned S3 URL to download a CSV file containing the requested export data. The URL is valid for 15 minutes.

Parameters

• experienceId (path) — required. UUID of the experience.
• exportType — required. Type of export: orders, order_line_items, or order_reconciliation (see table below).
• startTs — optional 10-digit epoch timestamp in seconds. Defaults to experience start date.
• endTs — optional 10-digit epoch timestamp in seconds. Defaults to now or experience end date.
• filters — optional analytics filters object. See below and the Filters Reference for available fields.

Export Types

order_reconciliation columns

Unlike the other two export types, this one is a narrow audit list rather than a metrics export. It has five columns and one row per store order in the window — including orders excluded from the analysis, not only orders attributed to the experience — so it answers "why is this order not in my numbers?".

Because excluded orders are included, the row count is normally higher than the orders export for the same window.

Upsell columns

Both the orders and order_line_items exports identify lines that an Intelligems upsell put in the cart, so you can separate upsell revenue from organic revenue.

order_line_items adds one column:

The surfaces are mutually exclusive, so a line has exactly one value. Filter or pivot on this column to split upsell revenue from organic revenue. To see which variation an upsell line belongs to, use test_group_name, which is already in the export.

Scoping — what an empty value means

When the experience has its own checkout upsell blocks or onsite upsell components, upsell_type is scoped to them. checkout_upsell then means "added by this experience's checkout upsell", not "is an upsell of any kind". A line added by a different, concurrently-running upsell experience is left empty.

This is deliberate: it stops an export of one upsell test from attributing an overlapping test's upsells to itself. When the experience has no upsell surfaces of its own, no scoping is applied and the values mean "from any Intelligems upsell".

So read an empty upsell_type as "no upsell attributable to this experience", not strictly as "organic line item".

orders adds three order-level columns rolled up from the same scoped classification, so the two exports always agree on whether an order contains an upsell:

For a per-surface revenue split, use the order_line_items export and group by upsell_type, or request the per-variation upsell metrics from POST /analytics/resource/{experienceId} with includeUpsellMetrics: true.

Filters

This endpoint accepts the same filters as POST /analytics/resource/{experienceId}. Key filters include:

userBehavior sub-fields

All fields are optional booleans. Set to true to filter to only visitors who performed that action.

See the Filters Reference section for the full list of available filter fields.

Response Structure

The response contains:

Date Range Behavior

• When startTs and endTs are omitted, the date range defaults to the experience's full lifetime (start date through end/pause date or now).
• If the experience is paused or ended, the export is automatically truncated at the pause/end date.
• If the provided startTs is before the experience start date, it is clamped to the experience start. Similarly, endTs is clamped to the experience end/pause date.
• Clamping only applies to a window that overlaps the experience lifetime. A window that falls entirely outside it is rejected rather than clamped: HTTP 400 with { "error": "Requested time range falls outside the experience lifetime" }.

Presigned URL

The returned URL is a time-limited presigned S3 URL. It expires after 15 minutes (900 seconds). After expiry, the URL returns a 403 Forbidden. Call the endpoint again to generate a new URL.

Rate Limit: 20 requests per 60s window, refilling 10 tokens every 60s.