Every mobile app should track these core events: app_opened (session start), onboarding_completed (activation), core feature events (value delivery), and conversion_completed (business outcome). Start with 10-15 events covering your key user journey, then expand based on specific questions.
๐ฏ The "Minimum Viable Events" Philosophy
Most analytics implementations fail not because they track too little, but because they track too much. Teams instrument hundreds of events, then drown in data they never analyze.
The better approach: Minimum Viable Events (MVE). Start with the smallest set of events that answers your critical questions. Add more only when you have a specific question that current events can't answer.
The MVE Framework
๐ก The Golden Rule
Before adding any event, ask: "What decision will this event help me make?" If you can't answer clearly, don't add it.
๐ 6 Universal Events Every App Needs
Regardless of your app category, these events form the foundation of any analytics implementation:
app_opened
Must-have
When: App launches (cold start or from background)
Why: Measures session volume, calculates sessions per day/week, baseline for all funnel conversions
onboarding_started
Must-have
When: User sees first onboarding screen
Why: Denominator for onboarding completion rate
onboarding_completed
Must-have
When: User finishes last onboarding step
Why: Activation metricโusers who complete onboarding are far more likely to convert
signup_completed
Must-have
When: User creates an account (if applicable)
Why: Key conversion point for apps requiring accounts
[core_feature]_used
Must-have
When: User engages with your app's primary value proposition
Why: Measures whether users experience your app's core value (e.g., photo_edited, workout_completed, message_sent)
conversion_completed
Must-have
When: User completes your primary business goal
Why: Your north star metric (e.g., purchase_completed, subscription_started, booking_confirmed)
๐ E-commerce & Shopping Apps
Shopping apps need to track the purchase funnel from discovery to checkout. Here's your starter set:
E-commerce Event Template (12 events)
| Event | Funnel Stage | Priority |
|---|---|---|
app_opened |
Session | Must-have |
search_performed |
Discovery | Must-have |
category_viewed |
Discovery | Nice-to-have |
product_viewed |
Consideration | Must-have |
cart_item_added |
Intent | Must-have |
cart_item_removed |
Intent | Nice-to-have |
cart_viewed |
Intent | Nice-to-have |
checkout_started |
Conversion | Must-have |
checkout_shipping_entered |
Conversion | Nice-to-have |
checkout_payment_entered |
Conversion | Nice-to-have |
checkout_completed |
Conversion | Must-have |
wishlist_item_added |
Engagement | Nice-to-have |
๐ก E-commerce Quick Start
Start with just 6 events: app_opened, product_viewed, cart_item_added, checkout_started, checkout_completed, and search_performed. This covers your core funnel.
โก SaaS & Productivity Apps
Productivity apps focus on activation (getting users to the "aha moment") and feature adoption:
SaaS Event Template (14 events)
| Event | Funnel Stage | Priority |
|---|---|---|
app_opened |
Session | Must-have |
signup_started |
Acquisition | Must-have |
signup_completed |
Acquisition | Must-have |
onboarding_started |
Activation | Must-have |
onboarding_step_completed |
Activation | Nice-to-have |
onboarding_completed |
Activation | Must-have |
project_created |
Core Value | Must-have |
task_created |
Core Value | Must-have |
task_completed |
Core Value | Must-have |
feature_discovered |
Engagement | Nice-to-have |
export_generated |
Value Delivery | Nice-to-have |
invite_sent |
Growth | Nice-to-have |
upgrade_started |
Revenue | Must-have |
subscription_started |
Revenue | Must-have |
๐ฐ Content & Media Apps
Content apps measure consumption and engagement. The key question: Are users finding and consuming content?
Content App Event Template (11 events)
| Event | Funnel Stage | Priority |
|---|---|---|
app_opened |
Session | Must-have |
feed_viewed |
Discovery | Nice-to-have |
search_performed |
Discovery | Must-have |
article_viewed |
Consumption | Must-have |
video_started |
Consumption | Must-have |
video_completed |
Consumption | Must-have |
content_shared |
Engagement | Must-have |
content_saved |
Engagement | Nice-to-have |
comment_posted |
Engagement | Nice-to-have |
notification_enabled |
Retention | Nice-to-have |
subscription_started |
Revenue | Must-have |
๐ฎ Gaming Apps
Gaming apps track progression and monetization. The key metrics: How far do players get? When do they spend?
Gaming Event Template (13 events)
| Event | Funnel Stage | Priority |
|---|---|---|
app_opened |
Session | Must-have |
tutorial_started |
Onboarding | Must-have |
tutorial_completed |
Onboarding | Must-have |
level_started |
Progression | Must-have |
level_completed |
Progression | Must-have |
level_failed |
Progression | Nice-to-have |
achievement_unlocked |
Engagement | Nice-to-have |
item_collected |
Engagement | Nice-to-have |
store_opened |
Monetization | Must-have |
purchase_started |
Monetization | Must-have |
purchase_completed |
Monetization | Must-have |
ad_watched |
Monetization | Nice-to-have |
friend_invited |
Growth | Nice-to-have |
๐ฅ Social & Community Apps
Social apps focus on content creation and interaction. The key: Are users creating and engaging?
Social App Event Template (12 events)
| Event | Funnel Stage | Priority |
|---|---|---|
app_opened |
Session | Must-have |
signup_completed |
Acquisition | Must-have |
profile_completed |
Activation | Must-have |
post_created |
Creation | Must-have |
post_viewed |
Consumption | Must-have |
post_liked |
Engagement | Must-have |
comment_posted |
Engagement | Must-have |
user_followed |
Connection | Must-have |
message_sent |
Connection | Nice-to-have |
content_shared |
Growth | Nice-to-have |
invite_sent |
Growth | Nice-to-have |
subscription_started |
Revenue | Must-have |
๐ซ Events NOT to Track
Knowing what not to track is as important as knowing what to track. These anti-patterns create noise without value:
โ Every button tap
Don't track back_button_tapped, menu_button_tapped, close_button_tapped. Track meaningful actions, not UI interactions.
โ Automatic screen views for every screen
Don't use automatic screen tracking that fires for every view controller or activity. This creates hundreds of events without insight. Track screens selectively.
โ Scroll depth on every screen
Scroll tracking makes sense for long-form content. For most screens, it's noise. Add it later if you have a specific question about engagement depth.
โ Form field focus/blur events
Don't track when users tap into or out of form fields. Track form submission success/failure instead.
โ Network requests or API calls
Analytics isn't for debugging network issues. Track user actions, not system events. Use proper monitoring tools for API performance.
โ Events with dynamic names
Don't create viewed_product_12345 or clicked_button_submit_form. Keep event names static. See our event naming guide.
๐ How to Prioritize When Starting
If you're starting from zero, here's the order to add events:
Implementation Priority
-
1
Session event
app_openedโ This is your baseline for everything -
2
Conversion event
Your primary business goal:
purchase_completed,subscription_started, etc. -
3
Funnel entry event
Where the conversion path starts:
checkout_started,upgrade_started -
4
Activation events
onboarding_started+onboarding_completed -
5
Core feature events
2-3 events for your app's main value proposition
-
6
Stop and analyze
Ship with 8-10 events. Run for 2 weeks. Add more only based on questions that arise.
๐ก Why Minimal Events Work Better
Respectlytics stores only 5 fields per event: event name, timestamp, platform, country, and session ID. This constraint forces focusโyou can't hide behind "we'll analyze it later" because there's no extra data to analyze.
The result: teams ship faster, analyze more, and make better decisions because they're not drowning in data they'll never use.
โ Frequently Asked Questions
What events should every mobile app track?
Every app should track: app_opened (session start), onboarding_completed (activation), core feature events (value delivery), and your primary conversion event. Start with 10-15 events covering your key user journey.
How many analytics events should a mobile app have?
Most apps need 15-30 well-designed events. Fewer than 10 misses important insights; more than 50 creates noise. Start minimal and add events only when you have a specific question to answer.
What's the difference between must-have and nice-to-have events?
Must-have events answer critical business questions: Did users complete onboarding? Did they convert? Did they use core features? Nice-to-have events provide extra context but aren't essential for basic analysis.
Should I track screen views in my mobile app?
Track screen views selectively, not automatically for every screen. Focus on screens that matter for your funnel: onboarding screens, checkout screens, key feature screens. Automatic tracking for all views creates noise.
What events should an e-commerce app track?
E-commerce apps should track: product_viewed, cart_item_added, checkout_started, checkout_completed, and search_performed. These cover the core purchase funnel.
Disclaimer:
These templates are starting points, not rigid requirements. Every app is differentโadapt these recommendations to your specific user journey and business model. The best event set is the smallest one that answers your critical questions.
Related Resources
- Event Naming Best Practices โ How to name your events for clarity and consistency
- Mobile App Metrics That Matter โ Essential KPIs for mobile apps
- How We Auto-Discover Conversion Paths โ Let algorithms find your funnels
- SDK Documentation โ Integration guides for Swift, Kotlin, Flutter, React Native