What It Provides
Key Features for ASO Skills
| Feature | Description | Used By |
|---|---|---|
| Event tracking | Custom events with parameters | app-analytics |
| User properties | Segment users by attributes | retention-optimization |
| Funnels | Multi-step conversion analysis | app-analytics, monetization-strategy |
| Cohort analysis | Retention by install date | retention-optimization |
| Audiences | Dynamic user segments | ua-campaign |
| Attribution | Install source tracking | ua-campaign, app-analytics |
| A/B testing | Remote Config experiments | ab-test-store-listing |
| Crashlytics | Crash reporting | app-analytics |
Key Metrics
| Metric | Description |
|---|---|
| Active Users | DAU, WAU, MAU |
| Sessions | App opens with duration |
| Retention | Day 1, 2, 3, 7, 14, 21, 28, 30 |
| Engagement | Session duration, screens per session |
| Revenue | In-app purchases and ad revenue |
| Conversions | Custom conversion events |
| User Properties | Custom segmentation |
Setup
Recommended Events for ASO
Core Events to Track
User Properties
subscription_status:free,trial,premiumonboarding_completed:true,falsesessions_count: Number of sessionsfeature_tier:new,casual,regular,power_user
Integration with ASO Skills
app-analytics
Uses Firebase for:
- Setting up the event tracking plan
- Creating funnels (onboarding → activation → purchase)
- Monitoring DAU/MAU and stickiness ratio
- Identifying drop-off points
retention-optimization
Uses Firebase for:
- Cohort retention curves
- Comparing retained vs churned user behavior
- Identifying activation events that predict retention
- Measuring push notification impact
monetization-strategy
Uses Firebase for:
- Purchase funnel analysis
- Paywall view → trial → purchase conversion
- Revenue per user segment
- A/B testing paywall variants (via Remote Config)
ua-campaign
Uses Firebase for:
- Install attribution by source
- Post-install event tracking by campaign
- Audience creation for remarketing
- ROAS measurement
Usage Examples
Track Onboarding Funnel
Measure Retention by Cohort
- Go to Firebase Console → Analytics → Retention
- Select cohort type: “First Open” or “Custom Event”
- View Day 1, 7, 14, 28 retention curves
- Compare cohorts by acquisition source or user property
Create Audiences for Remarketing
Example: Churned Users
- Last engagement: > 7 days ago
- Previous sessions: > 3
- Subscription status: free
A/B Test Paywall
Using Firebase Remote Config:When to Use Firebase vs Other Tools
| Need | Firebase | App Store Connect | RevenueCat | Appeeky |
|---|---|---|---|---|
| In-app event tracking | ✓ | ✗ | ✗ | ✗ |
| Custom funnels | ✓ | ✗ | ✗ | ✗ |
| Retention cohorts | ✓ | Basic | By revenue | ✗ |
| Crash reporting | ✓ | Basic | ✗ | ✗ |
| A/B testing (in-app) | ✓ | ✗ | Paywalls | ✗ |
| Download attribution | ✓ | By source type | By source | ✗ |
| Keyword rankings | ✗ | ✗ | ✗ | ✓ |
| ASO data | ✗ | ✗ | ✗ | ✓ |
| Cost | Free | Free | Free tier | Credit-based |
Best Practices
Event Naming
- Use snake_case:
feature_used, notfeatureUsed - Be specific:
paywall_viewednotscreen_viewed - Include context:
purchase_completednotcompleted
Parameters
- Keep parameter names consistent across events
- Use strings for categories, numbers for metrics
- Max 100 unique event names, 25 parameters per event
User Properties
- Use for segmentation: subscription status, user tier, country
- Update when values change (sessions count, feature usage)
- Max 25 user properties per app
Funnels
- Keep funnels short (3-5 steps)
- Focus on critical flows: onboarding, purchase, core feature usage
- Set up at least: Install → Onboarding → Activation → Purchase