A Streamlabs Cloudbot Loyalty Store lets viewers spend channel points on defined rewards: an Access Code, a Sound Effect or a Stream Perk. To set one up, enable Cloudbot and its Loyalty System, add an item with a clear cost and fulfillment plan, then tell viewers where and how to redeem it.
These points are a way to run a channel reward system, not cash or a promise of earnings. The practical work is deciding what you can reliably deliver, how many redemptions you can handle, and whether viewers need to provide information before you can fulfil a reward.
What a Cloudbot Loyalty Store Is
Streamlabs describes the store as a place where viewers can spend points to redeem sound effects, perks or access codes. In practice, the store connects a point balance to a reward you have configured. The points do not represent money, and a redemption is not a payment to you.
Cloudbot is the Streamlabs tool that manages the loyalty settings and store items. You choose how viewers earn points, what each item costs, and the conditions attached to it. A sound can play through an alert box; an access code can be distributed according to the code settings; a perk may need you to take an action yourself. Those are different fulfilment paths, so choose the reward format with your capacity in mind.
The Streamlabs guides describe a digital workflow. The documented item types do not require you to keep physical stock, and you do not need streaming hardware just to create a store. A social follow, for example, may be offered as a Stream Perk, but it is still your responsibility to define what the perk means and to do the work behind it.
A store can add an interactive element to a continuous channel, but it cannot fix an unclear channel promise. If your audience joins a devotional stream to listen quietly, a loud sound redemption may be a poor fit even if the feature works. For a calm station, a low-key acknowledgement or a useful access code may fit better. Decide what serves the people who watch before you add an item.
If your channel is built around a steady visual and a repeating programme, first make sure the stream itself is understandable to a new visitor. The guide to setting up a 24/7 stream with a static image between videos covers one way to keep the viewing experience coherent; the loyalty store is an extra layer, not a substitute for that foundation.
Enable Cloudbot Loyalty
Cloudbot has to be enabled before its loyalty store can be configured. In Streamlabs, open the Cloudbot area and enable Cloudbot if it is not already active. Then choose Loyalty in the left navigation and switch on the Enable Loyalty System control. Interface labels can change, so if the screen differs, consult Streamlabs’ current Quick Guide to Setting Up Cloudbot, which describes the sequence and the loyalty controls.
Once loyalty is on, decide what viewers call the points. Streamlabs allows a custom point name, which is useful if a generic label would feel out of place in your channel. Pick something short enough to appear clearly in chat and in a store listing. Avoid a name that could be mistaken for a rupee amount, a donation balance or a promise of credit.
Next consider how viewers earn points. The loyalty settings let you choose point earnings for activities and block specific users from earning. Set the activity rules deliberately: viewers should be able to understand what earns points, and the system should not reward behaviour you do not want in chat. If you moderate a channel with a small team, keep the rules simple enough that you can explain them without sending viewers through a long policy.
Do not add an item before you have decided whether the point balance and the proposed reward make sense together. A high cost can make an item effectively unreachable for a new viewer; an overly low cost may create more redemptions than you can handle. There is no universal cost that suits a bhajan audience, study stream and local news loop equally. Think about the pace of your own chat and the time or inventory each reward consumes.
Open the Store and Add an Item
With Cloudbot and loyalty enabled, select Loyalty and open the Store settings. Choose Add Your First Item. Streamlabs’ Loyalty Store setup guide walks through the item fields and redemption choices. Read it alongside the screen you see, because the guide is the primary reference for the documented options and interface names may shift.
Start with one item rather than filling the store at once. A single, well-described reward is easier to test: you can check how the listing reads, what information it asks for, and what happens when a viewer redeems it. Give the item a name that says what the viewer receives, not only an inside joke that newcomers may not understand. In the description, explain the reward, any limits that matter, and whether you will need to follow up after redemption.
The item setup includes a loyalty cost, quantity and cooldown. Treat them as separate controls. Cost determines how many points a viewer spends. Quantity can constrain how many are available. Cooldown controls how often the item can be redeemed. A low quantity may suit a one-off access code; a longer cooldown may help keep a frequently used sound from interrupting a programme. Match the settings to the actual reward rather than selecting values by habit.
The item can also include content such as a thumbnail. A clear image can help viewers distinguish rewards, but it should not imply a benefit the item does not provide. If you offer a Stream Perk that requires coordination, say that plainly in the description rather than relying on a picture or short title to explain it.
Before saving, read the listing as if you had never visited the channel. Can a viewer tell what the reward is, what it costs, whether it is limited, and how to claim it? If not, revise the text or settings first. A short test with a moderator or trusted viewer can reveal ambiguity, but do not ask someone to redeem a scarce item unless you have accounted for that redemption in the quantity.
Choose a Reward Type
Streamlabs documents three store item types: Access Code, Sound Effect and Stream Perk. They are not interchangeable labels for the same reward. The right one depends on how the viewer receives the benefit and how much manual work is involved.
| Reward type | What it is for | Fulfilment consideration |
|---|---|---|
| Access Code | A game key, gift code or similar code | You supply codes and configure how they are distributed on redemption |
| Sound Effect | A sound a viewer can redeem | The sound plays through the alert box; choose a file and volume that suit the channel |
| Stream Perk | A perk outside the code and sound categories | Define the action clearly; you may need to deliver it yourself |
Access Code
Choose Access Code when the reward itself is a code, such as a game key or gift code. You need to supply the codes and decide how code distribution should work in the item settings. Because the code is the reward, check that the available quantity reflects what you actually have. Do not advertise a code as guaranteed for every viewer if you have only configured a limited number.
An access code is not a general-purpose payment feature. It is a way to distribute a supplied code in exchange for points. Before listing it, make sure the description identifies what the code is for and any relevant redemption conditions. If the code has a region, expiry or account restriction, explain that accurately rather than expecting a viewer to discover it after claiming.
Sound Effect
Choose Sound Effect when a viewer should trigger a sound through the alert box. The item setup can use an uploaded sound file. Keep the choice appropriate to the stream: a sudden loud effect can be disruptive in a meditation or study broadcast, while a brief recognisable cue may suit an interactive entertainment channel. Listen to the file in the context of the programme before making it available.
A sound reward is closer to an on-stream event than a private message or an item you hand over later. Consider when the channel is live and who else may be listening. The item name and description should set expectations that redeeming it produces a sound, rather than implying a personalised service or a cash-equivalent benefit.
Stream Perk
Choose Stream Perk for a reward that is not an access code or a sound. Streamlabs gives following a viewer on social platforms as an example. Since a perk can involve your own action, state exactly what you will do and any boundary that affects delivery. “A social follow” is clearer than “special treatment”; a viewer should not have to guess whether the perk means a follow, a mention or something else.
This type needs the most attention to fulfilment. If you have to find a viewer’s account, decide how to contact them, or complete the action later, explain that in the listing and collect only the information you actually need. A small business might offer a defined acknowledgement or channel-related benefit, but should avoid suggesting a discount or product unless that is genuinely part of the reward and can be honoured.
Set the Cost and Reward Details
Set the loyalty cost after you have estimated the effort or supply involved. For a sound that can be triggered repeatedly, the main concern may be how often it interrupts the programme. For an access code, the number of codes on hand matters. For a Stream Perk, the cost should reflect the time you can set aside to fulfil it. Points are a channel-defined measure, so there is no conversion into money to calculate.
Use quantity to represent actual availability, not hoped-for availability. If you have a handful of codes, set a quantity that does not exceed the supply you are willing to distribute. If a perk depends on your personal time, limit the number to a pace you can meet. If the reward can be repeated without consuming inventory, a quantity limit may not be the main control; the cooldown may be more useful for spacing redemptions.
Cooldown and quantity solve different problems. A cooldown can stop the same item being claimed too frequently under the configured rules, while quantity limits overall availability. Neither setting explains the reward on its own. Put limits in the description as well when they affect a viewer’s decision, so a person does not spend points on an expectation that the listing never stated.
For rewards requiring viewer information, use the requirement fields to request only what is necessary. A code may need no personal details at all. A social perk may need a username or a way to identify the account, but avoid asking viewers to put sensitive information in public chat. Streamlabs notes that items with two or more requirement fields cannot be redeemed in chat, so the redemption route should be chosen before you publish the item.
You can add a thumbnail and, where applicable, content such as the sound file or access codes. Review these assets and details together. The visible listing, redemption form and actual fulfilment should describe the same thing. If a viewer sees “one sound” in the listing, the configured alert should not trigger a different or unexpectedly long effect.
Plan How to Fulfill Redemptions
A reward is only useful if you know what happens after a viewer claims it. For an Access Code, decide whether the configured distribution will send a supplied code automatically and make sure you have entered the intended codes. Streamlabs documents automatic distribution for supplied codes, but that does not mean every store reward is fulfilled automatically. Check the item’s settings and test the specific path you intend to use.
For a Sound Effect, confirm the right file is attached and the alert box is configured to play it. Streamlabs also describes optional redemption alerts. If you use one, keep its wording and sound consistent with the channel. A quiet devotional stream may need a restrained alert, while a news loop may need redemptions to stay unobtrusive so the content remains easy to follow.
For a Stream Perk, write down your own fulfilment steps. For example, if the reward is following a viewer’s social account, you need a clear account identifier, a way to locate it, and a point at which you will complete the action. Do not imply that Cloudbot performs an action that you have to carry out yourself. If you cannot comfortably fulfil the perk during a busy stream, explain when the viewer should expect you to do it, without promising a time you cannot keep.
Redemption alerts and requirement fields can reduce confusion, but they do not replace a workable process. Decide who checks redemptions, where you will see them, and how you will mark a manual task as complete. If a channel is run by several people, agree who owns the follow-up so two moderators do not both attempt the same perk or no one notices it.
For a reward that needs information, Streamlabs recommends keeping it off chat redemption and using the tip page. In its Loyalty Store guide, Streamlabs says: “We highly recommend making items that have requirements not redeemable through chat and only allow them to be redeemed through the tip page.” The practical reason is straightforward: chat is a poor place to collect multiple fields, and two or more requirement fields prevent chat redemption according to the guide. Keep account details and other identifying information out of public chat.
The broader programme still needs to fit the channel. If rewards are tied to a recurring event or giveaway, make the terms easy to understand and separate the point store from any cash donation or merch promotion. A livestream merch giveaway guide may help when you are planning a separate physical prize; the Cloudbot store’s documented formats remain codes, sounds and perks.
Explain Redemption to Viewers
A store listing is not enough if viewers do not know where to find it. Explain the point name, how points are earned, what each item provides, and whether a redemption happens in chat or through your Streamlabs Cloudbot tip page. The Streamlabs guide describes both redemption routes: viewers can type .redeem <keyword> in chat or use the creator’s Cloudbot tip page after signing in.
For a chat redemption, publish a short keyword that is easy to type and unambiguous. Tell viewers the exact command format and whether the item has a quantity or cooldown limit. For example, “Type .redeem rain-sound in chat to play the rain sound; one redemption is available at a time” is more useful than “Redeem your points for a surprise”. Keep the example aligned with the item’s actual keyword and settings.
For a tip-page redemption, give viewers a direct route from the channel description or a pinned message, and explain that they may need to sign in. If the item asks for details, say what information is needed and why. Do not ask for personal details in chat, and do not promise that the redemption will be instant if you still need to review a request or perform a manual task.
Use the same plain language in the listing, pinned chat message and channel description. If an item is limited, say so. If a Stream Perk will be completed later, say that it is a creator-provided action. If the store uses points, call them points consistently; do not describe a reward as a purchase, refund, payout or cash value. This is especially important for a local business channel, where viewers may reasonably confuse a loyalty item with a commercial offer.
If you run an always-on YouTube stream, consider what viewers see when they arrive in the middle of a programme. A concise pinned explanation can help without interrupting the content. For a radio-style station, the advice on making a static-image radio stream on YouTube can inform the visual presentation, while a store note can remain separate from the listening experience.
Review the wording after the first redemptions. If viewers repeatedly ask whether a sound is public, how long a perk takes, or whether a code is available, that is evidence the listing needs clarification. Do not solve unclear copy by adding more rules than the reward requires; answer the specific question in the item description and keep the published command or tip-page route current.
Once the store and channel are ready, compare operating choices against how much attention you want to give the stream day to day.
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
Do Cloudbot loyalty points have cash value?
No. The store uses points as a channel reward balance for the items you configure; the documented setup does not make those points cash or a payment. Explain them as points, and keep any separate donation or business transaction distinct.
Can viewers redeem every item in chat?
No. Viewers can use .redeem <keyword> for chat redemptions, but Streamlabs says items with two or more requirement fields cannot be redeemed in chat. For an item that needs viewer information, direct people to the Cloudbot tip page instead.
Does Cloudbot fulfil every reward automatically?
No. Supplied Access Codes can be distributed automatically when configured, and Sound Effects are played through the alert box, but a Stream Perk may require you to act. Check each item’s settings and explain any manual follow-up before viewers spend points.
Which reward type should I add first?
Choose the type you can describe and fulfil most clearly: an Access Code if you have codes to distribute, a Sound Effect if it suits the channel, or a Stream Perk if you can reliably complete the action. Start with one item, check its cost, quantity, cooldown and redemption route, then add more only if the first one works for your audience.