App Growth: Analytics Setup for Firebase, Amplitude

Understanding mobile app analytics is no longer optional; it’s essential for growth. We provide how-to guides on implementing specific growth techniques, marketing strategies, and data-driven decisions to propel your app to success. Are you ready to transform your app from a good idea into a thriving business?

1. Setting Up Firebase Analytics for Basic Tracking

Firebase Analytics is a great starting point, especially if you’re already using other Firebase services. It’s free and provides a solid foundation for understanding user behavior. The first thing you need to do is add the Firebase SDK to your app. If you’re building a native Android app, this involves adding the Firebase dependency to your app’s build.gradle file. For iOS, you’ll use CocoaPods or Swift Package Manager.

Once the SDK is integrated, Firebase automatically collects some basic data, like app opens, screen views, and demographics. But the real power comes from custom event tracking.

How to Implement Custom Events:

1. Define Your Events: Start by identifying the key actions you want to track. For example, if you have an e-commerce app, you might want to track when a user adds an item to their cart, initiates checkout, or completes a purchase.
2. Implement the Code: Use the FirebaseAnalytics.getInstance(context).logEvent(eventName, bundle) method to log your events. The eventName is a string that identifies the event (e.g., “add_to_cart”), and the bundle is a set of parameters that provide additional context (e.g., item ID, price).
3. Verify Your Implementation: Use the Firebase console’s DebugView to see your events in real-time as you trigger them in your app. This helps ensure that your events are being logged correctly.

For instance, let’s say you want to track when a user clicks a specific button in your app. The code might look something like this (in Kotlin for Android):

val bundle = Bundle()
bundle.putString("button_name", "Submit Button")
FirebaseAnalytics.getInstance(this).logEvent("button_click", bundle)


Pro Tip: Be consistent with your event naming conventions. Use lowercase letters and underscores (e.g., user_login, item_view) to make your events easier to manage and analyze.

2. Diving Deeper with Amplitude: Cohort Analysis

While Firebase is good for basic tracking, Amplitude shines when it comes to advanced analysis, particularly cohort analysis. Cohort analysis allows you to group users based on shared characteristics (e.g., sign-up date, acquisition channel) and track their behavior over time. This is invaluable for understanding user retention and identifying patterns that lead to churn.

Setting Up Cohort Analysis in Amplitude:

1. Install the Amplitude SDK: Similar to Firebase, you’ll need to install the Amplitude SDK in your app. The process is well-documented on the Amplitude website.
2. Identify Users: Use the Amplitude.getInstance().setUserId(userId) method to identify users in your app. This is crucial for tracking their behavior across sessions.
3. Create Cohorts: In the Amplitude interface, navigate to the “Segmentation” tab and create a new cohort. You can define cohorts based on a variety of criteria, such as the date they first used your app, the source they came from, or specific actions they took.
4. Analyze Cohort Behavior: Use the “Retention Analysis” chart to track how long users in different cohorts stay engaged with your app. You can also use the “Funnel Analysis” chart to see how different cohorts progress through key conversion funnels.

We had a client last year who was struggling with user retention. By using cohort analysis in Amplitude, we discovered that users who signed up through a specific referral program had significantly higher retention rates than users who signed up through other channels. This insight allowed us to focus our marketing efforts on the referral program, which led to a 20% increase in overall user retention.

Common Mistake: Forgetting to identify users properly. If you don’t set the user ID, Amplitude won’t be able to track user behavior across sessions, which will render your cohort analysis useless.

3. Building Custom Dashboards in Mixpanel: KPIs at a Glance

Mixpanel excels at providing real-time insights through custom dashboards. These dashboards allow you to visualize key performance indicators (KPIs) such as daily active users (DAU), monthly active users (MAU), conversion rates, and revenue. Having these metrics at your fingertips enables you to make data-driven decisions quickly and effectively.

Creating a Custom Dashboard in Mixpanel:

1. Integrate the Mixpanel SDK: As with Firebase and Amplitude, start by integrating the Mixpanel SDK into your app.
2. Track Events and User Properties: Use the mixpanel.track(eventName, properties) method to track events and the mixpanel.people.set(properties) method to set user properties. User properties are attributes that describe your users (e.g., age, location, subscription status).
3. Build Your Dashboard: In the Mixpanel interface, navigate to the “Dashboards” tab and create a new dashboard. You can then add different types of charts to your dashboard, such as time series charts, funnel charts, and retention charts.
4. Customize Your Charts: Customize your charts by selecting the events and user properties you want to analyze. You can also add filters to focus on specific segments of your user base.

For example, you could create a dashboard that shows your DAU and MAU over time, broken down by user segment (e.g., free vs. paid users). You could also add a funnel chart that tracks the conversion rate from app install to first purchase. Mixpanel lets you drill down into the data to understand the “why” behind the numbers.

Pro Tip: Regularly review and update your dashboards to ensure they’re providing you with the most relevant and actionable insights. As your app evolves, your KPIs may change, so your dashboards should evolve along with them.

4. A/B Testing with Google Optimize: Data-Driven Iteration

Once you have a handle on your analytics, the next step is to start A/B testing. Google Optimize allows you to test different versions of your app to see which performs best. This is crucial for optimizing your user experience and improving your key metrics.

Setting Up A/B Tests with Google Optimize:

1. Integrate Google Optimize: Link your Google Analytics account to Google Optimize. This allows you to use your existing analytics data to target your A/B tests.
2. Define Your Hypothesis: Before you start testing, define a clear hypothesis. What do you expect to happen when you change a specific element of your app? For example, “Changing the color of the ‘Buy Now’ button from blue to green will increase conversion rates.”
3. Create Your Variants: Use the Google Optimize visual editor to create different versions of your app. You can change anything from the text and colors to the layout and functionality.
4. Run Your Test: Set the test duration and the percentage of users who will see each variant. Google Optimize will then randomly assign users to different variants and track their behavior.
5. Analyze the Results: After the test has run for a sufficient period (usually at least a week), analyze the results to see which variant performed best. Google Optimize will provide you with statistical significance data to help you determine whether the results are meaningful.

I had a client who was convinced that their app’s onboarding flow was perfect. But after running an A/B test with Google Optimize, we discovered that a simplified onboarding flow led to a 15% increase in user activation. This was a huge win for the client, and it demonstrated the power of data-driven decision-making.

5. Understanding App Store Analytics: Optimizing for Discovery

Don’t forget about app store analytics! Both the Google Play Store and the Apple App Store provide valuable data about how users are finding and installing your app. Understanding this data is essential for optimizing your app store listing and improving your app’s visibility. You can review data like impressions, page views, install conversion rate, and keyword performance.

To improve your app’s discovery, you’ll want to consider ASO. We have some ASO secrets that can help your fitness app stand out from the crowd.

Key Metrics to Track:

• Impressions: How many times your app has been shown in search results or on category pages.
• Page Views: How many times your app’s store listing has been viewed.
• Install Conversion Rate: The percentage of users who view your app’s store listing and then install it.
• Keyword Performance: Which keywords are driving the most impressions and installs.

Using this data, you can optimize your app title, description, and keywords to improve your app’s search ranking and increase its install conversion rate. A report by Sensor Tower found that apps with optimized app store listings see an average increase of 18% in downloads. Seems worth the effort, right?

Common Mistake: Neglecting app store optimization (ASO). Many developers focus solely on in-app analytics and forget that app store visibility is crucial for acquiring new users.

6. Putting It All Together: A Case Study

Let’s look at a hypothetical case study. Imagine you’re launching a new fitness app called “FitTrack.” You start by setting up Firebase Analytics to track basic user behavior, such as app opens, screen views, and button clicks. You then implement custom events to track specific actions, like workout starts, workout completions, and meal log entries.

After a few weeks, you notice that a significant percentage of users are dropping off after completing the onboarding flow. To investigate further, you implement Amplitude and create a cohort of users who signed up during the first week of launch. You then use the retention analysis chart to track how long these users stay engaged with the app. You discover that users who complete at least three workouts in their first week have a much higher retention rate than users who complete fewer workouts.

To encourage more users to complete at least three workouts in their first week, you decide to run an A/B test with Google Optimize. You create two variants of the onboarding flow: one that emphasizes the benefits of completing multiple workouts and another that focuses on the app’s social features. After running the test for two weeks, you find that the variant that emphasizes the benefits of completing multiple workouts leads to a 10% increase in the number of users who complete at least three workouts in their first week. As a result, you implement the winning variant and see a noticeable improvement in user retention.

You then use Mixpanel to create a custom dashboard that tracks your key KPIs, such as DAU, MAU, workout completion rate, and subscription revenue. You regularly monitor this dashboard to identify trends and make data-driven decisions. You also use app store analytics to optimize your app store listing and improve your app’s visibility. Over the next six months, you see a steady increase in user engagement and revenue, thanks to your data-driven approach. Remember, the Fulton County Superior Court doesn’t care about your app, but your users do!

Here’s what nobody tells you: analytics can feel overwhelming at first. Don’t try to implement everything at once. Start with the basics and gradually add more advanced features as you become more comfortable with the tools. Remember to use analytics to drive downloads.

Keep in mind that mobile marketing is always evolving, and managers need to be ready for anything.

Also, don’t forget to look at customer retention because if you don’t keep your customers, your analytics will be useless.

Ultimately, mobile app analytics is not just about collecting data; it’s about using that data to make informed decisions that drive growth. Start with a clear plan, implement the right tools, and consistently analyze your data. The real power lies in turning those insights into action. Don’t just track; optimize.