How To Set Up Donation And Sub Alerts

Configure donation and subscription alerts so they stay readable, stable, and easy to test before each stream.

A practical workflow for donation and subscription alerts: style, audio, sequence testing, queueing, and common conflicts.

alerty donacji

how-to

How donation and subscription alerts differ

A donation alert usually needs amount, message, and goal context. A subscription or follow alert mostly reinforces community momentum. If both look identical, viewers lose context quickly.

Start with one shared brand style, but separate priorities: donations can use stronger audio and a clearer amount, while subscriptions can be shorter and calmer.

The goal is not to make every alert a show. The goal is fast feedback that helps the streamer react without interrupting chat flow.

Setup sequence for donations and subscriptions

Enable the donation alert first because it is closest to monetization and easy to validate with a test payload. Then add subscriptions, follows, or other community events.

For donations, show name, amount, and a short message. For subscriptions, show name, event type, and months if relevant. Do not overload one template with every field.

After each change, run one single-event test and one sequence test: donation, subscription after 30 seconds, then repeat both.

Audio, color, and display duration

A donation can have a stronger signal, but it still needs to sit inside the audio mix. A subscription alert can be shorter and calmer, especially on active channels.

Colors should separate event type, not redesign the whole layout. A different accent, icon, or title strip is usually enough.

Start with four to five seconds for donations and three seconds for subscriptions or follows. If alerts overlap, shorten duration or enable a queue.

Pre-live test flow

Trigger a donation and confirm that the panel, OBS, and scene show the same event. Then trigger a subscription and confirm that the visual difference is obvious.

Repeat both events after 30 seconds. If the alert freezes, lingers, or clips audio, the issue is usually duration, queueing, or duplicate sources.

Switch OBS scenes at the end. The alert should remain in a safe visual zone and should not disappear just because the streamer changed scenes.

Common conflicts and fixes

If donations and subscriptions mix colors or icons, separate the event template and keep only the core style shared: font, frame, and animation rhythm.

If the alert counter does not reset or shows old text, check Browser Source cache and event order. Refreshing the URL and removing duplicate scene sources often fixes it.

If the alert loop is too long, set a maximum display duration and remove exit animations with heavy delay.

When to expand alert variants

Expand alerts only after the basic set works reliably for several streams. Otherwise it is easy to confuse technical problems with creative ones.

Add a second variant when viewers react to alerts but the streamer needs clearer separation for amounts, subscription tiers, or special campaigns.

Save changes as presets. One production preset, one test preset, and one emergency preset provide more control than manual edits before every stream.

Questions fréquentes

Should donation and subscription alerts look the same?

They should share the same brand style, but differ by accent, sound, or duration. A donation needs amount and context; a subscription usually needs shorter community feedback.

How should you test donation and subscription alerts before going live?

Trigger a donation, then a subscription, wait 30 seconds, and repeat both. Check order, audio, scene visibility, and duplicate firing.

When is it worth adding a second alert variant?

Only after the basic setup has worked reliably for several streams. Then a second variant can separate donation amount, subscription tier, or a special campaign.

Hypr.stream

Run the stack behind this playbook.

Alerts, donations, overlays, and live operations in one creator control room.

Rejoindre la bêta
How To Set Up Donation And Sub Alerts | hypr.stream