TikRadar’s capture engine runs on our servers, not in your browser. For every tracked creator, the system watches for their next LIVE and connects the moment it starts — you do not need to be awake, online, or anywhere near a computer. Sessions capture whether anyone is looking at the console or not.
Once connected, the engine records the broadcast’s public event stream: every gift (with its diamond value and combo count), every comment, like, join, follow, and share, plus PK-battle state and the identity data the broadcast exposes — nicknames, avatars, gifter levels, fan-club levels, moderator and subscriber marks.
Events persist to the database the instant they arrive, then fan out live to every open console over WebSocket. That is why the feed moves in seconds — and why history survives: the calendar, the per-session stats, the leaderboards, and the exports all read from the same captured record, not from a cache that expires.
The engine is built for the messy reality of live streaming — creators drop and reconnect, battles restart, rooms end mid-gift. Reconnects are automatic, sessions are stitched into a coherent history, and a broadcast’s numbers keep adding up across interruptions. We read the public broadcast only: the same data any viewer in the room can see, captured properly.