Skip to main content

Create Custom in-app Events

Create Custom in-app Events

Updated over a month ago

At a Glance: This article will help you to set up and customize in-app events on the panel.


Overview

Any user action that happens after the installation of your app is considered an In-App Event. These events provide valuable insights into how users interact with your app post-installation. Apptrove automatically tracks attribution-related events, but you can also create custom in-app events to monitor additional user behaviours like registration, purchase, level completion, etc.

Each event you create is assigned a unique Event ID, which is used during SDK integration for tracking.

Note: You can create and track multiple custom events based on your app flow or KPIs.

Steps to Create Custom Events

1. Access the Event Section:

Log in to your panel and navigate to the "Event" section from the main menu.

2. Add a New Event:

  • Click on "Add Event" to create a new custom event.

    Create Custom in-app Events

  • Give the event a descriptive Event name matching the in-app action you want to track (e.g., Signup, Purchase, Level_Completed).

    Create Custom in-app Events

3. Share the SDK Event ID:

  • After creating the event, you can share access to the SDK event ID with your team for SDK integrations.

    Create Custom in-app Events

  • In case you want to see the built-in event, you can choose the filter option and choose "Built-in events" under Event type. You can also filter your data based on the event ID and event name.​

    Create Custom in-app Events

Note: The correct mapping of the Event ID in your SDK integration is crucial for accurate event tracking.

Broaden Your Knowledge:



We are delighted to have assembled a world-class team of experienced professionals who are ready to take care of your queries and answer any questions you may have.
Feel free to reach out to us at any time by emailing us at support@apptrove.com or by using the in-platform chat feature. We'd love to hear from you!

Did this answer your question?