Events

Events are the heartbeat of your stream. Every follow, sub, cheer, raid, channel-point redemption, super chat, tip, and Spotify track change flows through Lumio's event pipeline in real time. The Dashboard gives you a live feed of what is happening on every connected platform, and the same stream powers your overlays, automations, and bot reactions.

Lumio surfaces the same live feed in two places: the dedicated Events page in the sidebar and the /popout/events window for OBS and secondary monitors. This guide covers both, plus filtering and searching, sending test events, the channel-status indicator, and every supported event type.

Where to find it

• Events page (/dashboard/events): a dedicated, full-height feed in the sidebar under Stream → Events, right below Chat. This is the primary place to watch and filter events. It requires the events:read permission and the feature:events plan feature.
• Popout window (/popout/events): a borderless copy of the same feed for a second monitor or OBS browser source.

While Events opens on the dashboard or in a popout, its header, tabs and search bar keep their places and the feed shows loading rows. A hidden header or footer stays hidden during loading. Live events that arrive while the first history read is pending remain in the feed when that read finishes.

Both surfaces share the same feed component, so filters and display settings you pick carry across them, and each updates automatically as long as the WebSocket is connected. The Dashboard home does not embed the live feed - it carries the Test Events panel and a compact stream-history overview (the last few sessions) instead.

Quick start

1. Open Stream → Events in the sidebar for the full feed.
2. Connect at least one streaming platform under Manage → Connections so events can flow in.
3. Watch the feed. New events push in from the top.
4. If nothing arrives, go to the Dashboard home and click the Test Events header to expand the panel and fire a fake follow, sub, or cheer to verify your overlays and automations.
5. For a dedicated monitor, open the popout with the external-link icon (on the Events page or the home panel) or load /popout/events directly.

The event feed

Panel layout

Every surface shares the same controls:

• Tab toggle (Events / Filters) - switches between the event list and the filter controls.
• Search box - filter by any text in the event (username, message, reward title, track name). Placeholder reads Search events....
• Settings gear - on both the Events page and the popout, a gear opens the display settings (font size, emote size, timestamps, badges, avatars, viewer count, and the header/footer toggles) shared with the chat popout. The font-size slider scales the row text and its emotes together; the emote-size slider (0.5×–2.0×) tunes the emotes on top of that. The General tab also carries a Region & language block (language, time zone, date format, and time format) - a second entry point to the same global user preference as Dashboard → Settings, marked as applying everywhere you sign in; it is read-only in a token-authenticated popout. Both surfaces load older events automatically as you scroll (infinite scroll) - there is no page-by-page counter.

Each row shows the platform icon, a colored type badge (e.g. Follow, Sub, Bits, Raid), the username, the timestamp, and an event-specific payload (message, amount, reward title, etc.). Headline numbers sit as small chips right beside the type badge rather than under the name - a raid's viewer count (incoming, outgoing and completed), cheered bits, KICKs sent on Kick (500 KICKs), a resub's month count (×3), or an ad break's length in seconds next to its System badge. The Bits and KICKs chips carry a small graphic in front of the amount - the cheer's tier graphic or the Kick gift's sticker - and cheermotes in a cheer's message (Cheer100) render as graphic plus amount, as in the chat. A KICKs row also names the gift after the sender (trainwreck_fan · Rage Quit). The avatar keeps its place on the left; when no avatar is shown (avatars turned off, or an anonymous sender) the graphic takes that spot instead. Without a graphic (a Kick gift Lumio does not know yet, or an older event) the chip is text only. The graphics follow the font-size slider everywhere; cheermotes in the message box also follow the emote-size slider, while the chip graphic and the large graphic in the avatar spot follow only the font size. Twitch's larger cheermote image is loaded on high-resolution screens and for large graphics, so they stay sharp. With animations off or your system's reduced-motion setting on, the graphics show their still image, and where the platform sent no still image, the plain text instead of an animation. Clicking the username - or the small ⓘ button beside it - opens the User Info Card (see below). The username click target and the button appear together and only where a real platform user backs the row (not on channel-wide events like raids out or hype trains, the anonymous gifter, or Spotify).

The header also shows the total event count - "No events yet", "1 event total", or "42 events total" - and, while any channel is live, a small viewer-count pill per online platform.

Twitch Shared Chat session events

The feed shows Shared Chat started, channel joined, channel left and Shared Chat ended as Twitch events at the time they happened. Start and end show the host-first channel stack and partner details; join and leave show the affected channel. A join reconstructed from a later check says Detected later. An unavailable category, viewer or follower value is simply omitted. Use the Shared Chat chip to see these session events, or switch individual types on and off in the existing Twitch filter group. They are on by default and do not open a chat alert. The same session lines appear in the chat's All and Twitch tabs, with start/end details collapsed there.

Twitch Shared Chat partner events

During a Twitch Shared Chat session, subs, resubs, gift subs, upgrades, pay-it-forward, raids into a partner and Bits that happen in a partner channel appear in the feed as well. Their name line starts with a channel chip: the partner channel's channel-coloured avatar plus its name in a grey pill (a long name is shortened with …; hover: "Happened in {channel}'s channel (Shared Chat)"), so they never read as your own events. The chip shows in both the full and the compact feed, also with the type badge or avatars switched off. The stream report's announcement list names the partner channel next to its avatar the same way.

Partner events use the same filters as your own events of that type and do not count in your stream history. To hide all of them, switch off Events from Shared Chat partners in the feed's display settings (gear icon, on by default). The four Shared Chat session events always stay; the switch changes only what the feed shows.

Real-time updates

The dashboard maintains a WebSocket connection to the API and subscribes to the events:\{account_id\} and chat:\{account_id\} channels. Events flow through Redis pub/sub → API → WsServer → browser. When the connection drops, Lumio reconnects with exponential backoff (1s, 2s, 4s … capped at 30s) and you will see the connectionLost banner briefly.

Reconnect required

The per-platform stats row in the header (viewers / likes / views) doubles as a health indicator. If a platform's OAuth connection expires and needs reconnecting, that platform shows a reconnect-required error pill - and it stays visible even while the channel is offline (a dead connection is exactly when nothing is live, so the pill must not disappear). This is separate from the transient connectionLost WebSocket notice above. Members who may reconnect channels (connections:create) also get a red entry in the connection notices under the header, with a Reconnect {platform} button (e.g. Reconnect Twitch) that starts the platform's OAuth flow in place. Otherwise reconnect from Account → Profile or Connections; see Connections → Reconnect flags.

New permissions available

When Lumio starts requesting a scope that an existing connection was granted without, the connection keeps working but some events cannot arrive until you reconnect it. The Events page (and the Chat page) then shows an amber needs new permissions entry in the connection notices under the header, one per affected platform - for example "Reconnect Kick to receive KICKs and channel points." Its Grant {platform} permission button starts the same OAuth flow as the Connections page; from a popout window it opens in a new tab. Nothing needs to be disconnected first. The notice is only shown to members who may reconnect channels (connections:create), and a connection that already needs a reconnect (above) shows only that entry. See Connections → Missing scopes.

Filtering

Switch to the Filters tab to narrow the feed:

• Platform - toggle Twitch, YouTube, Kick, Spotify, StreamElements, Discord, Shopify, 7TV, Copyright, System. Twitch, YouTube, Kick, and Spotify appear when the account has the corresponding channel connection; StreamElements appears when a StreamElements token is stored; 7TV appears when at least one Twitch, YouTube or Kick channel is connected. Discord, Shopify, Copyright, and System do not depend on those connections. If Lumio cannot read a connection or token status, its platform remains listed (including StreamElements for a moderator without se-tokens:read). Turning a platform off hides its events from the feed.
• Type - fine-grained toggles for every event type that has appeared for your account (follower, subscribe, resub, cheer, raid, reward, poll, prediction, hype train, superchat, track, tip, and so on).

Filters persist locally, so they stick across reloads. The feed re-queries and the infinite-scroll list resets to match the filtered result set. Disconnecting a platform removes its controls from the Filters tab, but does not erase saved filter choices or older events from the feed history. Those events remain visible when your saved filters and access settings allow them.

Search

The search box performs a substring match on the rendered row. Useful examples:

• Type a username to find every action by that viewer.
• Type a reward title to audit channel-point redemptions.
• Type @yourname to find messages that tagged you.

User Info Card

Clicking a username opens the user's card as a full-page view over the Events page - tinted in the platform's colours, with the page behind faintly visible. It is the same card the chat opens (see User Info Card): the header shows the avatar, name, badges, @username, platform ID and an Open Profile link; on a wide screen the profile facts and moderation actions sit in a left column next to the tabs, on a narrow screen and in the events popout everything stacks into one column. Its tabs:

• Messages - the user's recent chat history on that platform. Links in these messages are clickable and open through the External Link warning (the same one the chat feed uses), so nothing leaves Lumio until you confirm; the warning appears on top of the card and Esc closes only the warning. This works on the Events page and in the events popout.
• Mod Notes - private notes shared with your moderators (requires chat:notes).
• Moderation History - bans, timeouts, deletions and treatment changes for this user.
• Events - every event that user has triggered (follows, subs, cheers, KICKs, redemptions, raids). Cheers and KICKs show their graphic in front of the amount, and the emotes in an event's message (for example a resub message's sub emotes, or the cheermotes in a cheer) render as images.

The card also shows account-created date, the user's own follower count (Twitch only), follow status and date, and the user's treatment status. Close it with X or Esc. Requires events:userinfo (or chat:userinfo when opened from the chat view). The chat-only Highlight / Hide buttons do not appear here.

Test events

On the Dashboard home, Test Event opens a side sheet; on a phone it fills the screen. The button appears with feature:events and events:create. The same catalog is available in the Test-Events popout, including as an OBS dock.

What it does

Sending broadcasts an event marked isTest: true to the account's overlays and dashboard activity. The activity row carries a TEST badge and dashed border. The Events page and Events popout filter test broadcasts out. Tests are not stored and do not affect metrics, the live Now card, milestones or history; the activity row disappears after a reload.

How to fire one

1. Open Test Event from the dashboard header.
2. Search the catalog or choose a platform tab; More contains other event sources. The catalog lists only sources that are connected, whose features are on and that your role may see — see which events are offered.
3. Choose Send on a row to use its defaults, or expand the row to change values or pick random values before sending.
4. Check the confirmation and Just sent list. Again repeats a test. The sheet stays open for further sends.

Use this to:

• Verify a new overlay animation before going live.
• Check several overlay alerts without waiting for real audience activity.

Popout window

Open /popout/events (or click the external-link icon on the Events page) to get a borderless, chrome-free event list suitable for a second monitor, a stream deck browser, or a browser source for your producer view.

Two authentication modes:

1. Cookie auth - if you are already logged in to Lumio in the same browser, the popout uses your session cookie automatically.
2. Popout token - append ?token=YOUR_TOKEN to the URL (e.g. https://lumio.vision/popout/events?token=lm_pop_…). Use this when loading the popout inside OBS, where cookies are unavailable. Create popout tokens under Settings → Channel → Access → Popout Tokens, see Tokens.

The popout respects the permissions granted to the token - a scoped token may hide moderation-only event types or the User Info Card.

The seasonal look also shows in this popout; append &season=off, &seasonStrength=subtle or &seasonMotion=off to the URL to change it for this popout only.

Animations for this view

Open the settings gear and choose Animations → As global, Reduced, or Off. The choice affects this view on the dashboard and in its popout, and is stored per browser and per user/account pair. It can only reduce motion further than your global Animations in Lumio preference; an unavailable looser choice is disabled. For an OBS popout, append &motion=reduced or &motion=off (use ? if it is the first URL parameter) to apply a stricter choice to that URL without saving it. The global preference is read-only in a token popout.

Where these settings apply

These settings apply to you on this account. Events settings are stored in your browser (there is no server copy) and keyed to the pair (you, the channel account you are viewing). This covers both the event-feed display options and the event-feed filter (the platform and type toggles under the Filters tab): switch to a second channel account, or sign in as a different team member of the same account, and they start from defaults — a filter you set while viewing one channel is not applied to another, and never leaks between team members. You set them once per browser context (the dashboard, and again in an OBS popout, which is separate). To reuse them elsewhere, move them deliberately with Export / Import or a preset.

Save and transfer your settings

Your events display options and event filters are stored in the browser, so they only exist where you set them - a fresh OBS browser source, a second computer, or a browser with cleared site data starts from defaults. Transfer settings lets you save them and re-import them anywhere, with no server involved.

Open the Settings cog, go to the Presets tab, and use the Export / Import buttons below the preset cards (the same controls are in the dashboard and the popout). On a plan without the presets feature there is no Presets tab, so Export / Import appears at the bottom of the General tab instead.

• Export - tick the sections you want (grouped Chat / Events / Music; your Events sections are pre-selected here); sections with nothing saved are greyed out. Take them with you by Copy code (a single LS1… line to send over a messenger), Copy link (a share link that carries the same code and opens the events settings with the import preview directly when clicked on any signed-in device - both update live as you change the selection), Copy JSON, or Download a file. Very long links can be wrapped by some messengers - for those, use the code or the file.
• Import - pick a file, drop it onto the dialog, or paste a file, an LS1… code, or a share link into the one input (detected automatically). A preview shows what each section will replace before anything is written; import replaces a section wholesale, it does not merge. The page reloads afterwards.

Event filters record which platforms and event types you show. Newly added event types are enabled automatically on the next load, so an older file never silently hides a brand-new event type. Importing something from a newer version of Lumio, an incomplete code, or anything that is not a valid Lumio settings file or code, is refused with a clear message.

See the Multichat guide for the full list of what is and is not included in a settings file.

Presets

The Events settings panel also has a Presets tab - named snapshots of your Events display and filter settings, saved to your account so you can switch layouts and reuse them across devices. (Because the Events panel used to be a single column, the Presets tab is what gives it a tab bar.) New preset opens an assistant to choose what to store and name it; each saved preset card offers Load, share, overwrite, rename and delete, with a quota line showing how many you have used. Share copies a code/link for the preset and can make it visible to your whole account (with the presets:share permission); presets teammates share into your account appear in a Shared from the channel section you can load or save as your own. In a popout you can load a preset but not change or share one. See the Setting Presets feature page for details.

Channel-status indicator

While a channel is live, the Events header shows a small pill per online platform with that platform's icon and viewer count (and, on YouTube, optional like and total-view counts you can switch on in the display settings). When every channel is offline, no pill is shown. The Dashboard home shows the same state as a LIVE badge on each channel card.

The Spotify worker and some event pollers only run while at least one channel is live (see the Channel Status guide). This saves API calls and avoids logging Spotify tracks when you are not streaming. If you need to bring the Spotify worker up manually, use the Connect button on the Music page - it starts the worker for 30 minutes.

Supported event types

Event type strings follow the platform:action convention (e.g. twitch:follower, youtube:superchat). The full set currently recognised:

Twitch

twitch:follower, twitch:subscribe, twitch:resub, twitch:prime_upgrade, twitch:gift_upgrade, twitch:gift, twitch:pay_it_forward, twitch:bits_badge, twitch:cheer, twitch:raid, twitch:raid_out, twitch:unraid, twitch:raid_done, twitch:reward, twitch:reward_status, twitch:hype_train, twitch:hype_train_end, twitch:poll, twitch:poll_end, twitch:poll_delete, twitch:prediction, twitch:prediction_lock, twitch:prediction_end, twitch:goal, twitch:goal_end, twitch:ad_break, twitch:stream_online, twitch:stream_offline, twitch:stream_update.

Twitch also reports twitch:mod_added, twitch:mod_removed, twitch:vip_added and twitch:vip_removed. The feed labels them New Mod, Mod removed, New VIP and VIP removed. In chat they are centred event rows with the platform icon first when that setting is on: grants use the role colour, while removals use a grey dashed treatment. The fallback VIP symbol is a diamond. Each type has its own chat Events switch, on by default. The row always says Moderator for a mod, including a Lead Moderator, because Twitch does not report that distinction. These role rows exist only for Twitch; Kick does not report its mod, VIP or OG commands to Lumio, and YouTube reports bans only.

The three Twitch pin types are twitch:pin_added, twitch:pin_updated and twitch:pin_removed. The feed calls them Message pinned, Pin duration changed and Pin removed; the icon at the start identifies the platform. Each type can be filtered independently and is on by default. A Pin removed row also says how long the pin stood (or that it expired): in seconds or minutes under an hour, in hours and minutes from one hour, and in days and hours from one day, rounded down.

A goal row shows the goal text as its title and the translated goal type underneath, with the progress as a chip in your language's number format (e.g. 13.284/14.000). Its badge reads Goal Started when the goal is created and Goal Reached or Goal Missed when it ends (Goal Ended if Twitch did not say). Progress updates in between are not listed. Stream Offline shows the stream's length as a clock chip, e.g. 3h 12m.

A Twitch prediction's end badge reads Prediction Resolved (Vorhersage aufgelöst in German) when Twitch reports it as resolved, or Prediction Canceled (Vorhersage abgebrochen) when it was canceled. If Twitch sends no status, the badge reads Prediction End (Vorhersage Ende). The prediction title and outcome breakdown stay visible in the event row.

A channel-point redemption shows the reward title, its cost in points and the viewer's input. When you complete or refund a redemption in Twitch's reward queue, that status change is its own twitch:reward_status row that reads completed or refunded; it is on by default and has its own toggle under the Twitch heading of the type filter. Creating, editing or deleting a reward is not listed in the feed — those changes reach widgets and extensions live only.

YouTube

youtube:subscribe, youtube:member, youtube:superchat, youtube:supersticker, youtube:gift_membership, youtube:gift_membership_received, youtube:poll, youtube:poll_end, youtube:stream_online, youtube:stream_offline.

A YouTube poll is one channel-event row titled with the poll question. Below it, each option shows its bar and its vote count, or its share of the votes when YouTube sends no count. The row updates in place on every vote, and once the poll is closed the leading option gets the trophy. Polls are not stored, so the row is only there while the page is open.

Stream start and stream end render as channel events with a System badge, like Twitch and Kick: Stream Online shows the broadcast's title underneath (YouTube has no stream category, so none is shown), Stream Offline shows how long the stream ran as a clock chip (e.g. 3h 12m) when the start time is known, otherwise the label only.

Kick

kick:follower, kick:subscribe, kick:resub, kick:gift, kick:kicks, kick:reward, kick:reward_status, kick:stream_online, kick:stream_offline, kick:stream_update.

kick:pin_added and kick:pin_removed use the same Message pinned and Pin removed labels, with the Kick platform icon.

Pin rows have the ordinary event layout. The large head avatar belongs to the person who pinned the message on Message pinned and to the sender on Pin duration changed or Pin removed. The head name has no badges. Below it, the message's sender appears with avatar, badges, text and the time they wrote the message when known. The planned duration appears as a chip by the type label. The moderator who pinned and a replaced sender show avatar and name without badges. Names open the User Info Card when the viewer has chat:userinfo; otherwise they are plain text. The feed row has no jump link to the message.

Kick rows look like their Twitch counterparts: the viewer's name and avatar (click it for the User Info Card), a months chip on a resub, the gift count and every recipient on a gift (an anonymous gifter shows a ? avatar and no clickable name), a gold KICKs row with the amount chip and the sender's message, and a channel-point redemption with the reward title, its cost in points and the viewer's input. A redemption's later status change is its own kick:reward_status row that reads accepted or rejected. Stream start, stream end and stream-info changes render as channel events with a System badge and the stream title or the changed fields (see Stream updates), not as a user row. Every Kick type is on by default and has its own toggle under the Kick heading of the type filter; a filter saved before a type existed turns the new type on automatically. Kick events need the platform:kick plan feature.

Stream updates

A Stream Update row (twitch:stream_update, kick:stream_update) names only the fields that actually changed, each with its own label:

Label	Shows	Platforms
Title	The new title	Twitch, Kick
Category	old → new category (game); only the new one when the previous is unknown	Twitch, Kick
Language	old → new broadcast language, as a language name in your interface language (e.g. English → German); the raw code when there is no name for it (Twitch's other)	Twitch, Kick
Tags	The new tag list, comma-separated; — when every tag was removed	Twitch

An unchanged field is never repeated. The title shows only the new value so the line stays readable. The same line appears on the Events page, in the chat inline event and on the Events tab of the User Info Card. Stream updates recorded before Lumio tracked language and tags show title and category only. On Twitch, a tag-only edit is reported together with the next title, category or language change — Twitch sends no update for tags alone (details: Stream update payloads).

Discord

discord:member_join, discord:member_leave, discord:boost.

Spotify, StreamElements, Shopify, Copyright, System

spotify:track, spotify:play, spotify:pause, spotify:skip, spotify:previous, spotify:seek, spotify:shuffle, spotify:repeat, spotify:volume, spotify:device, spotify:queue_add, spotify:playlist_create, spotify:playlist_edit, spotify:playlist_delete, spotify:playlist_add, spotify:playlist_remove, streamelements:tip, shopify:order, shopify:order_paid, shopify:product, copyright:warning, copyright:blocked, copyright:clear, system:test.

Permissions

Permission	What it unlocks
events:read	View the Events page and the popout
events:create	Fire a test event
events:userinfo	Open the User Info Card on an event row

Tips & best practices

• Use test events liberally before going live. Fire twitch:raid, twitch:cheer, and youtube:superchat to make sure overlays, alerts, and automations all behave.
• Pin a popout to your control monitor. /popout/events in a narrow window makes a great always-visible activity feed next to your streaming software.
• Generate a scoped token for browser sources under Settings → Channel → Access → Popout Tokens so a compromised stream PC does not expose your full Lumio session.
• Filter aggressively during raids. Hide spotify:* and chat:* noise so you can focus on follow/sub/cheer incoming during the chaos.

Troubleshooting

No events arrive

1. Check the channel-status pill - if all channels are offline, most platforms only push events for live streams.
2. Open Manage → Connections and confirm every platform shows a green Connected badge. Re-authorize anything showing Not connected.
3. Fire a test event. If it shows up but real events do not, the issue is with your platform connection or that platform's event subscription scopes.
4. Reload the page to force a WebSocket reconnect.

Connection lost - reconnecting… banner persists

The browser cannot reach the API's /v1/ws endpoint. Causes: your auth token expired (log out and back in), a network blocker (VPN, corporate firewall), or the API is genuinely down. Check Account → Sessions to confirm your session is still valid.

Test events do not fire

You need the events:create permission. Ask your account owner to grant it on your role under Settings → Channel → Roles.

Popout shows Invalid or expired token

The token was revoked, expired, or scoped too narrowly. Create a new one under Settings → Channel → Access → Popout Tokens and update the URL in OBS / your second monitor.

Popout shows No authentication token provided

You loaded /popout/events outside a browser session. Append ?token=YOUR_TOKEN to the URL, or load it inside the same browser where you are logged in.

Related

• Channel Status - how online/offline state gates workers and pollers.
• Overlays - how events drive on-stream widgets and alerts.
• Automation Templates - react to any event with the visual builder.
• Chat - chat messages and moderation share the same WebSocket channel.