12 lines
1.2 KiB
HTML
12 lines
1.2 KiB
HTML
<p>Viewer charts are useful when they change what you do in the next five minutes. They are decoration when they only confirm that a popular creator is popular.</p>
|
|
<h2>Read slope, not peaks</h2>
|
|
<p>A slow climb after a topic change is a stronger signal than a one-second spike from a raid that already ended. Train operators to talk about slope in the recap.</p>
|
|
<h2>Align events to the curve</h2>
|
|
<p>Overlay gifts, follows, and topic changes on the same timeline. A dip after a product pitch is information. A dip after a disconnect is a technical incident. Mixing the two in a client report is malpractice.</p>
|
|
<h2>Sampling</h2>
|
|
<p>If the source updates every few seconds, do not pretend you have millisecond precision. Store the native interval and label charts accordingly.</p>
|
|
<h2>Compare like with like</h2>
|
|
<p>Weekday lunch lives are not Saturday night lives. Compare against the same weekday and timeslot. Cross-slot comparisons create fake emergencies.</p>
|
|
<h2>Action examples</h2>
|
|
<p>Rising chat rate plus flat viewers: ask a question. Falling viewers plus gift burst: thank and hold the topic. Charts that never produce an action should leave the default screen.</p>
|