Category: Video Analytics

  • Video Analytics: Build a Measurement Plan Before You Report

    Video Analytics: Build a Measurement Plan Before You Report

    Your campaign is ready, but nobody has checked whether the embedded video records the actions the report will need. Discovering that gap after launch leaves you with a difficult question: did viewers do nothing, or did the measurement setup miss what they did?

    A video analytics measurement plan addresses that uncertainty before reporting begins. It records what should be collected, where the evidence will appear, how you will test it, and who owns the result. The task here is collection readiness, not interpreting a retention chart or choosing a universal performance benchmark.

    What belongs in a video analytics measurement plan?

    The plan is a working agreement between the marketer, the person responsible for the website or player, and the person preparing reports. It should be specific enough that someone other than its author can check the setup.

    For every required measure, record the video and placement, the action you expect to observe, the collecting system, the documented counting rule, the verification method and the owner. If one of those is unknown, record the gap in your planning document instead of treating a dashboard label as an answer.

    Keep the first version small. A launch report that needs evidence of playback and a particular next step does not automatically need every available interaction. Add a measure when you can name the reporting question it serves.

    Build a tracking inventory by placement and version

    Start with the actual pages where the video will appear. A title alone may be an ambiguous identifier if the same asset is embedded on several pages or replaced with a new edit.

    Fields for a practical video-measurement inventory
    Field What to record
    Placement The page and location of the intended embed, using your team’s internal naming convention.
    Video version A stable reference to the specific edit being measured.
    Required observation The viewer action or viewing measure needed for the report.
    Collection source The system expected to record it and the report or diagnostic view used to verify it.
    Counting rule The documented trigger, unit and treatment of repeated actions, or an explicit unresolved question.
    Acceptance check The controlled action, expected evidence and person responsible for checking it.

    As a hypothetical planning example, a product demonstration appears on a comparison page and a campaign landing page. Keep separate inventory rows if the team needs to report those placements separately. Then establish whether the selected collection system can distinguish them. Naming two rows in a spreadsheet does not create that capability in the software.

    Verify collection coverage before assuming it

    Installing a website analytics tool does not, by itself, establish that your particular player and every in-video action are measured. Check the documented conditions for the collection method you intend to use.

    For example, Google Analytics’ enhanced-measurement documentation scopes its video-engagement events to YouTube embeds with JavaScript API support enabled. That is a specific condition, not a promise of automatic coverage for every embedded player. This example does not establish a Vidzy integration with Google Analytics.

    Ask the implementation owner to identify which collection mechanism is active on each placement. Record any prerequisites and known exclusions in the inventory. Where a required observation has no verified source, either resolve collection before launch or narrow the promised report.

    Run a controlled collection check

    Use an authorized test environment or an agreed test window. Coordinate with the report owner so test activity is documented and handled appropriately; do not assume it can be automatically filtered out.

    1. Record the test context. Note the page, video version, device or browser, time and applicable consent state. Follow the site’s normal consent process rather than bypassing it to make data appear.
    2. Perform one defined action. Use the inventory’s acceptance check. Avoid combining several actions when you need to identify which one produced the evidence.
    3. Inspect the designated source. Confirm that the expected record or measure appears using the system’s supported diagnostic method and documented processing expectations.
    4. Compare the identity and meaning. Check that the evidence belongs to the intended placement and video where those distinctions are supported. A changed total somewhere else is not enough.
    5. Record the outcome. Mark the check passed, failed or inconclusive, with the evidence location and the next owner. Repeat for the other required observations.

    If nothing appears, keep “no activity recorded” separate from “the visitor took no action.” Check the collection prerequisites, reporting delay and test context before drawing a behavioral conclusion. A single successful test is also limited evidence: it validates the tested path, not every possible browser or viewing situation.

    Investigate duplicate collection without inventing a correction

    If one controlled action appears to produce more records than expected, first confirm the documented counting rule. Several records may represent different events rather than duplicates.

    Ask the implementation owner to inspect the collection paths and determine whether the same observation is being sent more than once. Record the finding and repeat the controlled check after any authorized correction. Do not simply divide the reported count to make it match an expectation.

    Two systems may also describe a similar action differently. Keep their names and definitions attached to the values; do not add totals together unless you have established that doing so is meaningful and does not count the same activity twice.

    Agree on the reporting handoff

    Choose the authoritative source for each reported measure before building the summary. The handoff should include the inventory, collection-check results, reporting period, known gaps and any video or page changes that affect comparability.

    Assign one person to resolve collection issues and one to maintain the report. Set a review point based on the campaign’s actual decisions rather than a fixed reporting habit. When an embed or video version changes, identify which acceptance checks need to be repeated.

    Where Vidzy contributes

    Vidzy provides an embeddable player with video analytics, watch-time tracking, CTA click tracking and opt-in tracking. These approved capabilities can inform which observations you investigate for an embedded-video report.

    They do not establish specific counting rules, event payloads, integrations or automatic joins to another system. Verify the definitions and collection behavior your plan requires; this guide does not prescribe Vidzy instrumentation or promise end-to-end attribution.

    Use this launch-readiness handoff

    • Each report question has a named measure and collection source.
    • The intended placements and video versions are recorded.
    • Required collection conditions have been checked.
    • Controlled checks have evidence, outcomes and owners.
    • Unresolved gaps and test activity are disclosed to the report owner.
    • A change to the video or embed triggers the appropriate recheck.

    Complete the inventory for one important video before extending it across the site. Hand it to the person who will prepare the report and ask them to trace each required measure back to verified collection evidence.

  • Video Heatmap: How to Read the Legend and Compare Reports

    Video Heatmap: How to Read the Legend and Compare Reports

    A video heatmap can look self-explanatory: some sections have more color than others. But a colored section does not explain itself. Before using the report in a presentation, you need to know what each mark represents, whose playback it includes and how the legend works.

    This guide helps you decode that report. The goal is to describe it accurately and recognize which other reports can be compared with it, before drawing conclusions about the video.

    What does a video heatmap represent?

    In playback analytics, a video heatmap represents activity along a video’s timeline. Read its documented definition to establish the exact activity being represented. Do not assume that the term means a map of where someone’s eyes looked or where their pointer moved across the image.

    Start with two questions: what does one row or mark stand for, and what changes its appearance? The answer should come from the report’s help text or documentation, not from the colors alone.

    Identify the reporting unit first

    A single-session record and an audience-wide summary answer different questions. The first can describe a particular playback journey; the second combines activity. Treating one session as the audience’s typical experience would require evidence beyond that one record.

    For a concrete, platform-specific example, Wistia describes a heatmap as a representation of a single viewing or listening session. Its glossary describes the engagement graph, in contrast, as an aggregate view. Those are Wistia’s report definitions, not definitions of Vidzy’s heatmaps.

    When opening an unfamiliar report, identify whether it describes a playback session, a viewer or a combined population. Do not assume that a session equals a unique person, or that an anonymous record identifies a contact. If the unit is unclear, leave it unresolved in your notes instead of choosing the interpretation that fits your story.

    Read the legend before naming a pattern

    Colors need an explicit key. Avoid labeling a warm-colored section “good engagement” or a pale section “lost interest” unless those words accurately describe the documented measure. A legend describes an encoding, not a judgment about content quality.

    Wistia’s official heatmap guide provides a useful example: white denotes unplayed portions, green denotes one play and yellow denotes two plays, with warmer colors for further repeats. It also explains that the percentage at the end counts repeatedly played portions only once. A colored timeline and its summary can therefore describe different aspects of the same session. Do not apply this legend to another product without checking its documentation.

    Save the legend with any report excerpt you share. Without it, a colleague may mistake repeat playback for a larger audience or interpret a change of color as a conversion signal.

    Separate coverage from repeated playback

    Consider a hypothetical video split into ten equal sections. A session plays four different sections, then plays one of those sections again. Under a measure that counts distinct sections reached, coverage is four out of ten. Under a measure that counts all complete section plays, the total is five.

    Neither number contradicts the other. They count different things. This is an illustrative accounting example, not a Vidzy calculation, a benchmark or a real customer result.

    Before explaining a summary next to a heatmap, establish whether it counts distinct portions, accumulated playback time or something else. Also check how partial plays are handled. A summary label such as “engagement” is not enough to reconstruct its formula.

    Check compatibility before comparing reports

    Two reports placed side by side can appear comparable simply because both use a timeline. Use the following checks before describing one as higher, lower or improved.

    Checks for comparing two video reports without mixing definitions
    Check What must be clear
    Reporting unit Whether both reports describe sessions, viewers or aggregates; a single session is not interchangeable with an audience summary.
    Measure and scale Whether the marks encode counts, time or percentages, and whether color thresholds stay fixed between reports.
    Timeline Whether positions refer to elapsed time or relative progress, and whether the video versions contain the same material at that position.
    Grouping Whether a mark represents a moment or a wider interval; an interval does not identify an exact second.
    Included activity Whether the reports cover the same relevant audience and period, and how repeats enter the calculation.

    For example, if a revised introduction moves a demonstration later, the same timestamp no longer points to the same content. Align the relevant sections before comparing them. Similarly, if each chart chooses its own color thresholds, the darkest tile in one report need not represent the same quantity as the darkest tile in another.

    If these details are unavailable, describe each report separately. A qualified description is more useful than a precise-looking comparison built on incompatible measures.

    Attach a short reading card to the report

    Before sharing a heatmap, add a plain-language note containing:

    • Report: the platform and report name.
    • Unit: what one record represents.
    • Legend: what color, height or another visual mark encodes.
    • Timeline: the video version and how positions are grouped.
    • Summary: what any adjacent total or percentage counts.
    • Comparison limit: which differences prevent a direct comparison.

    Use explicit wording such as “This report represents one playback session; its colors show the documented repeat categories.” Use that sentence only when both statements are verified. Otherwise, note the missing definition and request it from the report owner.

    Using heatmaps with Vidzy

    Vidzy is an embeddable video player with video analytics and heatmaps. Those capabilities do not establish a particular legend, aggregation method or formula. This article does not assign the Wistia example or the hypothetical section-counting method to Vidzy.

    Start with one report you need to explain and complete its reading card. Resolve the missing definitions before comparing it with another report or forwarding a cropped chart to your team.

  • Video Engagement Metrics: How to Read Watch Time and Drop-Off

    Video Engagement Metrics: How to Read Watch Time and Drop-Off