We work with three layers of event data to focus on suitable events. We are going from a high-level customer focus down to a granular interaction focus.

Define your customer and product entities first. They define the scope you want to look at your data. Then explain the activities of these entities and, finally, their properties.

Learn how to effectively map your customer journey and identify & design the core entities of your business product. These entities will help you to focus your activities and cluster the data to make it easy to access and understand.

Getting data for product usage and adoption is not easy. You need to adopt the right abstraction level to not gather granular data. For product adoption, you need to combine different product activities into measuring value milestones or successful sessions.

While activities will help you understand how customers are progressing, the properties give you depth to analyze.

With properties, you can slice and dice the data to identify high-performance segments and the segments you can help to progress. And gives you powerful segments for marketing activities.

How much value is in knowing how users are using small parts of a feature (filters, sorting, icons)? For the big picture not much. For teams working on improving these features a lot. But these events need a good structure so they don't ruin your tracking plan and setup.