Measurement

Video analytics that answer editorial questions

See which videos hold attention, where people stop watching and whether playback is working for your audience. Use aggregate reporting for the whole library, with optional per-user reporting on Plus and larger plans when your embed supplies your own user identifier.

Start free trialSee the API reference
Where attention dropsIllustration — not your data
drop-off

Viewer detail

Plays
per video
Watch time
per video
Completion
per video
Viewer identity
Plus and larger plans

The problem

Turn every play into a useful content decision

Most video reporting stops at views, which is the least useful number available. A video with a thousand views that everyone abandons after fifteen seconds and a video with two hundred views that people finish are wildly different outcomes, and a view count reports them identically.

The consequence is that decisions get made on volume rather than on attention. You keep producing the format that gets clicked and not the format that gets watched, and nothing in the dashboard tells you which is which.

What you actually need is shape: how far people get, whether that changes by video, and whether the drop-off is an editorial problem or a delivery problem. Those are different fixes, and separating them is the point of measuring quality alongside engagement.

The metrics

Measure attention, audience and playback quality

Start with library-wide patterns, then connect viewing to users in your own application when the workflow requires it.

Custom user analyticsPlus and larger plans
Pass your own user ID or email address with the video embed to connect playback activity to the people in your application. DynTube reports the identifier you supply; your system remains the source of truth for who that identifier belongs to.
Plays and watch secondsPer video
Bounded aggregates of how often a video was played and how much of it was watched in total. Watch seconds against plays is the ratio that tells you whether a video is holding people.
Completion ratePer video
How much of the video an average session reached. Read alongside watch seconds, this is what separates a video people finish from a video people open.
Audience and engagement viewsAccount level
Aggregate account-level views of audience and engagement, so you can see the pattern across a library rather than only per asset. Useful for deciding what to make next.
Quality of experience and bandwidthAccount level
Aggregate playback-quality and delivery views. This is the pair that answers whether a drop-off is people losing interest or playback struggling — and they need different responses.

Optional identified viewing

Connect viewing to users in your own application

On Plus and larger plans, enable custom user analytics and include your own user ID or email address with the player embed. Playback events then carry that customer-supplied identifier, giving your team per-user viewing reports alongside the aggregate dashboard.

This model keeps identity under your control: DynTube stores and reports the value your application supplies instead of guessing who an anonymous viewer is. Use an internal user ID when you want the analytics record separated from personal contact details, or an email address when that is the identifier your workflow already uses.

Use the per-user dashboard to review videos watched, views, watch time, completion and recent activity for the supplied identifier. For formal training completion or access decisions, send the result into the learning or identity system that owns those business rules.

The breakdowns

How the aggregates are sliced

Use each aggregate dimension to answer a different editorial, delivery or distribution question.

  • Top videos by engagement

    Which titles hold attention rather than merely collect plays. The most directly editorial view available, and usually the first place to look.

  • Geography

    Aggregate country and city distribution. Useful for deciding where delivery coverage matters and which regions justify localisation or subtitles.

  • Platforms, browsers and devices

    Aggregate technical profile of your audience. This is the list to test protection and player changes against, rather than guessing at a device mix.

  • Embed domains

    Aggregate view of where playback is happening. Worth checking against your domain restrictions — an origin you do not recognise is a signal.

Using it

Turning the numbers into a decision

Move from a library-level signal to the affected title, then separate editorial and delivery causes before changing anything.

  1. 01

    Start with completion, not plays

    Rank your library by completion and watch seconds. The gap between that ranking and the play-count ranking is usually the most surprising thing in the account.

  2. 02

    Separate editorial from delivery

    Where drop-off is high, check the quality and bandwidth views for the same period. A delivery problem looks like drop-off concentrated on particular devices or regions; an editorial problem does not.

  3. 03

    Check the device and browser mix

    Before changing protection, the player, or a quality ladder, look at what your audience actually uses. This is the list to test against.

  4. 04

    Pull it into your own reporting

    The analytics endpoints in the API let you fetch the aggregates on a schedule and keep them beside your other metrics, rather than logging into a second dashboard.

Look at your own completion curve

Upload a few real videos, put them in front of a real audience, and compare the completion ranking with the play ranking. That comparison is usually the whole insight.

Start free trialTalk to us