1. Measure adoption of a newly released feature closely

Goal : Identify potential issues with the feature's usability or value proposition and take corrective actions to drive adoption.

How to set up? 

Metric Type :

• Coded events : This can be coded events specific to the feature released. If you do not have events instrumented, you can ask you developers to send over the events related to the new feature and track those events. 
• Screens: Screens can also be used that are related to the specific feature released. 

Select the time frame, remember the time frame defines the period of time we consider for your metric: if you select last 7 days, we will look at the value of your metric on the last 7 days. 

2. Track your app's performance

Goal: Optimize app performance and get alerted about sudden issues. 

How to set up? 

Metrics Type : To track performance issues, you can use the following:  

• Crashes
• UI freezes
• Rage taps →Sessions > Gestures > rage tap number

Metric: Based on what you're monitoring, you can select count of issue, or count of users with issue, count of sessions with issue. 

3. Track abnormal drops in user engagement

Goal: Track user engagement metrics , significant decreases in these can indicate a decline in user engagement, prompting further investigation and action to address potential issues.

How to set up? 

Metrics type :

• Session  
• Users 

Metric: For each metric type, there are several metrics you can watch out for. 

• Session > Count of new users
• Session > Session duration 

• Users > Count of users

• Users > Engagement time per user

4. Track conversation rates changes

Goal: By setting up alerts to detect decreases in conversion rates, app owners can identify friction points and optimize the user journey to improve overall conversion performance.

How to set up? 

Metrics type : Conversion rate %

Set your threshold, if the conversion falls below a certain threshold the alert is triggered. 

Note:  When setting alerts for conversion rates (which are already percentages), the trigger is based on a percentage change of the percentage. For example, a 5% increase in a 20% conversion rate would result in a new rate of 21%, not 30%. This is different from percentage point changes.

6. Track Event ratio alerts  

Goal: This alert would notify you when the ratio of a specific event (like failed logins or UI freezes) to total app launches exceeds or falls below a certain threshold, allowing you to quickly identify significant changes in user behavior patterns.

How to set up? 

 

7. Celebrating Wins

Alerts aren't just for spotting problems—they're also for celebrating wins. In the midst of daily tasks, it's easy to miss progress. Alerts help highlight successes, keeping the team motivated and focused on making a difference.

Set an alert when an important metric reaches a target for the team.