At a glance
Event Volume by Platform is a cohort metric tracked from Amplitude data. Shown as a donut, it splits total event volume across the platforms your shoppers use, such as web, iOS, and Android. The split tells you where engagement actually happens and, just as usefully, flags when one platform’s share collapses, which often means an SDK or release broke tracking on that surface rather than that shoppers left it. Cross-reference the related cards listed below for context.
| What it counts | Total event volume broken down by platform (for example web, iOS, Android), displayed by share, as exposed by the Amplitude integration. Computed from the latest available data and refreshed on the standard data refresh. |
| Sample type | Backend API data from Amplitude, refreshed on the standard data refresh. |
| Why it matters | The platform split shows where engagement concentrates and where to invest. It is also a tracking-health check: if one platform’s share suddenly drops to near zero, the likely cause is broken instrumentation on that surface rather than a real shift in shopper behaviour. |
| Reading the value | Read each platform’s share against its normal level rather than as an absolute target. A stable split is healthy; a platform falling sharply or rising sharply is the signal to investigate a release or an SDK change. Compare to the prior period for direction. |
| Currency | count |
| Time window | 30D |
| Alert trigger | - |
| Sentiment key | amp_platform_split |
| Roles | owner, marketing |
Calculation
Calculated automatically from your Amplitude data. The card sums event volume within the window and groups it by the platform property on each event, rendering the result as shares in a donut. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A representative reading of Event Volume by Platform for a typical merchant on Amplitude. In the 30 days to 12 Mar 26 the donut reads 71% web, 19% iOS, and 10% Android. In the 30 days to 19 Mar 26 it reads 79% web, 4% iOS, and 17% Android. The iOS share has collapsed, but total volume is steady, which is the tell that iOS shoppers did not leave - an app release likely broke the Amplitude SDK so iOS events stopped sending. Treating that as a behaviour change would mislead the mobile team into chasing the wrong fix. Vortex Mind can pin the iOS drop to a specific app version and release date; ask Ask Viq “which platform’s event share fell this month and when did it start” to confirm it is a tracking break before reallocating any budget.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
amp_event_volume | The total this donut splits; confirms whether a platform drop changed the overall figure. |
amp_top_events | Shows which events drive volume, useful when one platform’s share shifts. |
amp_dau | Daily active users, to check whether a platform shift reflects fewer users or fewer events. |
amp_new_vs_returning | Pairs the platform split with the new-or-returning mix for richer segmentation. |
amp_session_count | Session volume, to see whether a platform change tracks with sessions or just events. |
Reconciling against Amplitude
Where to look in Amplitude’s own dashboard: In Event Segmentation, chart total event count and group by the platform property to reproduce the split. Dashboards is where a saved version of this breakdown usually lives, and the Data or Govern section confirms how the platform property is populated across your event taxonomy. Confirm the period boundaries and any segment filters match the Vortex IQ profile to reconcile cleanly. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses a rolling 30-day window by default; Amplitude views may use calendar months. | Variable | Match the period range. |
| Time zone. Amplitude uses the project time zone; Vortex IQ aligns to the merchant reporting time zone, shifting which day events land in. | Marginal | Confirm time zone match. |
| Filter or segment scope. Profile-level filters (test traffic, internal users, specific event sets) may narrow the Vortex IQ view versus an unfiltered Amplitude chart. | Variable | Match filter settings. |