Keep an event timeline
Record known events such as another creator directing viewers to the stream, a social announcement or a featured segment. An audience increase during an active request does not independently identify its cause. The surrounding broadcast context matters.
Distinguish observation from attribution
Label the audience number as an observation at a particular time, using the metric actually available. Do not assign every increase or decrease to one service. Ask what request-specific evidence is supplied and how it relates to your timeline.
Design a clearer future review
If practical, evaluate a later small test during a less crowded part of the schedule. Keep the target and timing stable and avoid several simultaneous services. A simpler timeline makes investigation easier without proving that all changes belong to the order.
Decision checklist
| Decision | What to check |
|---|---|
| Events | Other sources of audience movement |
| Metric | The observed live-session measurement |
| Attribution | What the evidence can actually connect to the order |
Worked example
During an illustrative request, another creator sends viewers to the channel and the audience rises sharply. Record that event separately rather than reporting the entire increase as delivery from the paid request.
Example figures explain the decision; they are not current prices or promised results.