[UPDATED] How to Choose In-App Events

Before you integrate the Singular SDK,  decide which in-app events you want Singular to track. By tracking the right in-app events in your app, you can measure the success of your organization's marketing efforts through the KPIs that are important to you.

Once you have compiled a list of events, your developers can use the Singular SDK or S2S integration to send the chosen events to the Singular servers.

Guide for Marketing and User Acquisition Teams
Prerequisites None

Step by Step

1

Understand In-App Events

In-app events are any interactions the end-user has with your product, such as signups, logins, items being added to the shopping cart, level-ups in gaming apps. By measuring in-app events, you can evaluate the success of your marketing efforts based on the KPIs that are important to you.

Before your organization starts integrating the Singular SDK or S2S, think of the KPIs you want to measure, and list the in-app events that will help you measure them.

Singular supports a variety of standard events. These events are commonly supported by ad networks for reporting and optimization. We recommend using standard events whenever possible

In addition, we let you define your own custom events if your desired KPI doesn't match any of the standard events. Custom events can be viewed in Singular reports and are sometimes also used by ad networks for optimization.

With each event you track, you can pass various attributes. See our list of supported standard attributes.

For more about how events work in Singular reporting, see the Events FAQ and Ways of Measuring Events (Cohort vs. Actual, Unique, First).

2

Create a List of Standard Events to Implement

To help you get started, we have compiled a list of events commonly used for apps in specific verticals.

For example, for ecommerce apps, we recommend implementing events such as Product View, Add To Cart, and Checkout.

For each standard event, we recommend attributes to pass. For example, when you track "Content View" events, you should pass the following attributes: "Content Type", "Content ID", and "Content". Add the attributes to your list of events.

3

Add Custom Events if Needed

Your app's content or your marketing needs may require you to track in-app events that do not map to any of the standard events offered by Singular. In that case, you can use your own custom events.

Custom events will be measured in Singular reporting. Depending on the ad network, you may or may not be able to use them for optimization.

Note: Even if you define custom events, we still recommend using standard attributes wherever possible to pass data with the event. This will help ad networks report on your attributes. Standard attributes will also be reported by Singular in the near future.

4

Share the Event List with the Developing Team

Once your development team has the list of events, they can incorporate the events into the Singular SDK integration. The goal is for your app to report every chosen event as it happens to the Singular servers, so Singular can aggregate and analyze the information for you.

Depending on your chosen SDK or S2S implementation, your development team should use the events implementation guide for the appropriate SDK or. S2S implementation: