Deciding whether something should be a user or event property can be tricky. Things can get a little blurry. Thankfully, Anuj Sharma, Sr. Customer Success Architect at Amplitude, has some tips to help guide you to the right choice:
“Anything that adds more context to a user is a user property, anything that adds more context to the actual action, that's the event property.
But another way to look at this, anything that should maintain state with multiple events in a session that can also be considered as a user property.
So things that are maintaining state would be user property as compared to things that would change within the session that would be an event property.”
This is a snippet from Tracking Plan Tips: Event and Property Recommendations an Office Hours session with Ampliteer Anuj Sharma and Avo’s Thora Gudfinnsdottir who discuss data design, data governance, and tracking plans.
