Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @KadenNo
You can try using custom media state tracking to capture those overlapping conditions. Since you are already firing state start/stop events for both "mini player" and "mute," the key is making sure those states are passed clearly in the media heartbeat config.
One way to approach it is to create a custom boolean or label (like isMiniMuted) and set it to true only when both the mini player is active & mute is on. You can pass this as a custom media state and then calculate watch time based on that condition later in reporting.
So basically:
When mini player starts --> state = "mini"
When mute starts --> state = "muted"
When both are active --> state = "mini-muted" (or set a flag)
Then in Analysis Workspace, use segments that filter for that combined state to isolate watch time in that exact condition.
Hope that helps!
Hi @KadenNo
You can try using custom media state tracking to capture those overlapping conditions. Since you are already firing state start/stop events for both "mini player" and "mute," the key is making sure those states are passed clearly in the media heartbeat config.
One way to approach it is to create a custom boolean or label (like isMiniMuted) and set it to true only when both the mini player is active & mute is on. You can pass this as a custom media state and then calculate watch time based on that condition later in reporting.
So basically:
When mini player starts --> state = "mini"
When mute starts --> state = "muted"
When both are active --> state = "mini-muted" (or set a flag)
Then in Analysis Workspace, use segments that filter for that combined state to isolate watch time in that exact condition.
Hope that helps!
I was going to suggest something similar.. using a custom value to distinguish the main player from the mini-player.
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies