Events
See every action Zappush tracks in your store, how often each fires, and how it moves through your funnel, all in one breakdown.
The Events screen shows every action Zappush tracks in your store: page views, product views, add-to-carts, checkouts, purchases, and any custom events you send. It tells you what fires, how often, and what it earns. Use it to spot the steps that are bleeding shoppers and the ones quietly driving revenue.
Like every analytics screen, Events has the shared time range selector and a Compare toggle that overlays the previous period and shows the percent change on each number.
Summary
Three cards across the top, and a fourth on some stores.
- Total events is the raw count of every tracked event in the period, across all event types. A small line under the number shows how it moved day by day, through yesterday.
- Attributed revenue is the revenue Zappush ties back to tracked events.
- Events tracked is how many distinct event types fired. Its hint breaks them down by stage, for example "6 top-of-funnel, 3 engage, 2 convert", plus any events not yet assigned to a stage.
- Extra event copies appears only if your store has any. Some setups re-send an action you already track under a second name, so one ad platform receives it under the name it expects. Those copies are not part of the counts beside them. If your totals drop after a cleanup, read this card first: it is usually the copies moving, not your shoppers.
Events over time
A chart of how many events your store tracked each day, with days counted in your store's timezone. It shows complete days, up to yesterday; today's running count is on the Total events card. Hover a day to see its count. With Compare on, a dashed line shows the previous period so you can see whether a drop is new or has been building.
Switch the chart from Total to By route or By event to see where the volume comes from. Each view draws your five biggest routes or event types as their own lines and groups the rest as Other. Hover a day to see that day's count for each line, largest first. When the total falls, the route view usually shows whether one source went quiet or everything dropped together. Compare applies to the Total view.
A sudden fall to near zero usually means tracking stopped on your site, not that shoppers left, so it is the first place to look after a theme change or a new app install. The chart is hidden while a route or domain filter is applied.
Event breakdown
The main table, one row per event type, in the natural journey order from first touch to purchase. Click a column heading to sort, for example Events to put the most frequent first, search by name, and filter by stage.
Each row has these columns:
- Event shows the friendly display name with the raw event name beneath it. You set the display name in Configure analytics.
- Stage is the funnel stage you assigned the event to: Top, Engage, or Convert. A colored dot matches the stage. Sorting by Stage follows the funnel.
- Events is how many times the event fired. With Compare on, the change from the previous period sits under it.
- Unique users is the number of distinct shoppers who triggered the event, not just the raw fire count.
- Trend is a small sparkline of the event's volume across the period.
The overall count is the Total events card above the table.
How to read it
- Leave the table in its default order to follow the shopper's journey from first touch to purchase, top to bottom.
- Sort by Events to see which events fire the most, then check the Stage column beside them to spot a top-of-funnel event that never leads anywhere.
- A high Events count with low Unique users means a few shoppers are repeating an action, which can hint at confusion or a loop on that step.
If an event you expect is missing, or shows up unclassified, head to Configure analytics to assign it a stage and a display name so it lands in the right place here and in the funnel.
Delivery health
Below the event breakdown, Delivery health shows what happened to those events once Zappush tried to send them to Meta: how many sent, how many carried the click-ID signal Meta uses for ad attribution, and how many Meta attributed to a campaign. The attributed figure sits beside the sent figure, not below it: Meta also counts view-through impressions and matches without a click ID, so it can legitimately be the larger of the two, and the section says so. The section also names the timezone it asked Meta for. If your store has no Meta ad account connected yet, this section says so instead of showing a delivery percentage.
Beneath the figures, tables break delivery out by campaign and by event type, and each opens full screen when it has more rows than fit. A workspace with no destination sees No destination connected with a link to set one up, instead of a table of zeros.
You may also see a warning here that reads something like "Your page fires two events for one action." It means one shopper action — a single click or purchase, say — is triggering two different tracked events together on the same page, so Meta counts it as two actions instead of one. The warning names the two events, how many sessions it affected, and the page it happened on. Fix the tracking on that page so the action fires only one event, and the warning clears once it does.
Where to go next
Overview
Your analytics home in Zappush: read sales, ad spend and return, where traffic and orders come from, and which products sell, all on one screen.
Sessions
Understand visitor volume over time in Zappush, plus where your traffic comes from, the countries it lands from, and the devices shoppers use.