SaaS Activation Metrics: The 7 Events Every Product Should Track in Week One
A practical guide to SaaS activation metrics. The 7 events to instrument in week one, how to spot your activation moment, and how to fix a broken activation funnel.
Most early-stage SaaS founders confuse three things: signups, logins, and activation. Signups tell you marketing works. Logins tell you the email confirmation works. Only activation tells you the product works.
This post is a practical guide to SaaS activation metrics. The 7 events you should instrument in week one, how to spot your real activation moment, and how to fix an activation funnel that is quietly leaking users you paid to acquire.
What “activation” actually means
Activation is the first moment a new user experiences the core value your product promised them. Not “they logged in.” Not “they clicked around.” The moment something actually worked.
For Slack, the classic activation event is a team sending 2,000 messages. For Dropbox, one file uploaded and synced to a second device. For Figma, creating a file and inviting one collaborator.
The pattern: activation is almost never the obvious top-level action. It is the action that, once taken, makes the user 5 to 10x more likely to stick around.
The 7 events every SaaS should track in week one
You do not need 40 events. You need 7. These are the minimum to measure activation on almost any product.
1. landing_viewed
The top of your funnel. Fires on your marketing site, not the app.
Properties to attach: referrer, utm_source, utm_campaign. This is the only event where marketing attribution belongs.
2. signup_started
The user clicked “Sign up” and is on the form. Not yet submitted.
This event is underrated. The delta between signup_started and signup_submitted tells you if your signup form is too long, confusing, or asking for things people do not want to share.
3. signup_submitted
The form was submitted. Does not mean the account was created.
4. signup_completed
The account exists. Email is verified if you require that, first login has happened, the user is inside the app.
The gap between signup_submitted and signup_completed exposes email deliverability problems. If 15% of signups never complete, your confirmation email is going to spam.
5. activation_event (your core action)
This is the one you have to name yourself.
Ask: what is the smallest action a user can take inside the product that makes them meaningfully more likely to return? For a CRM, it might be contact_imported. For a bug tracker, issue_created. For a newsletter tool, first_email_sent.
If you cannot name it in one sentence, your product does not have a clear activation moment yet. Fix that before you worry about tracking.
6. aha_moment (optional but powerful)
Sometimes activation has two steps: do the thing, then see the thing work.
Example: a user creates a bug report, and then a teammate comments on it. That second event is the moment the product delivers on its promise. If you have one, track it.
7. session_started
Fires when a user opens the app after a gap (usually 30 minutes of inactivity). This is your retention input.
Without this event, you cannot compute D1, D7, or D30 retention. It costs nothing to add and unlocks every retention chart downstream.
How to find your real activation event
Most founders guess wrong on the first try. Here is a cleaner approach.
Step 1: pick a candidate. Based on intuition and what other products in your category do.
Step 2: bucket users by whether they did it. Users who did the candidate action in their first session vs. users who did not.
Step 3: compare week-1 retention. If the “did it” group retains 3x better than the “did not” group, you have a real activation signal. If the gap is under 2x, try another candidate.
Step 4: tighten it. If contact_imported gives you 3x retention, does imported_5_contacts give you 5x? Find the sharpest version of the signal.
This is how Facebook found “7 friends in 10 days,” how Dropbox found “one file on two devices,” and how most companies you admire found their activation metric. It is not guessed. It is measured.
Your activation funnel in one picture
With the 7 events above, your funnel is:
landing_viewed → signup_started → signup_submitted → signup_completed → activation_event
In lightweight product analytics tools like Eventraze, you build this in three clicks. No SQL. No schema mapping. You pick the events, set the order, and the funnel renders with drop-off percentages at every step.
Your job after that is to look at the biggest drop-off and ask one question: is this a product problem or an onboarding problem?
Reading the drop-offs
Each step drops users for a different reason. The fix is different each time.
| Drop-off | Likely cause | First thing to try |
|---|---|---|
landing_viewed → signup_started | Weak value proposition, unclear CTA | Rewrite the hero, one CTA only |
signup_started → signup_submitted | Form too long, wrong fields | Cut to email + password, add Google SSO |
signup_submitted → signup_completed | Email deliverability, confirmation UX | Switch ESP, move confirmation into the app |
signup_completed → activation_event | Onboarding does not lead to value | Replace the empty state with a seeded example |
Fix the biggest drop first. Move to the next. It is boring, measurable, and it works.
Common mistakes when tracking activation
- Naming events by UI.
button_clickedis useless.contact_importedis useful. Name by what happened, not by what the user tapped. - Instrumenting too early. If your product changes twice a week, your events will rot. Wait until the core flow is stable, then instrument.
- Only firing client-side. Your activation event often involves something the server confirms. Fire it server-side or you will miss 10–20% from ad blockers and network failures.
- Picking a vanity metric. “Logged in” is not activation. “Spent 2 minutes in the app” is not activation. If the metric does not correlate with retention, it is a vanity metric.
- Measuring once, tuning never. Activation moves. Your onboarding changes, your audience changes, your product changes. Re-measure your activation signal every quarter.
A week-one rollout plan
A concrete plan you can ship this week.
Day 1. Pick a tool. If you are shopping, check the Amplitude alternatives list.
Day 2. Install the SDK. Fire landing_viewed from your marketing site. Confirm it arrives.
Day 3. Instrument the other 6 events. Do the first pass yourself — do not delegate it. You need to know exactly what each event means.
Day 4. Build the activation funnel. Screenshot it. Save the screenshot. That is your baseline.
Day 5. Bucket users by whether they did your candidate activation action. Compare week-1 retention. Adjust the event if needed.
Week 2. Look at the funnel daily. Pick the biggest drop-off. Pick the smallest experiment that might move it.
That cycle — measure, pick the biggest leak, run one fix — is how activation rates go from 8% to 25% in a quarter.
The honest take
Most founders do not have an activation problem because they lack data. They have one because they have never defined what activation means for their product.
Define it. Instrument 7 events. Look at the funnel every Monday. That is 90% of what you need from product analytics in year one.
If you want the fastest path from zero to a working activation funnel, join the Eventraze waitlist — we invite early teams each week.
- Indie Hacker Analytics Setup: From Zero to First Insight in 30 MinutesA no-fluff indie hacker analytics setup. The exact stack, the 5 events to track on day one, and how to read your dashboard in 60 seconds without becoming a data engineer.
- Self-Hosted Analytics: When It's Worth It (and When It's a Trap)A practical guide to self-hosted analytics for founders. When self-hosting Plausible, PostHog, or Umami pays off, the hidden costs nobody mentions, and when a managed alternative is the right call.