Measuring What Matters: Simple Analytics for Early‑Stage Apps

Step 1: Why Simple Analytics Matter For Early Apps

Step 2: The Basic Funnel – From Seeing Your App To Using It

Step 3: Define Activation For Your App

Your activation metric is the first moment a new user actually feels value.

It is not just "opened the app" or "created an account". Those are often just setup steps.

Think of common examples:

• A note app: created and saved 1 note
• A fitness app: completed 1 workout
• A language app: finished 1 lesson
• A budgeting app: added 1 bank account or 1 expense

Your turn.

1. Write down in one sentence: What is the first clear sign that a new user has felt value in your app?

• Start the sentence with: `A user is activated when they...`

1. Check that it is:

• Concrete (you can count it)
• User-value focused (not just an internal step like sign-up)

Example answers:

• "A user is activated when they send their first message to another user."
• "A user is activated when they track their first workout."

Pause and actually write your sentence now (on paper, notes app, or your laptop). You will use this later when we talk about analytics tools.

Step 4: Reading Store Data – Impressions, Visits, Installs

Step 5: Quick Check – Store Funnel

Test your understanding of the basic store funnel metrics.

Step 6: Tracking Activation And Retention With Free Tools

Step 7: Example – Tracking an Activation Event (Conceptual)

You do not need to be a programmer to understand this, but seeing a code example can make the idea concrete.

Below is a conceptual example using JavaScript-like pseudocode for a cross-platform app with Firebase Analytics. The real code will differ per platform (Android, iOS, web), but the pattern is the same:

1. When the user does the activation action (here: completes first workout)
2. Check if it is their first time
3. Send an analytics event

```js

// Pseudocode for tracking activation in a workout app

function onWorkoutCompleted(userId, workoutId) {

// 1. Mark that the user has completed a workout

saveWorkoutToDatabase(userId, workoutId);

// 2. Check if this is the user's first completed workout

const completedCount = getCompletedWorkoutCount(userId);

if (completedCount === 1) {

// 3. Log the activation event to analytics

analytics.logEvent("firstworkoutcompleted", {

user_id: userId,

workout_id: workoutId

});

}

}

```

Key ideas:

• You choose a clear event name (like `"firstworkoutcompleted"`).
• You send it only once per user for their first time.
• In your analytics tool, you look at how many new users trigger this event.

You can show this pattern to a developer on your team and ask:

• "Can we track our activation moment with one clean event like this?"

Step 8: Making Sense Of Small, Noisy Numbers

Early apps often have tiny numbers. That is normal.

Example week:

• Impressions: 800
• Product page views: 60
• Installs: 15
• Activated users: 6
• Users who came back next day: 4

Questions to think about:

1. Which step looks strongest?

• Hint: calculate rough conversion rates.

1. Which step would you try to improve first?

• Store visit rate (clicks from impressions)?
• Install rate (installs from page views)?
• Activation rate (activated users from installs)?

There is no single "correct" answer, but a simple rule is:

• If conversion is below ~10% at a step, it may be a good candidate to improve.
• If numbers jump up and down each week, look at 3–4 week trends, not a single day.

Activity:

• Take a calculator and compute:
• Store visit rate = 60 / 800
• Install rate = 15 / 60
• Activation rate = 6 / 15
• Day 1 retention (for that cohort) = 4 / 15
• Write down which step you would focus on next week and one guess about why that step is weak.

Step 9: Closing The Loop – Turning Metrics Into Actions

Step 10: Key Term Review

Flip through these flashcards to review the main concepts from this module.

Step 11: Final Check – Picking What To Fix

Use this quiz to confirm you can connect metrics to actions.