Twitch Bits alerts follow a multi-step path. An alert displayed in the Extension, the confirmation Twitch shows to a viewer, and an alert seen in the broadcast are separate checkpoints. Keeping them distinct helps you explain the experience and check your setup.
Stream Soundboard lets Twitch viewers trigger sound and video alerts that you configure. Alerts offered through the Twitch Extension can have a Bits amount and use Twitch’s Bits transaction flow.
For the broader installation context, see our Twitch soundboard guide.
The two-sided flow: viewer actions and streamer checks
Use this table as a pre-stream reference. The left column follows the viewer’s visible journey; the right column covers the settings and checks on your side.
| Step | What the viewer sees or does | What you configure or verify |
|---|---|---|
| 1. Availability | They may see alerts offered in the Extension when they are available for the channel. | Choose the sound and video alerts you want to offer and, where relevant, set a Bits amount. |
| 2. Selection | They select an alert from the visible options. | Check that the list matches the alerts you intend viewers to access. |
| 3. Twitch confirmation | Twitch shows a confirmation of the Bits amount before completion. The viewer can proceed or cancel. | Treat confirmation as a separate stage from alert selection. |
| 4. Completion and live observation | If they proceed and Twitch completes the exchange, the interaction tied to the configured alert may be triggered. | Observe whether the selected alert appears in the stream. |
| 5. Unavailable state | They may not see an expected alert, may not reach confirmation, or may cancel. | Record the last observable stage before changing settings. |
Eligibility and configuration
Start by defining the experience you want viewers to have. List your sound and video alerts, then identify the ones you want to associate with a Bits amount. Check that the viewer options displayed in the Extension match that plan.
Do not describe Bits as automatically available on every channel. Twitch’s Extensions monetization documentation says that Bits-in-Extensions features depend on channel eligibility and configuration. Check your channel’s current configuration before telling viewers that a specific alert is available with Bits.
Keep a short configuration record:
- List the sound and video alerts you plan to offer.
- Mark the alerts you want to associate with a Bits amount.
- Check the options visible to viewers.
- Check channel eligibility and the current Extension configuration.
- Record the planned Bits amount for each relevant alert.
The wording you use matters as well. Twitch allows Bits to activate permitted experiences in an Extension, while its Extensions Guidelines and Policies state that Bits in Extensions must not be described as a donation or as Cheering. In stream copy and viewer instructions, use terms such as “configured alert,” “Bits amount,” and “Twitch confirmation.”
Viewer selection and Twitch confirmation
The viewer starts by choosing an alert from the available options. That selection identifies the configured experience they want to activate; it is not yet confirmation of the Bits amount.
Before completing the exchange of Bits for the configured Extension experience, Twitch shows the viewer a confirmation. The amount displayed in that confirmation is the point the viewer can review before deciding whether to proceed or cancel.
For a general walkthrough of using a soundboard from the viewer’s side, link viewers to our Twitch soundboard viewer guide. The Bits-specific step in this guide is Twitch’s confirmation of the amount.
You can explain the flow to viewers in four steps:
- Find an available alert in the Extension.
- Select the alert you want to activate.
- Review the confirmation showing the Bits amount in Twitch.
- Proceed or cancel the transaction flow.
Transaction completion and alert delivery
If a viewer proceeds after confirmation and Twitch completes the Bits transaction, the interaction associated with that configured alert may be triggered. Your job is to prepare the alert and then check what appears in the live broadcast.
During a validation run, note the selected alert, whether the viewer saw Twitch’s confirmation, and what is visible in the stream. Those details make it possible to repeat the check or describe the observed difference precisely.
An alert not seen in the stream does not, by itself, establish a cause. The documented information here covers eligibility, configuration, confirmation, and cancellation; it does not define a playback time or delivery guarantee. Keep your record focused on the stages you and the viewer can observe.
Cancellation and unavailable-state handling
A viewer can cancel the Bits transaction flow, as Twitch notes in its Extensions monetization documentation. Cancellation is a normal outcome of the flow and should not be treated as completion.
An unavailable state can occur earlier in the visible path. The viewer may not see an expected alert, or may not get as far as the confirmation screen. In either case, identify the visible stage instead of guessing at a reason.
Use this record when something does not appear as expected:
- The alert is not visible: note the alert the viewer was looking for and any other options they can see.
- The alert is visible, but no confirmation appears: note the selected alert and where the on-screen flow stops.
- Confirmation appears and the viewer cancels: record the cancellation; do not infer completion.
- Confirmation is observed, but no alert is seen live: record the time and the visible details on both sides without assigning a technical cause.
This approach gives you a precise record instead of a vague diagnosis while you are live.
Pre-live validation steps
Run a check with a test viewer before introducing the alerts to the full chat. The goal is to confirm what is visible in the current setup.
- Check that the planned sound and video alerts are the ones you intend to offer.
- Note the configured Bits amount for every relevant alert.
- Confirm that Bits availability matches the channel’s eligibility and current Extension configuration.
- Ask the test viewer to find the Extension and identify the alerts they can see.
- Have them select an alert and check whether Twitch displays a confirmation showing the Bits amount.
- Confirm that the viewer can cancel the flow before completion.
- If the flow is available and you proceed with the test, simply observe whether the selected alert appears in the live broadcast.
- Record the tested alert, the amount shown at confirmation, the time, and what the viewer and streamer observed.
This record shows whether the test stopped before confirmation, ended with cancellation, or reached live observation. It gives you a clear way to explain Twitch Bits alerts without merging distinct stages of the viewer flow.