Choose observation points
Plan a few consistent observation times across the relevant session window. Save the metric label and timestamp with each screenshot. A single high or low snapshot cannot describe the whole period or identify why the number changed.
Record session context
Note interruptions, major programme changes and other promotion around the observations. Keep those events beside the order timeline. Comparing screenshots from different parts of a changing broadcast without context can exaggerate or hide meaningful differences.
Limit the interpretation
A snapshot sequence supports a description of observed audience conditions, not a count of distinct people or guaranteed attention. Compare it with the service’s actual unit and evidence. Ask about unexplained mismatches rather than converting every variation into an exact delivery claim.
Decision checklist
| Decision | What to check |
|---|---|
| Timing | Preselected labelled observations |
| Context | Events affecting the broadcast window |
| Interpretation | Snapshot audience rather than distinct people |
Worked example
For a hypothetical hour-long request, observations at the start, midpoint and end reveal more context than the peak screenshot alone. If a major event occurs between them, note it rather than attributing the peak solely to the order.
Example figures explain the decision; they are not current prices or promised results.