Hi everyone!
I wanted to share with you a problem that I’m facing that is causing me headaches 
What are your thoughts on how should I instrument events in order for me to start understanding how users interact with the videos we offer?
Let me know your thoughts!
Thanks
Best answer by MikkoKarvonen
Hi everyone!
I wanted to share with you a problem that I’m facing that is causing me headaches
What are your thoughts on how should I instrument events in order for me to start understanding how users interact with the videos we offer?
Let me know your thoughts!
Thanks
Like in most cases, the answer depends on what you want to do with your data. For our purposes, simple LoadVideo, PlayVideo, and related error events have been enough, but if you need to understand the usage in more detail, you may want more.
One thing we have found useful is building summary events. So during whatever on-going action you want to track (like watching a video), you store any actions you want to track as independent variables, and when the activity end, you generate one event that sums up what happened.
So using playing a video as an example, the summary event could look something like this:
That’s a random set of properties, but hopefully it conveys the idea. This approach allows you to easily analyse things like how does EntryPoint affect PercentageWatched or FollowUpAction.
+10Hey
The Amplitude Data Taxonomy Playbook could be a good place to start if you haven’t already, where they have a sample taxonomy for the Media domain.
I would also love to hear from other Community members who work in the Media space about their experience of instrumenting video interaction events :)
+3Hi everyone!
I wanted to share with you a problem that I’m facing that is causing me headaches
What are your thoughts on how should I instrument events in order for me to start understanding how users interact with the videos we offer?
Let me know your thoughts!
Thanks
Like in most cases, the answer depends on what you want to do with your data. For our purposes, simple LoadVideo, PlayVideo, and related error events have been enough, but if you need to understand the usage in more detail, you may want more.
One thing we have found useful is building summary events. So during whatever on-going action you want to track (like watching a video), you store any actions you want to track as independent variables, and when the activity end, you generate one event that sums up what happened.
So using playing a video as an example, the summary event could look something like this:
That’s a random set of properties, but hopefully it conveys the idea. This approach allows you to easily analyse things like how does EntryPoint affect PercentageWatched or FollowUpAction.
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. You can also create a Guest account below!
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. Want to sign up as a guest? Create a Community account.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
