Recent Events Widget: Set It Up in OBS

Why add recent events to a stream

A recent events widget shows the latest support, follows, or viewer actions without waiting for the next alert. It is a quiet signal that the channel is active and viewer actions have visible space on screen.

The value is not decoration. A well-placed list helps the streamer thank people later, return to the last donation, and show new viewers that support is part of the live show.

Do not put recent events in the center of the scene. It is a support layer next to alerts and goals, so it should be readable but calmer than the main reaction moment.

Step 1: choose which events matter

Start with only the events you actually want to mention live: donations, subs, follows, or recent support messages. If the list mixes too many types, viewers cannot tell what matters.

For a smaller channel, a shorter list with three to five entries usually works better. An empty or very long history looks worse than a modest widget with a clear label.

Name the widget in the channel voice: `Last support`, `Recent events`, or `Thanks for the support`. The label should fit the space you give the layer.

Step 2: add the widget as a Browser Source

In OBS, add `Sources` -> `+` -> `Browser`, paste the private recent events URL, and set the size to match the layout. OBS Browser Source loads the web widget without a separate plugin, so viewport and refresh testing matter most.

For a side list, start with a narrow source such as 360 x 640. For a lower bar, use a wider layout, but do not let text cover captions, a minimap, or in-game chat.

Name the source `Recent events - main` and lock it after positioning. During an incident, it is easier to separate the event list from the alert, donation goal, and chat layers.

Step 3: tune the layer for readability

Recent events should be visible during slower moments without competing with gameplay. A right column, lower-left corner, or starting soon bar usually works best.

Use less animation than alerts. The list should remind viewers about recent actions, not trigger a second alert every time it changes.

Check contrast on both dark and bright game scenes. If viewer names are readable only on one scene type, add a subtle background or simplify the palette.

Step 4: test updates before going live

Before streaming, trigger a test event, refresh the scene, and confirm the entry appears without a manual reload. Then switch scenes and make sure the list returns in the same state.

Record a short clip and watch it like a viewer. Check whether the viewer name fits, whether the timestamp is useful, and whether the list feels like a second chat.

If the widget disappears, check the private URL, widget enabled state, Browser Source refresh settings, and whether another OBS layer is covering it.

What to measure after publishing recent events

After publishing, measure article CTA clicks, `recent-events` setup starts, and sessions that return to widget editing after the first test.

On the channel, watch whether viewers refer to recent support more often or ask how to appear on the list. That signal is stronger than the widget simply existing.

Experiment P09-E1 should compare a compact list with a more visible version. The winner is the variant that improves CTR and engaged sessions without complaints that the screen feels crowded.

Preguntas frecuentes