Twitch alerts

Follows, subs, gift subs, resubs, bits, raids, and channel point redemptions - configured per overlay, announced in chat by the bot.

Twitch alerts are configured per overlay: open an overlay in the overlay editor, select the Alert box widget, and its inspector decides which events pop an alert on that overlay, which get read aloud, the wording and sound each event uses, the alert volume, the minimum bits for cheers and minimum viewers for raids, and the tip sound effect. Two overlays can behave completely differently - follows on your main scene, subs-only on a minimal one, a higher bits threshold on another.

The bot’s chat messages for the same events live separately, on the Chat bot page - an event can be announced in chat without showing on an overlay, and vice versa.

Supported events

A subscriber coming back - a lapsed sub, or a Prime sub renewing (Prime has to be re-upped every month) - who shares their resub is one Resub alert, not a Sub and then a Resub. Twitch sends the payment and the share as two separate events and never says which subs are returns, so TipPage uses its own memory of the channel: a viewer it has seen subscribe before (an earlier sub alert, the subscriber badge in chat, a sub-reward credit, a sign-in as a subscriber) is a returning sub, and their alert is the share, the moment they press it. A first sub plays the moment it happens. Nothing is ever held back. A returning sub who never shares gets no alert - the same as Twitch’s own chat, which shows nothing for an unshared resub; their sub-reward credit still lands at payment. Someone whose last sub was before the channel joined TipPage reads as new the first time.

Kick

If your Kick channel is connected (Settings -> Platforms), Kick events use the same rows: a Kick follow is a Follow alert, a Kick sub a Sub alert, a gifted Kick sub a Gift sub, a renewal a Resub - same wording, sound, GIF and colour as the Twitch version, and the alert shows the viewer’s Kick avatar. Kick subs have no tiers, so {tier} is always 1. Cheers, raids and channel points are Twitch-only; Kicks (Kick’s paid gift) is Kick-only and behaves like a cheer: its own row, message block, sound, and a Minimum Kicks threshold.

Each row shows the platform logos it applies to. Under Platforms (shown once a Kick channel is connected) you can turn Twitch or Kick events off for this alert box - so one overlay can run a Twitch box and a Kick box side by side - and switch on a platform badge, which puts the platform’s logo in front of every alert.

Alerts render through the Alert box widget, using the same style, animation, and font as your tip alerts. Out of the box each event keeps its classic tint - subs in Twitch purple, bits in gold, raids in red - and every colour is yours to change.

Per-overlay settings

In the Alert box widget’s inspector:

• Alert events - one row per event with an Alert toggle (show it on this overlay) and a TTS toggle (read it aloud on this overlay). Expand a row to customise that event:
  • Alert wording - your own headline, with variables like {user}, {tier}, {bits}, {viewers} (gift subs also get {recipients} - placing it in your wording replaces the automatic recipient list). {user} just followed, they are a real one! shows on stream exactly like that, and TTS speaks it too. Blank keeps the built-in wording.
  • Spoken wording (TTS) - optionally different text for the voice than the screen. Blank speaks the alert wording.
  • Show / read the viewer’s message - two independent toggles for the viewer’s own text (cheer or resub message, channel-point input, gift-sub recipient list): show it on the overlay, and read it aloud. Turn one off without the other - e.g. TTS speaks the message while the overlay shows just your headline.
  • Sound - the default chime, no sound, or any sound from your library, per event. A follow can chime while a raid plays an air horn.
  • Highlight colour - the colour of that event’s numbers (tier, bits, viewer count) in the headline.
• Twitch alert colours (under the widget’s appearance) - the viewer-name colour and the headline text colour, shared by all Twitch alerts.
• Volume (near the top of the widget’s settings) - three sliders, per overlay: Voice (TTS) is how loud every spoken line plays, alerts included; Alert sounds is the chime or sound picked for each event; Tip sound is the tip sound effect.
• Voice - the voice every spoken line on this overlay uses, alerts included, with its speed and pitch. Each overlay can speak in a different voice - see TTS.
• Minimum bits (in the Cheer event’s panel) - cheers below this don’t alert on this overlay. Stops the 1-bit spam; each overlay can set its own bar.
• Minimum viewers (in the Raid event’s panel) - raids bringing fewer viewers than this don’t alert on this overlay. 0 (the default) alerts for every raid.
• Minimum Kicks (in the Kicks event’s panel) - Kicks gifts below this amount don’t alert on this overlay. 0 (the default) alerts for every gift.
• Which rewards (in the Channel points event’s panel) - see below.
• Tip sound - whether tips play a sound on this overlay, which sound, and how loud. Sounds are uploaded once (here or on the TTS page) and shared across all your overlays.
• Timing - whether an alert plays straight away or in order with the tips, and how far back the overlay replays the alerts it missed when it connects. See Timing.

New overlays start from your defaults; saving an overlay in the editor pins its own copy of these settings.

Timing

Two settings in the Timing group decide when an alert plays, per overlay. Both start the way every alert box has always worked, so nothing changes until you change it.

Alerts and tips. A sub, a raid or a cheer and a paid tip can be waiting at the same time. Straight away (the default) plays the alert as soon as the tip on screen finishes, ahead of whatever is waiting in the tip queue - a raid never sits behind ten tips. In order plays everything in the order it happened: an alert comes after the tips that were queued before it and before the ones queued after, so the stream replays the evening as it was. With a long tip queue an alert waits its turn. A Replay pressed on the TTS page counts from the moment you press it. In linked mode the same rule runs against the TTS + media units, and an overlay whose alert box doesn’t play tips still keeps to the tip queue’s order.

Missed alerts. When the overlay connects - OBS opened, the scene reloaded, the browser source refreshed - it plays the subs, gift subs, cheers, raids and Kicks that happened while it was closed, back as far as you choose: the last 4 hours by default, anything from 15 minutes to 7 days, or Don’t replay missed alerts for live alerts only. Follows are never replayed. A Replay pressed on the TTS page while no overlay was open always plays on the next connect, whatever this is set to. An event your box filters out (a type that is off, a cheer under its minimum) is never replayed either.

Channel points

Channel points are the one event that starts off. Every other alert type is on by default, but a channel usually has a dozen cheap rewards and an alert for each redemption gets old fast - so you turn the Channel points row on yourself, on the overlays you want it on.

Once it’s on, the row’s panel has a Which rewards switch:

• All rewards - every redemption alerts.
• Only chosen - tick the specific rewards from your channel. The list is pulled live from Twitch, so it’s the rewards you actually have.

Picking rewards stores their Twitch ids, not their names: rename a reward on Twitch and it stays selected. Delete one and it just stops matching - the editor shows you any leftovers so you can clear them.

Each overlay decides separately. A gameplay overlay can alert on every redemption while your chatting overlay stays quiet, or one box can be narrowed to the two rewards that are worth interrupting the stream for.

This has nothing to do with the Channel Points page - that’s for what a redemption does (credits, a bot message, a song request, reading the text aloud). Whether it shows on screen is the alert box’s job, exactly like a follow or a cheer. One overlap: a reward with Read it aloud speaks the viewer’s text itself, so the alert box shows that redemption without reading it again.

Replaying an alert

Every alert that played on stream is kept in the History panel on the TTS page, between the tips, in the order it happened (one cut short from Controls says Skipped). Press Replay to play it again on your alert box - the same wording, sound and voice as the first time, with a gold “(Replay)” badge so chat knows it’s a rerun.

A replay goes through the alert box like a live event, so the overlay you have open decides. If its alert box has that kind of alert switched off (or the cheer is under its bits minimum), the dashboard tells you rather than replaying into nothing. No overlay open? The replay waits, plays when one connects, and shows in the history then. Replays never count twice - no sub-reward credit, no goal or label bump, no chat announcement, no webhook.

If some events aren’t firing

Twitch alerts need permissions from your Twitch account, granted when you signed up. Two common cases:

• A “Reconnect Twitch” banner in the dashboard - Twitch permissions have changed or expired since you signed up. Click it, re-authorise, and everything resumes.
• Channel point alerts need Affiliate or Partner - channel points don’t exist on other channels, so there’s nothing to fire.

Everything working? Send some test alerts and watch them play.