When a viewer plays an embedded video, the player records the origin of the page that hosts the embed. Your dashboard shows a list of origins per video, ranked by play count. This is the analytics most creators actually want.
What an "origin" is
An origin is the protocol plus host of the page where the embed lives, for example https://example.com. The path is not recorded. So if your video is embedded on https://example.com/blog/post-one and https://example.com/blog/post-two, both count toward https://example.com.
Not recording the path keeps the analytics aggregate-only and avoids accidentally fingerprinting individual viewers based on which post they read.
Where to find it
Open the video from your library and click Analytics. The "Top embed origins" panel lists origins ranked by plays in the selected period.
What this is good for
- Knowing which sites are sending viewers
- Catching unauthorized re-uploads of your embed snippet
- Measuring the impact of a guest post or a partner page
- Choosing where to invest more content effort
What this is not
It is not a referrer log. It is the origin where the embed is, not the page that linked to that page. If a tweet drives traffic to a blog post that has your embed, you see the blog post's origin, not Twitter.
When the origin is unknown
For plays on the share page itself (/v/<slug>), the origin is recorded as videoplayer.ai. For embeds inside emails, intranets, or environments where the browser does not send a referrer, the origin shows as "(unknown)".