Get data analysis
POST/openapi/2026-07/data-analysis
Retrieve analytical data for the specified time range and dimensions.
Request
- application/json
- Body
- Example
Bodyrequired
pv: Page viewsuv: Unique visitorsadd_cart_uv: Unique visitors who added to cartadd_cart_qty: Add-to-cart quantityadd_payment_info_uv: Unique visitors who submitted payment infobegin_checkout_pv: Begin-checkout page viewsbegin_checkout_uv: Begin-checkout unique visitorsorders: Number of orderssales: Total sales amountconversion_rate: Conversion rateimpression: Impression count UTM indicators (valid with UTM dimensions):pv: Page viewsuv: Unique visitorsadd_cart_uv: Unique visitors who added to cartbegin_checkout_pv: Begin-checkout page viewsbegin_checkout_uv: Begin-checkout unique visitorsorders: Number of orderssales: Total sales amountcountry_code: Country code UTM dimensions:utm_source: UTM sourceutm_medium: UTM mediumutm_term: UTM termutm_campaign: UTM campaignutm_content: UTM content
Start time, a Unix timestamp in seconds passed as a string, e.g. "1748736000"
End time, a Unix timestamp in seconds passed as a string, e.g. "1781481600". Should be greater than begin_time
Metrics to query. Categorized into two groups based on the requested dimensions: Custom indicators (valid with custom dimensions):
Cursor for pagination
Page size
10Notice: Values outside the range -12 to 14 might lead to unexpected results in time-based calculations. Time zone offset (in hours) used for analysis. Recommended range: -12 to 14
Sort by field
Sorting direction: asc (ascending) or desc (descending)
Time granularity for aggregation: dt_by_hour, dt_by_day
Notice: Mixing custom dimensions (e.g., country_code) with UTM-based dimensions will cause validation failure. Dimensions for the query. Categorized into two groups: Custom dimensions:
filters object
Simple equality filters, keyed by dimension name with the exact value to match,
e.g. {"country_code": "US"}. Each entry is an exact-match condition and multiple
entries are combined with AND. Only keys within the supported dimension set take
effect; unknown keys are ignored.
{
"begin_time": "string",
"end_time": "string",
"indicator": [
"string"
],
"cursor": "string",
"page_size": 10,
"time_zone": 0,
"sort_by": "string",
"sort_direction": "string",
"dt_by": "string",
"dimension": [
"string"
],
"filters": {}
}
Responses
- 200
OK
- application/json
- Schema
- Example
Schema
- Array [
- ]
error code
error message
data object
data object[]
Data list
Date and time
Country abbreviation
Country code (e.g. CN)
UTM source
UTM medium
UTM campaign
UTM term
UTM content
Page views
Unique visitors
Add-to-cart unique visitors
Add-to-cart quantity
Add-payment-info unique visitors
Begin-checkout page views
Begin-checkout unique visitors
Number of orders
Sales
Conversion rate
Impression count
Cursor for pagination
Whether there are more records
{
"code": "string",
"message": "string",
"data": {
"data": [
{
"date_time": "string",
"country_abbr": "string",
"country_code": "string",
"utm_source": "string",
"utm_medium": "string",
"utm_campaign": "string",
"utm_term": "string",
"utm_content": "string",
"pv": 0,
"uv": 0,
"add_cart_uv": 0,
"add_cart_qty": 0,
"add_payment_info_uv": 0,
"begin_checkout_pv": 0,
"begin_checkout_uv": 0,
"orders": 0,
"sales": 0,
"conversion_rate": 0,
"impression": 0
}
],
"cursor": "string",
"has_more": true
}
}