Events are triggered when users interact with your app, website, and campaigns. Moreover, attributes help in understanding the events in a better way. Attributes include time, device details, user location, browser, quantity, and more.
NotifyVisitors offer different types of events - Custom Events, System Events, Default Events, and attributes - Custom Attributes, System Attributes.
Custom Events are the ones that can be added to a website and will be triggered on actions that are specific to that particular website. It can be anything that doesn't come under system events. For example, if a native lead form is present on the website and on submission of the same, a custom event can be configured, and attribute data of the same can be used to communicate with the lead further.
Custom events are created by website administrators to track certain events. These events get captured whenever a user performs certain actions. Custom events get recorded and reflected like this in NotifyVisitors Dashboard.
System Events are predefined actions users perform while interacting with apps and websites. These are integrated automatically when their respective campaigns are configured in the NotifyVisitors panel.
NotifyVisitors provide the following system events -
Push
- Push Registered
- Push Delivered
- Push Clicked
- Push Dismissed
- Push Unregistered
- Email Opened
- Email Clicked
- Email Unsubscribe
- Email Delivered
- Email Bounced
- Email Rejected
- Email Sent
SMS
- Sms Clicked
- Sms Sent
- Sms Rejected
- SMS Delivered
- Whatsapp Sent
- Whatsapp Read
- Whatsapp Delivered
Pop-Ups
- Popups Impression
- Popups Clicked
- Popups App Impression
- Popups App Clicked
NPS
- NPS Impression
- NPS Attempted
- NPS Completed
- NPS App Impression
- NPS App Attempted
- NPS App Completed
- NPS Activity
- NPS App Activity
Survey
- Survey Impression
- Survey Attempted
- Survey Completed
- Survey App Impression
- Survey App Attempted
- Survey App Completed
Android / iOS App
- App Install
- App Update
- App Uninstall
Custom Attributes: Custom Attributes will solely depend on the data points you choose to custom define and pass to your NotifyVisitors account via custom events. It can be anything related to customer data, for example, membership ID, Annual purchase, monthly spending, etc.
System Attributes are generic attributes (client system related) that are collected by default by NotifyVisitors whenever an event is triggered such as device, location, browser, country, and so on. Have a look at the table below.
| Attribute | Web | Android | IOS |
| Browser | Yes | No | No |
| OS | Yes | Yes | Yes |
| IP Address | Yes | Yes | Yes |
| Language | Yes | Yes | Yes |
| Platform | Yes | Yes | Yes |
| PWA / TWA | Yes | No | No |
| Time Zone | Yes | Yes | Yes |
| Search Engine | Yes | No | No |
| Location | |||
| City | Yes | Yes | Yes |
| Country | Yes | Yes | Yes |
| State | Yes | Yes | Yes |
| Longitude | Yes | Yes | Yes |
| Latitude | Yes | Yes | Yes |
| Region Code | Yes | Yes | Yes |
| Continent Code | Yes | Yes | Yes |
| Page | |||
| Page URL | Yes | No | No |
| Query Params | Yes | No | No |
| Referrer Source | Yes | No | No |
| UTM | |||
| UTM Source | Yes | Yes | Yes |
| UTM Medium | Yes | Yes | Yes |
| UTM Campaign | Yes | Yes | Yes |
| UTM Term | Yes | Yes | Yes |
| UTM Content | Yes | Yes | Yes |
| UTM Gclid | Yes | Yes | Yes |
| App | |||
| App ID | No | Yes | Yes |
| App Version | No | Yes | Yes |
| SDK Version | No | Yes | Yes |
| Screen Name | No | Yes | Yes |
| Google Advertising ID | No | Yes | No |
| Ios Advertising ID | No | No | Yes |
| Device Info | |||
| Android ID/ IOS Vendor ID | No | Yes | Yes |
| Manufacturer | No | Yes | Yes |
| Model | No | Yes | Yes |
| Carrier | No | Yes | Yes |
| Network Type | No | Yes | Yes |
| Wifi Enabled | No | Yes | Yes |
| Bluetooth Enabled | No | Yes | Yes |
Default Events
| Event Name | Triggering Logic | Description |
|---|---|---|
| Session Started (session_start) | This event is triggered in two cases: – When a new user visits a webpage or opens an app for the first time. – When a returning user reloads a page after being inactive for more than 30 minutes. | Marks the beginning of a user’s browsing session on your website or mobile app. A session represents a continuous period of user interaction and engagement. Tracking session starts helps measure website visits, unique users, and how often users return. |
| Page View (page_view) | Triggered automatically through the web SDK whenever a new page loads. Works independently of session tracking, so each page load (including reloads or navigation within a single-page application) fires a new page_view. Includes metadata like page URL, referrer, and UTM parameters if available. | Captures every instance of a user loading or navigating to a new page on your website. This helps in understanding how users explore different parts of your website and which pages attract the most attention. |
| Session Ended (session_end) | A session ends if the user is inactive for 30 minutes. A session is only marked as “engaged” if: – The user performs at least two tracked events, or – The session duration exceeds 10 seconds. | Represents the conclusion of a user’s interaction on your website. It helps differentiate between short-lived and meaningful sessions based on engagement and activity levels. |
| Screen View (screen_view) | Each time a user transitions to a new screen, the event records screen name, app version, and other context. This can be used for analyzing in-app behavior and navigation patterns. | Tracks each screen the user navigates to within your mobile app. It’s essential for analyzing how users interact with various parts of the app and identifying drop-off or engagement points within in-app flows. |
| App Installed (install) | Fired automatically the first time the app is launched in any of the following scenarios: – After a fresh installation of the app. – After the app is reinstalled or app data is cleared. – When an existing user installs the app on a second device. – When a user updates to the app version that includes the NotifyVisitors SDK for the first time. | Captures when a user first opens the mobile app after installation or under certain reinstallation conditions. It helps track new installs and monitor SDK adoption across devices and app versions. |
| App Launched (app_launch) | Triggered in two cases: – When a user opens the app from a fully closed/killed state. – When a user brings the app back to the foreground after 30 minutes of inactivity. | Captures every time a user opens your mobile application. It gives insight into how frequently users interact with the app and supports engagement analytics. |
| App Update (update) | Triggered when there’s a change in the app version between launches. The SDK compares the current app version with the previously stored version locally. If a difference is detected on app launch, the App Update event is triggered. | Tracks when a user launches a newly updated version of the app. It is valuable for understanding how quickly users adopt new versions and whether new features are reaching your audience. |
| App Uninstalled (uninstall) | Detected indirectly using silent push notifications. NotifyVisitors sends a silent push daily; if the push fails to reach the device for multiple days, the device is considered uninstalled. | Used to infer when a user has removed your mobile app from their device. While uninstalls cannot be directly detected by the app, they are critical for measuring churn. |
Default Events for E-commerce Stores
| Event Name | Triggering Logic | Description |
|---|---|---|
| Checkout Update | This event is fired whenever a user provides or updates shipping, billing, or payment details during checkout. | Helps monitor checkout progress, identify cart recovery opportunities, and analyze friction points within the funnel. |
| Order Place | Triggered at the final step of the purchase when the user places an order. | Captures order ID, amount, payment method, and product details to track revenue and enable post-purchase engagement. |
| Order Cancel | Triggered when a user cancels an order manually or if the order is invalidated from the backend due to issues like stock or payment failure. | Helps identify user churn and supports re-engagement campaigns or feedback collection. |
| Add to Cart | Fired as soon as the user clicks “Add to Cart” on any product. | Captures product ID, name, price, quantity, category, and more to support retargeting/cart abandonment campaigns. |
| Product View | Automatically triggered when the user lands on a product detail page. | Captures product ID, name, and category to analyze product interest, page popularity, and improve personalized recommendations. |
This is how Custom and system events and attributes will be shown in the NotifyVisitors panel. Also, you may have understood which events are available or unavailable for Web, Android, and IOS.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article