event_type on the events endpoint. This page defines every type, the key fields it carries, and how the dashboard turns them into metrics.
Event types
event_type | Meaning | Key fields it carries |
|---|---|---|
flow_start | A flow began (was presented and started). | flow, version, placement, user, session |
screen_view | A screen became visible. | screen_id, screen_name, screen_index |
screen_exit | A screen was left. | screen_id, time_on_screen_ms |
flow_complete | The flow finished successfully. | time_since_flow_start_ms |
flow_exit | The flow was dismissed before completing. | the screen it exited on |
conversion | A revenue or goal event tied to the flow. | revenue, currency, plus product_id in properties |
experiment_exposure | The user was assigned to an experiment variant. | experiment_id, variant_id, variant_name |
element_interaction | A user interacted with an element. | element_id, element_type, interaction_type |
resolve_no_flow | A resolve returned no matching flow. | placement_id (no flow IDs) |
user_id, session_id, app_id, device_platform, sdk_version, timestamp, and (when applicable) flow_id, flow_version_id, placement_id, experiment_id, variant_id.
What the iOS SDK emits
The SDK fires seven automatic event types (AutomaticEventType), with these exact wire values:
flow_start, flow_complete, flow_exit, screen_view, screen_exit, experiment_exposure, element_interaction.
Two more exist that the SDK does not fire automatically:
conversionis sent explicitly viatrackConversion, not as an automatic lifecycle event.resolve_no_flowis recorded server-side by the backend when a resolve matches no flow. The iOS SDK does not emit it.
Mapping to dashboard metrics
The placement and dashboard analytics are built from these raw events:| Dashboard metric | Derived from |
|---|---|
| Impressions / Trigger Events | flow_start count |
| Completions / Flow Completions | flow_complete count |
| Completion Rate | flow_complete divided by flow_start |
| Funnel reach per screen | distinct sessions with screen_view for that screen |
| Funnel drop-off | distinct sessions with flow_exit on that screen |
| Time per screen | mean time_on_screen_ms from screen_exit |
| Element engagement | element_interaction rows grouped by element |
| Experiment exposures | experiment_exposure count per variant |
conversion events carry revenue and currency. See Placement analytics and Reading results.
Reading these in your app
Your app can observe every event (includingconversion) through the SDK analytics callback. The callback fires in-process for each event the SDK enqueues. See Analytics integration for the AnalyticsEvent shape and how to forward events to your own analytics.