> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/customer-data/events/netmera-events.md). # Netmera events Reference for automated and standard events the Netmera SDK tracks, and how custom events extend them. Track Netmera events in your app to understand user behavior and app performance. Netmera provides automated and pre-defined standard events. You can also create custom events.
Overview of Netmera event types
### Standard events #### Automated events The Netmera SDK tracks these events automatically after you integrate it into your app. They show how users engage with your app, from installation through ongoing use. * **Install (First open) app**: Captures the first app open after installation. * **App opens**: Tracks every app open. * **Time passed inside the application**: Measures the duration of each foreground session. * **Push receipts**: Records when a push notification is received (requires configuration from the Dashboard). * **Push opens**: Logs when a user opens a push notification. * **Geofence actions**: Monitors enter/exit actions for geofence regions if they are set up. * **Web view actions**: Tracks actions taken inside web views presented by Netmera. * **Log event**: Triggers when an error occurs in the app. #### Pre-defined events Netmera provides these built-in events for tracking specific user actions in your app. * **Screen View Event**: Logs when a specific screen is viewed. * **Login Event**: Captures user login actions. * **Register Event**: Tracks user registration actions. * **Search Event**: Records search actions performed by users. * **Share Event**: Logs when content is shared from the app. * **In-App Purchase Event**: Captures in-app purchase transactions. * **Banner Click Event**: Tracks clicks on banners within the app. * **Category View Event**: Logs views of specific categories. * **Battery Level Event**: Monitors the battery level during app usage. * **Product View Event**: Tracks when a product is viewed. * **Product Rate Event**: Logs when a product is rated. * **Product Comment Event**: Captures comments made on products. * **Order Cancel Event**: Records when an order is canceled. * **Purchase Event**: Logs completed purchase transactions. * **Cart View Event**: Tracks views of the shopping cart. * **Add To Cart Event**: Captures when items are added to the cart. * **Remove From Cart Event**: Logs when items are removed from the cart. * **Add To Wishlist Event**: Tracks when items are added to a wishlist. * **Content Comment Event**: Captures comments made on content. * **Content Rate Event**: Logs ratings given to content. * **Content View Event**: Tracks views of media content. Use these events to understand user interactions and improve your app experience. ### Custom events If the SDK's default events don't meet your needs, create custom events in the Netmera Dashboard. Use custom events to track actions specific to your app. To create a custom event: 1. In the Netmera Dashboard, select **Developers** → **Events**. 2. Select **Create New Event**. 3. Define event attributes, set data types, and specify required parameters. After you create a custom event, the Netmera Dashboard generates the required source files. Integrate the files into your project. The next page shows the code for triggering the event. See the [Broken mention](broken://pages/SSCbVwGXAPxKrDyx80Ru) for event integration guidance. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://user.netmera.com/netmera-user-guide/customer-data/events/netmera-events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.