This document lists all system events tracked by the Smartech SDK. Each event has an event ID, event name (sent to the backend), a short description, and a capture type.
Capture Type
Type
Meaning
Auto captured
SDK tracks the event automatically when conditions are met; no extra app code required beyond basic SDK integration.
Integration driven
Event is tracked only when the app integrates the SDK and performs specific flows or API calls (e.g. first launch for install/update/reinstall, login/logout, showing double opt-in, pushing profile or opt-in state).
When feature used
Event is tracked only when that feature or module is used (e.g., in-app when an in-app is shown, geofence when geofencing is active)
1. Device & App Lifecycle
Event ID
Event name
Description
Capture type
99
device_common_data
Device/common data dump: device, app, and SDK metadata sent for sync/identification.
Auto captured
20
app_installed
Fired when the app is installed (first launch after install).
Integration driven
81
app_updated
Fired when the app is updated to a new version.
Integration driven
21
regular_app_launched
Fired when the app is launched (regular open).
Auto captured
83
app_reinstalled
Fired when the app is detected as reinstalled (uninstall + install).
Integration driven
26
device_updated
Device details updated (e.g. after significant device/app info changes).
Auto captured
2. Location
Event ID
Event name
Description
Capture type
89
app_location_enabled
App/location fetch has been enabled (user or app granted location).
Auto captured
90
app_location_disabled
App/location fetch has been disabled or revoked.
Auto captured
3. Push Notification – Token
Event ID
Event name
Description
Capture type
86
pn_token_generated
Push notification (FCM/other) token was generated successfully.
Auto captured
87
pn_token_failed
Push token generation or registration failed.
Auto captured
88
pn_token_refreshed
Push token was refreshed (e.g. new FCM token).
Auto captured
4. Push Notification – Engagement
Event ID
Event name
Description
Capture type
18
pn_rendered
Push notification was rendered/displayed to the user.
When feature used
12
pn_delivered
Push notification was delivered (and typically shown).
When feature used
13
pn_clicked
User clicked/tapped the push notification.
When feature used
14
pn_dismissed
User dismissed the push notification.
When feature used
19
pn_replied
User replied to the push (e.g. inline reply).
When feature used
5. Push Notification Permission – Double Opt-in
Event ID
Event name
Description
Capture type
76
pn_double_opt_in_viewed
User was shown the push double opt-in prompt.
Integration driven
77
pn_double_opt_in_allowed
User allowed push in the double opt-in flow.
Integration driven
78
pn_double_opt_in_denied
User denied push in the double opt-in flow.
Integration driven
6. In-app Messaging
Event ID
Event name
Description
Capture type
41
inapp_viewed
In-app message was viewed by the user.
When feature used
42
inapp_clicked
User clicked on the in-app message (or CTA).
When feature used
43
inapp_closed
In-app message was closed/dismissed.
When feature used
7. App Inbox
Event ID
Event name
Description
Capture type
44
inbox_delivered
Message was delivered to the app inbox.
When feature used
45
inbox_viewed
User viewed a message in the inbox.
When feature used
46
inbox_clicked
User clicked on an inbox message.
When feature used
47
inbox_dismissed
User dismissed an inbox message.
When feature used
8. User Identity & Session
Event ID
Event name
Description
Capture type
22
user_logged_in
User logged in (identity set via SDK).
Integration driven
23
user_logged_out
User logged out (identity cleared).
Integration driven
40
user_profile_push
User profile/attributes were pushed/updated to the platform.
Integration driven
9. Opt-in / Opt-out (App & User Level)
Event ID
Event name
Description
Capture type
84
app_pn_opt_in
App-level push notifications enabled (e.g. system permission granted).
