Test your alerts before going live

A few minutes of checks before you go live saves you from a silent or missing alert in front of your audience. Work through this list in order.

1. Check the design with test events

1. Open Creator workspace → Studio and open the scene you will stream with.
2. Select the Tip alert widget.
3. Under Test events, select a tip button.
4. Watch the alert play on the canvas in the editor.

The buttons test different cases:

• The standard tip shows a normal alert.
• Large tip shows how a bigger tip looks.
• Flagged message shows how a message with rude words looks, including whether your profanity filter hides them.

Test events are preview only. They play in the editor, not in OBS, and they do not count toward your goals, totals, or leaderboard.

2. Test subscriber alerts

If your scene has a Twitch or Kick subscriber alert, select that widget. Under Test subscription activity, pick the Provider, then fire a new subscription, a renewal, or gift subscriptions.

You can only test a provider that is connected. If you see Connect a broadcaster account before testing subscription alerts, see Connect Twitch and Kick for subscriber alerts.

3. Check sound and text to speech

1. In the tip alert's properties, check Alert sound is not set to No sound, and Alert volume is above 0.
2. In the editor, select Enable sound. Browsers block sound until you allow it, but OBS does not need this.
3. Fire a test tip. If Read tips aloud is on, you should hear the alert sound first, then the tip read aloud.

If the read fails, see Read tips aloud with text to speech.

4. Publish your changes

Select Publish changes. OBS only shows what is published, so anything you changed but did not publish will not appear on stream.

5. Check OBS is connected

1. In OBS, make sure the WeTip browser source is in your live scene and is visible.
2. In the studio editor, check that Renderer reads live. That means the scene's private URL is open somewhere, such as your OBS source, and ready for alerts.
3. If it reads inactive, nothing has the scene open, so OBS is not connected. Check the browser source URL matches the scene's Copy URL link, then refresh the source in OBS.

For setup help, see Connect WeTip to OBS.

6. Check OBS audio

In the OBS Audio Mixer, find the WeTip browser source and make sure it is not muted. If you do not see it, open the browser source's properties and turn on Control audio via OBS.

7. Check your goals and tip page

• If you show a goal, check it is active and that the Goal widget shows the right goal.
• For a goal that resets every stream, select Start a new cycle so it starts from zero.
• Open your public tip page and check your suggested amounts and goal look right.

See Set and track goals.

Checklist

• Tip alert looks right in a test event.
• Sound and text to speech play in the editor.
• Changes are published.
• Renderer reads live while OBS is open.
• WeTip source is not muted in OBS.
• Goals are active and reset for this stream.

Related

• Connect WeTip to OBS
• Choose a studio scene type
• Manage tip messages