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.
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.
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.
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.
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.
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.