A YouTube membership alert appears on your livestream only when memberships are enabled for an eligible channel, an alert provider is linked to that channel, and the provider’s alert source is in the broadcast scene. For a 24/7 stream, you also need to test the alert in the scene that stays on air and avoid settings that leave events waiting for someone to approve them.
The workflow below uses Streamlabs as an example: connect the YouTube channel, customise its Members alert, then add the Alert Box to OBS. The same principle applies with another provider, but check that it supports the membership events you want to show and offers an alert source your streaming software can display.
Check membership and alert requirements
Start with the channel, not the overlay. YouTube says channel memberships or Super Chat must be eligible and turned on before you configure a Streamlabs integration. Check the current YouTube Help guidance for connecting Streamlabs and confirm the membership feature is available on the channel you intend to stream from. Account eligibility and product availability can change, so do not assume a setting you saw on another channel will appear on yours.
You need three parts working together:
| Part | What to check | Why it matters |
|---|---|---|
| YouTube channel | Memberships are enabled and the channel is eligible | The provider cannot display a membership event the channel is not able to receive. |
| Alert provider | The correct YouTube channel is linked and the Members event is configured | A provider account on its own does not connect an event to the right channel. |
| Broadcast scene | The alert widget is present and visible in the scene that is on air | An alert configured in a dashboard is not automatically part of the video sent to YouTube. |
You will also need access to the provider account, the streaming software that runs the channel, and a way to test the alert before leaving the broadcast unattended. If you have a scene collection with several scenes, identify which one is live for most of the day and whether the stream switches away from it. That choice determines where the alert source must be placed.
Keep membership alerts distinct from subscriber alerts when you test and troubleshoot. YouTube memberships are a paid channel feature; a channel subscription is a different event. Streamlabs documentation discusses delays and privacy effects for subscriber alerts, but those points should not be treated as evidence that membership alerts behave the same way. If a new member event is what you need, select the Members event rather than a generic subscriber alert.
An alert is only the on-screen acknowledgement. It does not enable memberships, collect payment, or prove that every live event will be delivered. Treat the overlay as one component of the broadcast and check the channel’s membership status separately.
Link the eligible channel to a provider
For the Streamlabs route, sign in to Streamlabs using the Google account associated with your YouTube channel and follow the channel-linking flow. YouTube’s integration instructions explain the connection process; Streamlabs also has its own YouTube setup documentation. During setup, confirm that the selected platform and channel are the ones you mean to use. If you manage more than one channel, it is easy to customise an alert on the wrong account and only discover the mix-up when you test it.
Once linked, open the Alert Box settings and look for YouTube Members or the equivalent membership event. Do not stop at seeing the provider account listed as connected. The event must be enabled within the alert configuration, and the widget you later add to OBS must belong to the same provider account and theme. If the provider lets you select among themes or widget sets, note which one you are editing before copying its source.
Streamlabs is a documented example, not a requirement. YouTube’s integration page also lists StreamElements for live member recognition and alerts, including membership-level information. If you use a different provider, check its current documentation for event support and the method for putting the overlay into your software. A useful comparison is whether it supports new members, whether it can show the details you want, and whether it provides a widget or browser-compatible URL. Do not choose on a feature label alone; make sure the specific event exists in your linked account.
The OBS guide to starting a 24/7 YouTube radio stream covers the broader scene and broadcast setup. Here, the important distinction is that linking a provider is account configuration, while adding the widget to a scene is a separate production step.
Enable and customise the Members alert
In the provider’s Alert Box, enable the Members event and set the appearance to suit the channel. Streamlabs supports event-specific alert customisation and variations. Depending on the available controls, you can choose an image or animation, sound, display duration, and message behaviour. Save the settings before moving on; a preview that was never saved may not match the widget you eventually place in OBS.
Keep the alert legible against the video underneath it. A devotional channel might use a restrained visual and a short message so it does not compete with lyrics. A local news loop may need the alert in a corner that does not cover a headline or ticker. For a study or ambience stream, consider whether sound is appropriate at all: an alert sound can interrupt the reason someone left the channel playing. Make choices for the viewing context rather than copying a prominent style from another channel.
If the provider offers variations for different membership events, decide which ones should appear before you go live. New membership, gift membership, and membership-level details may be handled differently, and provider support can vary. Streamlabs documents gifted-membership widget support, but its published guidance described availability during a limited YouTube rollout. Check whether the relevant event is available in your own account now, then test that event type rather than assuming the general Members alert covers it.
Be deliberate about names and message text. Use the provider’s intended event fields and avoid adding instructions or content that could make an alert misleading. If you allow custom messages, consider whether they need moderation; a decorative acknowledgement with a fixed message is simpler to run unattended than a layout that displays unreviewed viewer text.
Add the Alert Box to the live scene
The provider’s dashboard does not put anything on the YouTube picture by itself. You must add its alert source to the software producing the broadcast. In Streamlabs Desktop, the documented route is to add Alert Box from Sources. In OBS, use the Streamlabs widget integration if you have it, or add the widget URL as a Browser Source. OBS does not generate third-party alerts natively; its Browser Source documentation describes how web content can be shown as a source in a scene.
For a Browser Source, copy the Alert Box widget URL from the provider and add a Browser Source in OBS. Paste the URL into the source properties, then set its dimensions to suit the alert design and the canvas. The precise labels in the provider and OBS can change, so follow their current interfaces rather than relying on an old screenshot. Treat the widget URL with care if your provider treats it as account-linked: do not post it publicly, and follow the provider’s current account guidance.
Place the source where the event can be seen without hiding the content viewers came for. In OBS, sources higher in the scene’s order appear over those beneath them. If the alert is behind a full-screen background, it may be configured correctly and still be invisible. Check both its layer position and its visibility toggle, and size the browser area so animations and text are not clipped.
Do not judge placement only from the provider’s dashboard preview. A preview can show the widget while the actual OBS source is missing, hidden, incorrectly sized, or tied to another theme. Test through the intended scene so you see the composed result, including the background, text-safe areas, and any other overlays.
Use a Browser Source without the plugin
A plugin is not necessary for the basic OBS method if the provider supplies a browser-compatible widget URL. Add the URL as a Browser Source, keep the source in the scene, and test it. This keeps the alert integration separate from the rest of the OBS scene configuration, though you will need to revisit the source if you replace the widget URL or change provider settings that affect its output.
Check that the source is not hidden behind another element, that it is enabled, and that its browser area matches the overlay’s expected layout. If your alert design uses animation or custom styling, inspect the result in the live scene rather than assuming the browser will render exactly like the provider’s editor. Streamlabs’ troubleshooting guidance for alerts includes checks such as source layering and widget configuration; use the current instructions for the version you run.
A browser overlay is a web-based source, so it can be refreshed or re-added if it stops displaying. Do not make that your only plan for recovery in an unattended broadcast: a person cannot click refresh at three in the morning if no one is monitoring the channel. Test after changes and include a periodic visual check in whatever monitoring routine you already use. The guide to alerts that reach you while monitoring a 24/7 stream can help separate alerts for operators from alerts shown to viewers.
Keep the source in the scene that stays on air
For an always-on stream, the alert must exist in the scene that remains on air. If your broadcast uses a single static scene, add the source there and verify it is visible. If OBS switches between scenes—for example, between a video loop, a holding screen, and a scheduled segment—add the alert source to every scene where you expect a membership event to appear. A source in one scene does not automatically show in a different scene unless you have deliberately built a shared scene arrangement.
Check the whole scene path, not just the most attractive layout. A channel might run a main loop for most of the day but switch to a slate when a file ends or a scheduled programme begins. If the alert is absent from that slate, a membership event during the transition will not appear there. The goal is not to put the alert everywhere by default; it is to know which scenes are on air and decide consistently where viewers should see recognition.
This is also a useful point to check composition. Keep alerts away from persistent labels, lyrics, captions, lower thirds, and controls that should remain readable. A membership message can be brief, but a long animation or oversized graphic can obscure the broadcast. If the provider allows you to alter duration or layout, make the smallest change that resolves the overlap, then retest it in the scene.
Scene changes are easy to overlook after a rebuild. When you add a new source, rename a scene, or switch collections, confirm that the source has not been left in an old scene collection. A bitrate guide for YouTube radio streams addresses a different part of stream quality, but it is a useful reminder that the on-air result depends on the complete broadcast setup, not a single setting.
Test the alert and remove approval bottlenecks
Use the provider’s test control or in-software test widget, then watch the intended OBS scene. Streamlabs documents dashboard and in-software testing. Confirm that the alert appears at the expected size and position, its sound level is sensible, and the background remains visible. A test verifies the visual integration; it does not prove that every real platform event will always arrive or that an unattended broadcast will never fail.
If you use a moderation delay, check what it requires. Streamlabs says its unlimited alert moderation delay requires an operator or moderator to accept events, and unaccepted alerts will not play. That can be useful when someone is actively reviewing alerts, but it is a dependency for an unattended channel. If nobody will be watching, choose a workflow that does not leave every event waiting for approval, or arrange a moderator who understands that the broadcast depends on timely action.
This does not mean turning off sensible moderation everywhere. Review what the provider’s settings actually hold for approval and what is displayed automatically. If the alert includes only a fixed acknowledgement and limited event details, that may have different moderation needs from a design that displays user-supplied text. Decide based on what appears on screen and who will be responsible when the channel is unattended.
When an alert fails, work through the simple checks first: confirm the right YouTube account and widget theme, confirm the Members event and its variations are enabled and saved, check source visibility and layer order, and check whether alerts are paused or awaiting approval. Then refresh or re-add the Browser Source and test again. If you use custom HTML or CSS or altered animation settings, temporarily return to a known simple configuration to see whether the customisation is the cause.
Retest after changes to the YouTube account, provider settings, OBS scenes, or software. Membership test controls may not reproduce every real event type, especially gifted memberships or level-specific behaviour, so verify availability in the provider account and test where possible. Avoid promising viewers that every membership will trigger an alert; the setup is a practical integration, not a guarantee of continuous delivery.
For a 24/7 service, an alert source is one more component to monitor alongside the stream itself. A cloud-run broadcast can remove the need to leave your own computer switched on for the video to continue, and StreamNeo can also remove the repeated need to keep a local machine running for a file-based channel; neither point replaces checking that the membership provider and on-air scene are configured as intended. If the file and channel are ready, the next step is to compare operating arrangements and try the setup.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can I add a YouTube membership alert without an eligible channel?
No. Memberships need to be available and enabled for the channel, and the alert provider must be linked to it. The alert source must also be present in the broadcast scene; configuring only the provider dashboard is not enough.
Do I need the Streamlabs plugin in OBS?
No, not for the Browser Source method. If Streamlabs provides a widget URL, you can add it as a Browser Source, position it in the scene, and test it there. OBS displays the third-party overlay; it does not create the membership alert itself.
Will the alert appear in every scene automatically?
Not necessarily. Make sure the source is in each scene where you want an alert to show, or use a scene structure that deliberately shares the source. Test scenes that the broadcast can switch to, including holding or transition screens.
Can alerts run unattended if moderation is enabled?
It depends on the moderation setting. Streamlabs documents an unlimited alert moderation delay that requires a person to accept events; an unaccepted event will not play. For a channel with nobody monitoring it, avoid a required approval step or arrange a moderator to handle it.