12 lines
1.4 KiB
HTML
12 lines
1.4 KiB
HTML
<p>Gift events are dense, bursty, and easy to miss if you only watch an on-screen ticker. Tracking them as data lets you thank the right people, notice unusual spikes, and review a session without scrubbing a recording.</p>
|
|
<h2>Capture the fields that matter</h2>
|
|
<p>At minimum log sender handle, gift name, quantity, diamond or coin value if available, and timestamp. Without value, a “Rose x99” and a high-tier gift look the same in a naive count. Without a handle, you cannot follow up.</p>
|
|
<h2>Burst handling</h2>
|
|
<p>Combos arrive faster than a human can type. Debounce on-screen toasts so operators see a summary, but keep the raw events in the archive. Summaries are for the shift. Raw events are for the post-show recap.</p>
|
|
<h2>High-value thresholds</h2>
|
|
<p>Define two alert tiers before the show: “acknowledge in chat” and “pause other work and thank on camera.” Numbers differ by creator. The mistake is using one threshold for every room and then ignoring the alerts.</p>
|
|
<h2>After the live</h2>
|
|
<p>Export the gift table, sort by value, and mark who already received a public thank-you. Repeat gifters over several nights are a relationship list, not a one-off statistic.</p>
|
|
<h2>Integrity</h2>
|
|
<p>Do not invent gift values. If the upstream event omits a field, store it as unknown. Fake precision in recap decks trains teams to distrust the whole pipeline.</p>
|