Skip to main content
Configure how your app handles navigation, analytics events, and experience lifecycle callbacks.
Important (iOS)On iOS, callback instances must be stored in static fields to prevent the .NET garbage collector from finalizing them. The native Swift SDK holds weak Objective-C references to these objects, which the .NET GC cannot see.
Register callbacks before calling Setup() on Android so events fired during initialization are not lost. Register callbacks after calling Setup() on iOS.
Handles deep link routes triggered by Userpilot experiences (for example, when a user taps a CTA link inside an experience).

iOS

Android


Analytics Callback

Receives callbacks whenever the SDK tracks an event, screen, or identifies a user. Use this to integrate with another analytics tool or log events for debugging.

iOS

Android


Experience Callback

Receives callbacks when Userpilot experiences (flows, surveys, NPS) start, complete, are dismissed, or progress through steps. Experience Types: Flow, Survey, NPS Experience States: Started, Completed, Dismissed, Skipped, Submitted

iOS

Android