Get daily performance report for an experience

post

https://api.convert.com/api/v2/accounts/{account_id}/projects/{project_id}/experiences/{experience_id}/daily_report

Retrieves a day-by-day breakdown of performance metrics (visitors, conversions, conversion rate, etc.) for a specific experience and goal. This allows trend analysis and observation of how an experiment performs over time. Supports filtering by date range and segments, and can show cumulative or non-cumulative data. The Knowledge Base article "Experiment Report" (Graphs section) visualizes this type of data.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

account_id

integer

required

ID of the account that owns the retrieved/saved data

project_id

integer

required

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

experience_id

integer

required

ID of the experience

Body Params

Parameters to customize the daily performance report. Requires:

goal: The ID of the specific goal for which daily data is requested.
report_type: 'cumulative' or 'non_cumulative' data.
metric: The primary metric for the daily report (e.g., 'conversion_rate', 'avg_revenue_per_visitor'). Also supports start_time, end_time, utc_offset, and segments for filtering.

Base Parameters needed to drill down the reports.

goal

number

Goal's ID for which to return the reporting data

report_type

string

enum

Determines how daily data is aggregated in time-series reports.

Allowed:

metric

string

enum

The specific performance metric to be displayed in a daily report.

Allowed:

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

utc_offset

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.

start_time

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.

end_time

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.

stats_engine_processing

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

Headers

report_token

string

Token to access the experience report in read-only mode.

Responses

200A day-by-day breakdown of performance metrics for an experience, specific to a single goal and metric (e.g., daily conversion rate for "Purchases"). Includes data for each variation.

defaultIndicates an error occurred while processing the request. The code provides an HTTP status code, message offers a human-readable explanation or an array of validation errors, and fields (if present) specifies which input fields were problematic.