Event types
Events are categorized in these three general groups:
| Category | Description |
|---|---|
| Builtin or Managed | Those are automatically collected events by SDK. As long as you properly integrated Pulse SDK you don't need to write any additional code to collect these events. You can't disable these events or modify predefined parameters. |
| Standard | There are two subtypes of standard events: |
| Custom | Those are fully manageable by the clients: you need to specify the event name, parameters and fire from target touchpoints. |
Builtin events
Default events
The Analytics SDK will collect the subsequent events automatically, regardless of user involvement, after proper initialization. To ensure the consistency of event chain analysis and prevent duplication, it is recommended not to call these methods explicitly by your application.
| Event Name | iOS SDK | Android SDK | Web SDK |
|---|---|---|---|
| "app_open" | + | ||
| "app_install" | + | ||
| "app_update" | + | ||
| "app_to_foreground" | + | ||
| "app_to_background" | + | ||
| "app_become_active" | + | ||
| "app_resign_active" | + | ||
| "app_close" | + | ||
| "settings_monitoring" | + | ||
| "settings_tracking" | + | ||
| "user_segments" | + | ||
| "user_experiments" | + | ||
| "experiment_participate" | + | ||
| "deeplink_opened" | + | ||
| "ntp_sync_info" | + | ||
| "tag_settings_monitoring" | +* | ||
| "setting_prefetch_monitoring" | +* |
* - Temporal service event that might be deprecated in the future without any announcement.
UI events
The Analytics SDK will collect subsequent events automatically if the app developer enables this feature through appropriate Public API calls.
| Event Name | iOS SDK | Android SDK | Web SDK |
|---|---|---|---|
| "page_load" | + | ||
| "page_view" | + | ||
| "click" | + | ||
| "items_impression" | + | ||
| "scroll" | + | ||
| "gesture" | + | ||
| "deeplink_received" | -* | ||
| "push_notification_received" | +** | ||
| "push_notification_clicked" | + |
* - Deferred Deep Link: The event for receiving a deferred deep link should be triggered by the host app.
** - APNs Push Notification: The event for receiving an APNs push notification should be explicitly triggered by the Notification App Extension of the host app.
Revenue events
The Analytics SDK will collect subsequent events automatically if the app developer enables this Revenue Tracking feature through appropriate Public API calls.
| Event Name | iOS SDK | Android SDK | Web SDK |
|---|---|---|---|
| "revenue_payment_start" | + | ||
| "revenue_payment_success" | + | ||
| "revenue_payment_fail" | + | ||
| "revenue_purchase_restored" | + | ||
| "revenue_payment_deferred" | + | ||
| "revenue_payment_refund" | + | ||
| "revenue_subscription_renewal" | + | ||
| "revenue_subscription_cancel" | + | ||
| "revenue_subscription_grace" | + | ||
| "revenue_subscription_expired" | + |