2.3 KiB
2.3 KiB
eas channel:insights JSON schema
Complete JSON output shape returned by eas channel:insights --channel <name> --runtime-version <version> --json --non-interactive.
{
"channel": "production",
"runtimeVersion": "1.0.6",
"timespan": { "start": "...", "end": "...", "daysBack": 7 },
"embeddedUpdateTotalUniqueUsers": 2401,
"otaTotalUniqueUsers": 8312,
"mostPopularUpdates": [
{
"rank": 1,
"groupId": "abc123",
"message": "Fix checkout crash",
"platform": "ios",
"totalUniqueUsers": 4210
}
],
"cumulativeMetricsAtLastTimestamp": [
{ "id": "...", "label": "Embedded update", "data": 12345 },
{ "id": "...", "label": "Embedded update failed installs", "data": 0 }
],
"uniqueUsersOverTime": { "labels": ["..."], "datasets": [ { "id": "...", "label": "...", "data": [100, 200] } ] },
"cumulativeMetricsOverTime": { "labels": ["..."], "datasets": [ { "id": "...", "label": "...", "data": [10, 20] } ] }
}
Field reference
| Path | Meaning |
|---|---|
channel |
The channel queried. |
runtimeVersion |
The runtime version filter used. Channel insights are always scoped to a single runtime. |
timespan.start / .end / .daysBack |
Window bounds (UTC ISO) and size in days. |
embeddedUpdateTotalUniqueUsers |
Distinct users running the embedded (binary-bundled) build in the window. |
otaTotalUniqueUsers |
Sum of totalUniqueUsers across mostPopularUpdates. May undercount if more than top-N updates are active (see caveat below). |
mostPopularUpdates[] |
Top-N updates ranked by totalUniqueUsers. Each entry has rank, groupId, message, platform, totalUniqueUsers. |
cumulativeMetricsAtLastTimestamp[] |
Snapshot totals at the end of the window, labelled (e.g., "Embedded update", "Embedded update failed installs"). |
uniqueUsersOverTime |
Chart-shaped object with labels (dates) and datasets for plotting unique users over time. |
cumulativeMetricsOverTime |
Chart-shaped object for plotting cumulative metrics over time. |
Caveats
otaTotalUniqueUsersis a sum ofmostPopularUpdates[].totalUniqueUsers. If more OTA updates are active than the top-N the server returns, this figure undercounts true OTA reach.- A user running the same publish on both iOS and Android may be counted on each platform. Don't treat
uniqueUsersas cross-platform-deduped.