Analytics and reports
Delivery, subscription, event, conversion, funnel, provider health, engagement heatmap and retention reports; date ranges, comparison, CSV; the public analytics API and ClickHouse scaling.
Analytics are produced from delivery records (deliveries, delivery_events), events and conversions through hourly rollups. The dashboard Analytics page and the public API (analytics:read) serve the same reports; at high volume you can enable the ClickHouse analytics store (runbook).
Reports
| Report | Endpoint | Contents |
|---|---|---|
| Overview | GET /v1/apps/{app_id}/analytics/overview | Active subscriptions, send/delivery/open summaries |
| Messages | …/analytics/messages | Day × channel × campaign: sent, delivered, opened, clicked, bounce, complaint, error codes |
| Subscriptions | …/analytics/subscriptions | Growth: new, opt-out, invalid; breakdown by channel/platform |
| Events | …/analytics/events | Event volume (name × day), unique users |
| Conversions | …/analytics/conversions | Conversion count/revenue; direct_click and influenced attribution, per campaign/message |
| Funnel | POST …/analytics/funnels { steps: [{ name, where?: { key, value } }], from, to } (2–8 steps) | Per-step conversion and drop-off |
| Providers | …/analytics/providers | Provider error codes, latency p50/p95, success rate |
| Engagement | …/analytics/engagement | Day-of-week × hour heatmap (opens/clicks) |
| Retention | …/analytics/retention?weeks= | Cohort (first-session week) × return |
Common query parameters: from, to (ISO 8601, UTC), compare=true (compare with the previous period), format=json|csv (CSV text); the messages report also accepts group_by=day|channel|campaign. All parameters and examples: API → Analytics. In the server SDKs, use hs.analytics.messages({ from, to }) and similar.
Counters and definitions
| Counter | Definition |
|---|---|
targeted | Number of subscriptions in the audience |
suppressed | Suppressed by policy/preference/suppression (suppression_reason) |
sent | Accepted by the provider |
delivered | Provider/device delivery confirmation (received, email delivered) |
failed, errored, expired | Permanent failure, giving up after a temporary error, TTL expiry |
opened, clicked | Clicks/opens (push opened, email open pixel and link redirect) |
converted | Conversion event within the attribution window |
bounced, complained, unsubscribed | Email/SMS feedback |
sms_segments | Number of billed SMS segments |
Open/click counts are calculated from the timestamps on the delivery row (independent of the event retention period). Conversion: an event marked is_conversion in its event definition is attributed as direct_click when it happens within the window after the last click, and as influenced when there was only a delivery/open.
Message, campaign, journey and template statistics
- Message:
GET /v1/notifications/{id}→counts; deliveries via…/deliveries. - Campaign:
GET …/campaigns/{id}/stats, variants via…/variants/stats(campaigns). - Journey:
GET …/journeys/{id}/statsfor per-node transitions/conversions (journeys). - Template:
GET …/templates/{id}/stats. - In-app: impressions, clicks, dismissals, CTR (in-app).
Data export
- CSV export/import jobs: exports and imports.
- Event Streams: stream events to external systems with Liquid transforms and conditions (Event Streams).
- Data warehouse: scheduled exports to BigQuery, Snowflake and S3/Parquet (data warehouse).
- Analytics destinations: send events and sync cohorts to Segment, Amplitude and Mixpanel (integrations).
- Metrics: operational Prometheus metrics at
/metrics(status and monitoring).
Live event stream
The dashboard Events page shows a live event stream over SSE (recent events, properties, source); event definitions are recalculated daily with count_30d (event definitions API).
Feature flags
Turn a feature in your app on and off without shipping a new release, and roll it out gradually to a percentage of users. Text, number or JSON values also serve as remote configuration. Decision record:…
RFM segmentation
RFM groups users by three measures: how recently they last transacted (recency), how often they transact (frequency) and how much they spend (monetary). Pushizo gives each user a 1–5 score on these measures, derives a ready-made segment from the scores…