PushizoDocs
Analytics & data

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

ReportEndpointContents
OverviewGET /v1/apps/{app_id}/analytics/overviewActive subscriptions, send/delivery/open summaries
Messages…/analytics/messagesDay × channel × campaign: sent, delivered, opened, clicked, bounce, complaint, error codes
Subscriptions…/analytics/subscriptionsGrowth: new, opt-out, invalid; breakdown by channel/platform
Events…/analytics/eventsEvent volume (name × day), unique users
Conversions…/analytics/conversionsConversion count/revenue; direct_click and influenced attribution, per campaign/message
FunnelPOST …/analytics/funnels { steps: [{ name, where?: { key, value } }], from, to } (2–8 steps)Per-step conversion and drop-off
Providers…/analytics/providersProvider error codes, latency p50/p95, success rate
Engagement…/analytics/engagementDay-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

CounterDefinition
targetedNumber of subscriptions in the audience
suppressedSuppressed by policy/preference/suppression (suppression_reason)
sentAccepted by the provider
deliveredProvider/device delivery confirmation (received, email delivered)
failed, errored, expiredPermanent failure, giving up after a temporary error, TTL expiry
opened, clickedClicks/opens (push opened, email open pixel and link redirect)
convertedConversion event within the attribution window
bounced, complained, unsubscribedEmail/SMS feedback
sms_segmentsNumber 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}/stats for 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).

On this page