Auto-Tracked Events

The SDK records the events below automatically. You do not need to call track() for any of them, and doing so produces duplicate data — two rows for the same moment, which silently double-counts every metric built on it. These events can be used as:

Experiment conversion goals in the Console
Webhook triggers for server-side integrations
In-app message and survey triggers
Analytics filters in dashboards and exports

This page is generated from the SDK source. Every event below is emitted by a real call site in the iOS SDK (82 events). CI (pnpm check:auto-tracked-events) fails if the SDK gains an event that is not listed here, so the page cannot drift out of date.

Every event carries the session and identity context automatically — session_id, the anonymous id, and the user id once identify() has been called. The Key properties column lists what is specific to that event.

Session & lifecycle

Event	Trigger	Key properties
`session_start`	New session begins	—
`session_end`	30 minutes of inactivity or app enters background	—
`app_open`	App enters foreground	—
`app_close`	App enters background	—
`sdk_initialized`	`AppDNA.configure()` completes and the SDK is ready	—
`config_fetched`	A remote-config bundle is fetched (cold start, or a refresh)	—

Onboarding

Event	Trigger	Key properties
`onboarding_flow_started`	An onboarding flow begins	`flow_id` · `flow_version`
`onboarding_step_viewed`	A step is displayed to the user	`flow_id` · `step_id` · `step_index` · `step_type` · `selection_data`
`onboarding_step_completed`	User completes a step (e.g., answers a question)	`flow_id` · `step_id` · `step_index` · `selection_data`
`onboarding_step_skipped`	User skips a step	`flow_id` · `step_id` · `step_index`
`step_skipped`	A step is skipped through the advance path	—
`onboarding_completed`	The user reaches the end of an onboarding flow	`flow_id` · `paywall_id` · `completed_via` · `continue`
`onboarding_flow_completed`	User completes the entire flow	`flow_id` · `total_steps` · `total_duration_ms` · `responses`
`flow_completed_via_fallback`	The flow completes through the fallback path rather than the normal one	—
`onboarding_flow_dismissed`	User dismisses the flow before completing	`flow_id` · `last_step_id` · `last_step_index`
`onboarding_paywall_stay`	The user stays on the onboarding paywall instead of dismissing it	`flow_id` · `paywall_id` · `reason` · `completed_via` · `continue`
`onboarding_paywall_skip`	The user skips the onboarding paywall	`flow_id` · `paywall_id` · `reason`

Permissions

Event	Trigger	Key properties
`permission_prompted`	The SDK presents a system permission prompt during onboarding	`permission_type` · `flow_id` · `step_id` · `granted`
`permission_granted`	The user grants the permission	`permission_type` · `flow_id` · `step_id` · `granted`
`permission_denied`	The user denies the permission	`permission_type` · `flow_id` · `step_id` · `granted`
`permission_already_granted`	The permission was already granted, so no prompt was shown	`permission_type` · `flow_id` · `step_id` · `granted`
`permission_unavailable`	The permission cannot be requested on this device or OS version	`permission_type` · `flow_id` · `step_id` · `granted`

Paywalls & purchases

Event	Trigger	Key properties
`paywall_view`	A paywall is displayed	—
`paywall_close`	Paywall is closed	`paywall_id` · `dismiss_reason`
`purchase_started`	A purchase flow begins	`paywall_id` · `product_id`
`purchase_completed`	A purchase completes successfully	`product_id` · `price` · `currency` · `provider` · `transaction_id` · `paywall_id`
`purchase_pending`	A purchase is pending approval (e.g. Ask to Buy / deferred)	`paywall_id` · `product_id`
`purchase_canceled`	User cancels the purchase dialog	`paywall_id` · `product_id` · `pending`
`purchase_failed`	A purchase fails with an error	`paywall_id` · `product_id` · `error` · `error_type`
`purchase_restored`	A previous purchase is restored	`product_id` · `paywall_id` · `restored_count`
`purchase_restore_failed`	A restore fails	`paywall_id` · `error`
`purchase_request`	A screen flow requests a purchase from the host app	—
`restore_request`	A screen flow requests a restore from the host app	—

Subscriptions

Event	Trigger	Key properties
`subscription_started`	A completed purchase is an auto-renewing subscription — fires alongside `purchase_completed`	`product_id` · `price` · `currency` · `provider` · `transaction_id` · `paywall_id`
`subscription_renewed`	The store reports a renewal	`product_id` · `purchase_time`
`subscription_canceled`	The store reports the subscription cancelled	`product_id` · `purchase_time`
`subscription_renewal_failed`	The store reports a failed renewal (billing retry)	`product_id` · `purchase_time`

Web entitlements

Event	Trigger	Key properties
`web_entitlement_activated`	Web subscription becomes active	`plan_name` · `status` · `reason`
`web_entitlement_expired`	Web subscription expires or is canceled	`plan_name` · `reason`

Screens, flows & slots

Event	Trigger	Key properties
`screen_presented`	A server-driven screen is displayed	`screen_id` · `screen_name` · `duration_ms`
`screen_dismissed`	A server-driven screen is closed	`screen_id` · `screen_name` · `duration_ms`
`screen_action`	User taps a CTA or interactive element in a screen	`screen_id` · `action_type`
`screen_response_submitted`	A screen form is submitted	`screen_id` · `field_count`
`flow_started`	A multi-screen flow begins	`flow_id` · `flow_name` · `start_screen_id`
`flow_completed`	A multi-screen flow finishes	`flow_id` · `flow_name` · `start_screen_id`
`flow_abandoned`	A flow is dismissed before completion	`flow_id` · `flow_name` · `start_screen_id`
`interception_triggered`	A navigation interception fires and injects a screen	`trigger_screen` · `timing` · `screen_id`
`slot_registered`	A screen slot first renders in the app	`slot_name` · `platform` · `screen_id` · `screen_name`
`slot_rendered`	A slot displays content from a screen config	`slot_name` · `screen_id` · `screen_name`
`slot_empty`	A slot renders with no assigned content	`slot_name`
`message_request`	A screen flow requests an in-app message from the host app	—

In-app messages

Event	Trigger	Key properties
`in_app_message_received`	A message is delivered to the device	`delivery_id` · `trigger` · `source` · `consumed` · `message_type`
`in_app_message_shown`	An in-app message is displayed	`message_id` · `message_type` · `trigger_event` · `cta_action`
`in_app_message_clicked`	User taps an action in the message	`message_id` · `cta_action` · `url`
`in_app_message_dismissed`	Message is closed	`message_id`

Push

Event	Trigger	Key properties
`push_token_registered`	Device token is registered with AppDNA	`token_hash` · `platform`
`push_permission_granted`	User grants push notification permission	`granted` · `push_id`
`push_permission_denied`	User denies push notification permission	`granted` · `push_id`
`push_delivered`	A push notification is delivered to the device	`push_id`
`push_tapped`	User taps on a push notification	`push_id`

Surveys & feedback

Event	Trigger	Key properties
`survey_shown`	A survey is displayed	`survey_id` · `survey_type` · `trigger_event` · `question_id` · `question_type`
`survey_question_answered`	The user answers a survey question	`survey_id` · `question_id` · `question_type` · `answer`
`survey_completed`	User submits a survey response	`survey_id` · `survey_type` · `answers` · `user_id` · `platform` · `completed_at` · `context` · `app_version`
`survey_dismissed`	Survey is closed without completing	`survey_id` · `questions_answered` · `survey_type`
`feedback_form_submitted`	The user submits the free-text feedback form	`feedback`
`feedback_form_dismissed`	The user dismisses the feedback form	—
`survey_followup_prompt_review`	A survey answer routes the user to a review prompt	—
`survey_followup_feedback_form`	A survey answer routes the user to the feedback form	—
`survey_followup_winback`	A survey answer routes the user to a win-back offer	—
`review_prompt_shown`	A store review prompt is requested	`prompt_type`
`review_prompt_accepted`	The user engages with the review prompt	`prompt_type`
`review_prompt_declined`	The user declines the review prompt	`prompt_type`

Onboarding chat step

Event	Trigger	Key properties
`chat_message_sent`	The user sends a message in a chat onboarding step	`flow_id` · `step_id` · `turn` · `message_length`
`chat_message_received`	The assistant replies in a chat step	`flow_id` · `step_id` · `turn` · `message_count`
`chat_quick_reply_tapped`	The user taps a quick reply	`flow_id` · `step_id` · `quick_reply_id` · `turn`
`chat_rating_submitted`	The user rates the chat step	`flow_id` · `step_id` · `rating` · `turn`
`chat_completed`	The chat step completes	`flow_id` · `step_id` · `user_turn_count` · `total_messages` · `duration_ms` · `completion_reason` · `role` · `user`
`chat_webhook_error`	The chat webhook returns an error	`flow_id` · `step_id` · `turn` · `http_status` · `response_body`

Deep links

Event	Trigger	Key properties
`deep_link_handled`	A deep link is opened	`url`
`deferred_deep_link_resolved`	A deferred deep link is resolved on first launch	`path` · `params` · `visitor_id`

Experiments

Event	Trigger	Key properties
`experiment_exposure`	First `getVariant()` call per session per experiment	`experiment_id` · `variant` · `source`

Identity

Event	Trigger	Key properties
`identify`	`AppDNA.identify()` links the anonymous id to a user id	`anon_id` · `user_id`

Platform differences

The tables above are generated from the iOS SDK. Android, Flutter and React Native emit the same event names for the same moments — that parity is enforced by the shared behavioural fixtures in packages/sdk-shared-fixtures/ — but a platform may not implement every surface yet. If an event you expect never arrives, check the platform SDK page under SDKs before implementing it yourself.

Defining your own events

Anything not listed above is yours to define — the product moments no SDK can infer: the action that means a user got value, what counts as activated, the loop a healthy user repeats. See Events for the track() contract, and Analytics & feedback for how they reach your dashboards.

Before adding a custom event, search this page for the moment you are trying to capture. The two most common duplicates are onboarding_completed and subscription_started — both are already here.

​Auto-Tracked Events

​Session & lifecycle

​Onboarding

​Permissions

​Paywalls & purchases

​Subscriptions

​Web entitlements

​Screens, flows & slots

​In-app messages

​Push

​Surveys & feedback

​Onboarding chat step

​Deep links

​Experiments

​Identity

​Platform differences

​Defining your own events

Auto-Tracked Events

Session & lifecycle

Onboarding

Permissions

Paywalls & purchases

Subscriptions

Web entitlements

Screens, flows & slots

In-app messages

Push

Surveys & feedback

Onboarding chat step

Deep links

Experiments

Identity

Platform differences

Defining your own events