User Behavior → Trackable Events (in minutes)

Logo - Taking BS (600 x 600 px) (1080 x 1350 px) (New LinkedIn Banner) (25).png

Not every click == a behavior. Before you launch your next feature , run through this template to translate user behaviors to readable, informative data 🙂

What will I get out of this? A list with all the events and properties you need to visualize the user behavior - make sure to attach these to your PRDs!

Behavior	Relevant flows	Steps & Clicks	Conditions	How indicative is it? (1 high-5 low)	Events embedded in code	Properties to track
What user behavior do you want to track? Be specific.	Which user flow(s) or feature(s) reflect this behavior?	What are the key steps and interactions that indicate the behavior?	*Under what conditions should a behavior be tracked?

Must some steps be in sequence? Within a certain time frame?* | Does completing the relevant flow strongly indicate the behavior? use it as a prioritization tool later on | What event triggers should developers implement? | *What additional details should be collected? (e.g., timestamps, user properties, device, event properties)

Don’t forget to mention what type of data format you want to receive for each property.* | | Example (a learning app): | | | | | | | |

Users learning from their mistakes in the learning unit |

Review session | * Opened a lesson

Read content
Took a quiz
Completed a lesson
Logged out
Logged in
Looked at the review. | Looked at the review within 7 days of completing the lesson | 1 | * Start lesson
Submit quiz
Hit the complete button | Event properties: Timestamp (MM/DD/YY. hh:mm) Unit name (text) Unit difficulty level (one option out of the list) ….

User properties: Email (text) Location (GMT) Sign-up date (MM/DD/YY. hh:mm) ….. | | | 2. Take hints and read them | * Opened a lesson

Read content
Started the quiz
Answered questions
Read a question
Took a hint
Answered question *Completed a lesson | Looked at the hint more than 3 seconds | 1 | * Enter question
Hit the hint button
Close the hint pop-up window *Submit question | Event properties: Timestamp (MM/DD/YY, hh:mm:ss) Unit name Unit difficulty level Question number Answered correctly ….

User properties: Email Location Sign-up date ….. | | | 3. Not repeating the same mistake on a different unit | * Opened a lesson

Took a quiz
Answered question incorrectly
Completed a lesson
Reviewed lesson
Opened a different lesson
Took a quiz
Answered the same question
Completed a lesson | The same question is being asked in different sessions.

They didn’t look at the hint the second time | 3 - can be wrong because of carelessness | * Enter question

Hit the hint button
Entered session review screen | Event properties: Timestamp Unit name Unit difficulty level Question number ….

User properties: Email Location Sign-up date ….. |

–––––––––––––––

Want more tools like this?

👉 Subscribe to my newsletter for weekly behavioral design tips: yael.substack.com