ShepHertz has added an Event API to its broad gamut of services. The Event API is a powerful analytic API and allows the developer to track app events as well as real-time sessions of mobile apps and web apps. This also helps in tracking your Page views/Button clicks/Downloads/App Open/App Close/Installs/DAUs and user activity in your app.
App42 provides a powerful management console to track and analyze these events in just few clicks. It also provides an option to drill down your data based on custom and app properties like country/city/device model/OS etc. This does not only help you in analyzing the data, one can also take actions such as sending Push notifications/In-app messages/Emails to target users who have executed certain events. Segmentation features add more power to the drilling option where one can see the list of users based on events and properties.
The developer needs to enable this service from the App42 dashboard and can be used just like any other service of App42. Refer to the following steps in order to get started
Login to AppHQ console > App Manager > Settings > Select your app > Analytics State. (Go to Getting Started if you are not registered or if you have not created an app)
Once you have enabled it form the console, you have to initialize it as usual and build the service as shown below in code snippet.
Events are actions inside your app that are being taken by your app users. These actions could be important parameters on which you can measure the success of your app. These form the key matrix which you can track and monitor to analyze business performance. For example: Game Play, Registration, Photo share, Checkout, Payment are some actions that you might be interested in tracking and analyzing inside your app. These events could be any actions that you want to put in the funnel and analyze for conversion too.
Property is an extra information that you want to track along with event. For example, tracking age/gender of the user who is doing the event. Having this field in the query builder facilitates further drilling down of the data that you have on events.
When you track an event, some of the properties are sent along with the request and managed by the SDK itself; you donâ€™t have to pass this as a property in the method call. These properties include app version, device model, browser, browser version, carrier info, OS, OS version,Screen dpi, height and width.
Define Properties that you want to tag users with on occurrence of events and track how many such tagged users have executed various events. For example, you can tag a user with property type paid once he has done some in-app purchase and then you can track how many times a particular event (e.g. game play event) occurs for these paid users.