Hi everyone 👋
We're currently refining our event structure in Amplitude for screen views in our app, and we'd love to get the community's thoughts on best practices.
We’re considering two approaches:
Option A:
Create a specific event for each screen, such as:
Load_Onboarding_IntroPage, Load_Home_Feed, etc.
Option B:
Use a generic event, like load_screen, and pass screen-specific data in the event properties, e.g.:
"screen_name": "Onboarding_IntroPage", "screen_id": "onboarding_001"
We’re particularly interested in understanding:
-
Which approach tends to work better in Amplitude in terms of dynamic analysis, funnels, and user segmentation?
-
Are there any limitations in any of the features (e.g., in dashboards, cohorts, or behavioral reports) with either method?
-
What are the pros and cons of each approach, especially when scaling up to many screens or when trying to maintain clean taxonomy?
Any real-world examples or recommendations from your experience would be super helpful. Thanks in advance!
Daniel
