Activation is a promise kept, not a screen completed

Completing onboarding is easy to instrument, but it says little about whether the user received the value that brought them to the app. A useful activation signal sits closer to a promise kept.

Write the promise plainly

Describe what a new user expects to accomplish in their first meaningful session. A marketplace buyer may need to discover relevant supply and trust the transaction. A finance app user may need confidence and a successful first task. The right signal depends on that promise.

Test for future behaviour

Candidate activation events should be common enough to matter, achievable early and associated with later valuable return. Association is not causation, so compare users with similar initial intent and acquisition context where possible.

Use a small signal set

A chain of two or three behaviours can be more robust than one event. Keep it understandable enough that design, engineering and growth teams can explain why it matters. If nobody can act on the definition, it is not yet useful.