A Streamlabs Cloudbot loyalty store lets viewers spend points on rewards such as access codes, sound effects and stream perks. To set one up, enable Cloudbot, turn on its loyalty system, add a store item, and configure its cost, limits, content and redemption route.
The details matter: an access code needs codes to distribute, while a reward that asks viewers for information is better suited to the tip-page redemption flow. Streamlabs’ dashboard labels and available options can change, so use the steps below as a route through the current setup rather than assuming every screen will look exactly the same.
Before You Set Up a Loyalty Store
Start by deciding what the reward is and how you can fulfil it. A sound effect can be played on stream; an access code is something you provide for a viewer to receive; a stream perk might be a follow, greeting or other action you agree to provide. The store is a way to exchange points for a defined reward, not a way to create the reward content for you.
It helps to write down four things before opening the dashboard: the reward name, what the viewer receives, how many points it should cost, and whether you need information from the viewer to fulfil it. For example, if a viewer can redeem a personalised greeting, decide whether you need their preferred name or pronunciation. That choice affects which redemption route will be practical.
Cloudbot and its loyalty system are prerequisites in the documented workflow. Do not assume that the store can be enabled independently of Cloudbot, or that a feature configured for one channel platform will behave identically on another. Streamlabs’ Cloudbot loyalty store guide describes the store features, while its current Cloudbot setup guide covers enabling the bot. Check those official pages if the dashboard differs from the steps here.
This is separate from keeping a live channel on air. If you are planning a continuous programme, a loyalty store does not make the video loop or maintain the broadcast; those are separate jobs. The distinction is useful when planning a 24/7 study stream as a live broadcast rather than a Premiere or deciding how looping prerecorded video works on YouTube Live.
Enable Cloudbot
Sign in to Streamlabs and open the dashboard area for Cloudbot. Enable it there. The exact layout and wording can change, so look for Cloudbot’s main enable control rather than relying on a particular button position.
Streamlabs’ quick guide also recommends linking the relevant channel account and granting permissions needed for bot activity. Its examples include granting moderator status on Twitch or Kick with /mod Streamlabs, and adding Streamlabs as a moderator through YouTube Studio for YouTube. Treat these as platform-specific Cloudbot setup steps, not as a promise that every loyalty-store feature needs identical permissions. Follow the current Streamlabs and platform instructions for your channel.
A bot that cannot participate in chat may be unable to deliver the experience you expect, even if an item appears in the store. If you are setting up YouTube, review the relevant channel role and permissions before testing. Do not share a stream key as a substitute for granting the correct account permissions; the key controls broadcasting, not a Cloudbot loyalty reward. If you use an encoder too, this explanation of using a YouTube stream key without exposing it in shell history covers a different, security-sensitive part of a streaming setup.
Once Cloudbot is enabled, confirm that the dashboard recognises the channel account you intend to use. A loyalty store attached to the wrong account or an unlinked channel can lead you to configure an item that viewers cannot use in the expected chat. Check the active channel identity before moving on.
Turn On the Loyalty System
In the dashboard, select Loyalty, then open its settings and enable the loyalty system. Streamlabs’ documented route places the loyalty controls under Cloudbot. If the navigation has changed, use the dashboard’s Cloudbot section and look for Loyalty or its settings rather than assuming the store is a separate product area.
The settings can include the name shown for points and the activities that earn them. Pick a points name that viewers will understand in chat and on the store page. If you rename points to match your channel, explain the name once in your channel information or pinned message so viewers know that it is the loyalty balance they spend on rewards.
Review the earning settings before assigning costs. The system may award points for viewer activity, and the settings let you shape the amounts and block selected users from earning, as described in Streamlabs’ loyalty-points guide. The exact earning behaviour depends on the available controls and the platform context; check what is shown in your account. Avoid setting a reward cost by guesswork alone. Consider how quickly a regular viewer could earn the balance, and whether a one-time reward should be attainable sooner than a recurring perk.
A useful first test is to make a small, clearly described reward and check whether the points balance is visible to the intended audience. Do not promise that a particular viewer will earn points at a fixed rate unless you have checked the current settings and tested the relevant channel. Point names, earning rules and store item costs work together, so a change to one can make the other confusing.
Open the Store and Add an Item
With Cloudbot and loyalty enabled, open Store in the Cloudbot area. Streamlabs’ guide describes choosing “Add Your First Item” for an empty store, then selecting a reward type and entering a name and description. If you already have items, the button or menu may instead offer a general add-item action.
Make the name specific enough to distinguish the reward from other items. “Song request” is clearer than “special reward” if the viewer receives one song request. In the description, state what is included and any limits that affect fulfilment, such as whether the reward is delivered in chat or requires a response from you. Keep the offer within what you can reliably provide during your stream schedule.
A store item should not be a vague promise of attention. If you offer a greeting, describe when or how it will happen. If it is a code, say what sort of code it is without implying that every code is interchangeable. For a recurring channel, account for the fact that a redemption may happen while you are away from the desk. A reward that needs a manual decision may be easier to fulfil later than one that is expected immediately.
Save only after reviewing the item as a viewer would see it. If Streamlabs presents a preview or item list, check the wording there as well as in the editor. Clear names and descriptions reduce avoidable questions and make it easier to test redemption without accidentally promising more than you can supply.
Choose a Reward Type and Description
Streamlabs documents three store item types: Access Code, Sound Effect and Stream Perk. The choice determines what content you must provide and what happens on redemption. The guide describes access codes for creator-provided codes such as game keys or gift codes, sound effects played through the Alert Box, and stream perks for other benefits, with following a viewer given as an example.
| Reward type | What you prepare | Consider it when |
|---|---|---|
| Access Code | One or more codes to distribute | You have a code-based item and can explain what it provides |
| Sound Effect | A sound file for the Alert Box | The reward is an audible effect that should play on stream |
| Stream Perk | A clear description of the benefit | You will provide an action or experience rather than a file or code |
For an access code, make the description precise and check that you have the rights and supply needed to provide the codes. Streamlabs says codes are distributed automatically when a viewer redeems the item. That delivery mechanism does not establish whether a code is valid, unused or suitable for the viewer, so use codes you have checked and describe any restrictions plainly.
For a sound effect, choose a file that is appropriate for your broadcast and make sure its volume and content are suitable for the channel. A redemption can be audible to everyone watching, so consider how it fits a devotional stream, local news loop or quiet study channel. A sound that makes sense on a gaming channel may be disruptive in a calm setting.
For a stream perk, define the action instead of leaving it open-ended. “Follow the viewer” is an example in Streamlabs’ material, but you can describe a different perk that is feasible for your channel. Avoid wording that implies a guaranteed schedule or outcome you cannot control. A 24/7 Naam Simran stream, for instance, may need a reward that can be handled without interrupting the continuous programme.
Set Cost, Quantity, Cooldown, and Content
Set the loyalty point cost to reflect both the value of the reward and the effort needed to fulfil it. There is no universally correct cost: an automatically delivered code and a personalised action have different fulfilment demands. Check the loyalty earning settings alongside the cost, then consider whether the balance feels understandable for a new viewer as well as a regular.
Quantity controls how many redemptions are available, where that setting is offered. Use a finite quantity when you have a limited supply, such as a set of codes, or when you want to limit the number of manual rewards you can fulfil. For a reward you can repeat, decide whether leaving it available is manageable. Do not enter a quantity as though it were a promise that Streamlabs will replenish the item for you.
Cooldown is a way to prevent repeated redemptions. Set it with the reward’s purpose in mind: a sound effect might need a pause so repeated activations do not overwhelm the stream, while a limited code item may be governed more by quantity than by repeated use. Review the available controls in your dashboard and explain any meaningful restriction in the item description.
Add a thumbnail if it helps viewers recognise the reward. For a sound-effect item, select or upload the sound file through the item settings. For an Access Code item, enter the codes you intend to distribute. Streamlabs documents automatic code delivery on redemption, but you remain responsible for providing appropriate content and maintaining enough available codes for the quantity you set.
You can also choose whether a redemption triggers an on-stream alert using the Redeem Shows Alert control, if it is present. Consider the viewing context before enabling it. An alert can make a redemption visible, but it may interrupt a quiet stream or reveal information you would rather handle privately. Streamlabs’ Alert Box includes a Cloudbot Redemption category for adjusting redemption alerts; check the current controls rather than assuming every alert is enabled by default.
Finally, save the item and revisit its settings if you change the reward content, point economy or channel format. A file, code supply or perk description that was suitable for one broadcast may not suit another. For continuous programming, it is useful to consider the wider limits of repeating episodes in a live stream separately from the loyalty reward itself.
Check How Viewers Redeem Rewards
Streamlabs documents two routes: chat redemption and the creator’s Cloudbot tip page. For chat, enable Redeem Via Chat and set the keyword viewers will use after .redeem. For example, if the configured keyword is greeting, the command format is .redeem greeting. The keyword is the item’s redemption trigger, so keep it short, readable and distinct from other commands.
The alternative is the creator’s Cloudbot tip page, at https://streamlabs.com/<your_name>/cloudbot, where viewers log in to redeem. This route is useful when the item needs information from the viewer. Streamlabs says the tip-page flow can show a popup that collects requirement fields entered for fulfilment. Check the page while logged in or ask a trusted viewer to test the route before announcing it.
If you add requirements for information, decide whether chat is an appropriate route. Streamlabs recommends keeping items with requirements off chat redemption, and documents that items with two or more requirements cannot be redeemed through chat. A request for a preferred name or contact detail is not something a simple chat keyword can collect. In that case, use the tip-page flow and explain what information is needed and why.
Test the complete path, not just the item editor. Confirm that the viewer can find the reward, understands its cost and keyword or page route, and receives the expected result. If it is an access code, check the delivery experience; if it is a sound effect, check the Alert Box behaviour; if it is a manual perk, make sure the redemption appears somewhere you can act on it. Streamlabs’ chat-command instructions provide context for commands on Twitch and YouTube, but follow the current platform and dashboard guidance for your own channel.
When the setup is ready, make the redemption instructions easy to find. A short pinned chat message can state the command, while a channel description can point to the tip page. If you run an always-on stream and are away at times, say when a manual reward will be fulfilled rather than implying that every redemption will receive an immediate response.
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 create a loyalty store without enabling Cloudbot?
The documented Streamlabs workflow puts the loyalty store inside Cloudbot, and it calls for Cloudbot and the loyalty system to be enabled before creating store items. Do not assume the store is available independently; check Streamlabs’ current dashboard and support instructions if the navigation or feature has changed.
Which reward type should I choose?
Choose Access Code for creator-provided codes, Sound Effect for an Alert Box sound, or Stream Perk for another defined benefit. Match the type to what you can actually supply and explain any limits in the description.
Can viewers redeem an item that asks for information in chat?
Streamlabs recommends using the tip-page route for items with requirements, because it can collect information in a popup. Items with two or more requirements cannot be redeemed through chat according to the documented guide, so test the route and current settings before publishing the item.
How do I know the reward works on my channel?
Test it using the channel account and redemption route you intend viewers to use, checking the result as well as the item settings. Cloudbot features and dashboard labels can differ or change across platforms and versions, so consult the current official Streamlabs and platform help pages if something does not match.