HummingDeck analytics show how a shared document or Room was accessed and used. They are most useful when several signals point in the same direction.
Overview
Engagement across documents and Rooms
Start with the viewer and link
Before reading time or completion, check which link produced the session. A Personal, Room, Proposal, or Restricted link carries more sharing context than a broad open link.
Identity strength also differs:
- An assigned contact is the intended audience, but an open URL can be forwarded.
- An email captured through Ask is self-reported.
- Verify proves control of the entered inbox.
- Restricted proves control of an inbox that was allowed in advance.
None of these proves legal identity, employment, or decision authority.
Read the core signals
Views and return visits
A view means the link was requested and a viewing session began. Return visits can show renewed attention, internal circulation, or preparation for a meeting. Look at the surrounding activity before deciding which explanation fits.
Completion
Completion estimates how far the viewer progressed through the document. A high completion rate is more meaningful on a linear deck than on a reference document where the reader only needs one section.
Time spent
Time helps compare sessions and pages, but it is not a stopwatch for active reading. A viewer can leave a tab open, switch applications, or skim quickly. Use time as a directional signal.
Page engagement
Page-level analytics show where attention concentrated and where viewers left. They can help you find a pricing page that draws repeat visits, an implementation section that is being studied, or an early page that loses readers.
Clicks and engagement flow
Supported links inside a document can show which calls to action were used. Engagement flow helps show how viewers moved through the material.
Room analytics
Room analytics connect entry, stakeholder activity, and the documents opened inside the Room. Use separate recipient links when you need cleaner attribution for different audiences.
A Room visit without a document open can still matter. The viewer may be checking next steps, discussions, or the available material. Combine the Room activity with document sessions.
Bot filtering
Email security scanners, social previews, and other automated systems can request a link before a person sees it. Without filtering, those requests can look like instant opens and distort views, time, completion, and follow-up decisions.
HummingDeck checks request and network signals for likely automation. Known bot traffic is excluded from standard Analytics, Pipeline, Captured Leads, account metrics, and view notifications. If a likely automated session later produces real in-view interaction, it can be treated as human activity.
Bot filtering reduces noise, but it cannot identify every automated request or prove that every remaining session came from an interested person. Avoid acting on a single instant view with no meaningful reading or interaction.
When you need to investigate a suspicious open, the Activity page can reveal stored bot sessions. See Activity, view notifications, and follow-up for the steps.
Plan and retention differences
Analytics history and advanced views depend on the workspace plan. Geographic insights, team analytics, stakeholder views, and retention windows can differ. The product’s plan controls are the current source of truth.