Video engagement events
Video engagement events record interaction with embedded video: video_start, video_progress (at 10/25/50/75% milestones), and video_complete. GA4's enhanced measurement captures these for supported embeds automatically. They turn an opaque 'a video exists' into a watch-depth signal — and because progress is milestone-based, you can see where viewers drop off rather than only that they pressed play.
What this means
GA4 enhanced measurement collects video engagement for embedded YouTube players that have the JS API enabled: video_start when playback begins, video_progress at 10%, 25%, 50%, and 75% milestones, and video_complete at the end. Each event carries video metadata such as title, provider, and duration.
Why progress matters
A single play count tells you almost nothing — pressing play and watching three seconds looks identical to watching to the end. Progress milestones reveal the drop-off curve: a steep fall after video_start means the opening is not holding viewers; a healthy climb to video_complete means the content lands. That curve, not the play count, is the useful signal.
- video_start, video_progress (10/25/50/75%), video_complete
- Captured for supported embedded players
- Progress shows drop-off; a play count does not
How it appears in analytics and logs
video_start without later video_progress means viewers leave early. Many video_start but few video_complete points to length or relevance problems with the content.
Diagnostic use case
Measure how much of a video visitors actually watch, using start, progress, and complete events to find drop-off rather than counting plays alone.
What WebmasterID can help detect
WebmasterID can record video milestones as first-party engagement events without cookies, so watch-depth analysis stays anonymous and separate from bot traffic.
Common mistakes
- Reading play counts without watch depth.
- Expecting auto-capture for unsupported or self-hosted players.
- Ignoring that autoplay inflates video_start.
Privacy and accuracy notes
Video events describe watch progress, not the viewer. They need no identifier and carry no personal data, making watch-depth a privacy-safe engagement signal.
Related pages
- Enhanced measurement (auto events)
Enhanced measurement is a GA4 setting that automatically collects a set of interaction events — scrolls, outbound clicks, site search, video engagement, file downloads, and form interactions — without extra code. It is convenient but not magic: it only covers standard patterns, can over- or under-count, and each option can be toggled. This page explains what it does and its limits.
- Engagement time and the user_engagement event
Engagement time measures how long a page was actually in the foreground and active, recorded through GA4's user_engagement event. It replaces the old, unreliable time-on-page that could not measure the last page of a visit. By only counting time when the tab is visible and focused, engagement time is a more honest attention signal — though still not a guarantee that anyone read anything.
- The scroll event and depth tracking
A scroll event records that a visitor scrolled to a depth on the page. In GA4 enhanced measurement, a single scroll event fires once per page when the visitor reaches 90% of the page height. It is a coarse engagement signal — useful for spotting content people do not reach, but limited because the default is one threshold, not a continuous read-depth curve.
- Event Explorer
Inspect video milestone events.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.