Why Most Channel Point Redeems Get Ignored

You set up twelve channel point redeems when you hit Affiliate. The Hydrate reminder, the song-skip, the “make me drink water,” a couple of sound effects you saw on a streamer you watch. You priced them, named them, hit save, went live.

A month later, three of them get used. The Hydrate fires every stream. Skip Song gets spammed. Pet Cam gets one redemption from the same regular every week. The other nine sit at zero.

You don’t know if those nine are bad ideas. Maybe nobody saw them. Maybe they’re priced wrong. Maybe the sound effect on the “Wrong Answer” buzzer was perfect for the trivia stream you ran once and useless during your usual Stardew runs. You’d remove some of them, but you suspect one of them is a regular’s favorite they only redeem once a month, and removing the wrong one would burn a viewer’s attachment to your channel.

If you’ve Googled this, you’ve seen the answer everyone gives. Most channel-point content treats this as an idea problem. Open up any “Twitch channel point ideas” listicle and you get twelve more redeems to add to the list of dead ones. That’s not what’s happening.

A redeem dies for one of two reasons, and they’re completely different problems with completely different fixes.

The two reasons redeems die

Discovery. Viewers don’t know it exists. Twitch’s channel-point menu is a flat list. New viewers don’t open it. Even regulars often only know about the redeems that fired in front of them once. The redeem that’s eight items down nobody scrolls past has zero chance.

Design. Viewers see it and skip it. It costs more than they think it’s worth. It doesn’t trigger anything visible. It requires text input nobody wants to write. It plays a sound that’s only funny in a context the streamer isn’t currently in.

Every dead redeem in your list is dying for one or the other of these reasons. Across the streams I’ve watched and the threads I’ve read, discovery is the more common one. Most “dead” redeems weren’t bad ideas. Viewers just never saw them.

The rest of this post is split into three parts. First, a way to figure out which of your redeems are actually dying, because the data isn’t anywhere obvious. Second, four design principles for redeems that don’t sit at zero. Third, the five real options for surfacing your redeems to viewers, ordered by how much of the discovery problem they actually solve.

Figuring out which redeems are actually dying

Twitch doesn’t show you any of this data. There’s no analytics tab for channel points. The redemption queue tells you what’s happening live, but it doesn’t keep history. Once you mark a redemption complete, it’s gone from the dashboard.

I covered why the data doesn’t exist in What Twitch Doesn’t Tell You About Your Channel Point Rewards. The short version: Twitch built channel points as an engagement feature and didn’t ship analytics alongside it. The Twitch API gives third-party tools roughly seven days of fulfilled redemption history, and that’s it.

Three ways to find out which of your redeems are dying, ordered by effort.

Manual queue counting

Free, tedious, works. Before you clear your redemption queue at the end of each stream, spend two minutes counting. A simple spreadsheet:

Date	Stream length	Redeem	Count	Notes
Mar 3	3.5h	Hydrate	12	Fired throughout
Mar 3	3.5h	Skip Song	7	Same viewer 4 of 7
Mar 3	3.5h	Pet Cam	0
Mar 3	3.5h	Buzzer	0

After four to six sessions, the dead redeems are obvious. They’re the rows with zeros across.

The signal framework for what to do with that data is in How to Price Your Channel Point Rewards. Read that for the four signals worth watching: redemption frequency, unique redeemers, usage over time, dead rewards.

Live observation patterns

While you’re streaming, watch for three things:

Spam patterns. One viewer hitting the same redeem ten times. That’s a pricing or cooldown problem, not a design problem. The redeem works, the constraints don’t.

Silence on a redeem fire. A redeem fires and chat doesn’t react. That’s design feedback. The trigger isn’t visible enough to know it happened, or it isn’t interesting enough to comment on.

Same-viewer concentration. Three viewers redeem everything, the rest of chat redeems nothing. That’s not a redeem problem, that’s an engagement-spread problem. Different fix entirely.

Tool-based tracking

If you don’t want to count manually, three options surface the data automatically:

• BetterStreams logs every redemption to your dashboard. Most popular redeems, total points spent, unique redeemers, and trends over time. The data starts the moment you connect.
• Streamer.bot can capture redemption events through its trigger system and route them to file or webhook. You’d build the logging chain yourself, but it’s flexible.
• Mix It Up tracks basic stats with export, including channel point activity.

How to pick: if you want zero setup, BetterStreams is configured in two clicks and the analytics view is built in. If you already run Streamer.bot, build the logging chain yourself; you’ll learn the action system in the process. If you’re on Mix It Up, the export is enough to do post-stream analysis in a spreadsheet.

All three start from connection date. None of them can backfill last month. The sooner you hook one up, the longer your history will be when you go to make decisions.

Pick one method. Manual is fine if you don’t have anything else. Four sessions of counting is enough to see which redeems are dying.

What makes a redeem actually engage

Once you know which redeems are dying, you have to fix them or replace them. The redeems viewers actually use share four things. None of these are ideas. They’re properties.

Visible feedback

When the redeem fires, the viewer sees something happen. A sound effect. A scene change. A specific overlay. A chat message that mentions them by name. The “did anything happen?” silence is what kills repeat use.

A redeem that mutes your mic for five seconds is invisible. A redeem that mutes your mic for five seconds and plays a comically loud “shhh” sound is a redeem viewers will spam.

If a redeem doesn’t have a visible trigger, add one. Even something cheap: a chat message saying “@viewer just redeemed Pet Cam, here we go.” Acknowledgment is feedback. Silence is a dead loop.

Worth the time-to-earn

Channel points come from watching. Roughly 320 per hour for non-subs, more for subs and active chatters. The pricing post covers the math in detail.

A 5,000-point redeem requires fifteen-plus hours of watching. If the payoff is “I get to see your face cam for thirty seconds,” nobody’s earning that. The cost has to match what the redeem actually delivers.

Cheap redeems get used. Expensive redeems need a reason. A 50,000-point redeem that lets the viewer pick the next game category for the night earns the cost. There’s a real payoff for the viewer who waited for it. A 50,000-point redeem that plays a sound effect is dead before you publish it.

Match the cost to the act of waiting, not to how cool you think the redeem is.

Context-aware

A horror jumpscare redeem is dead during a chill art stream. A “play wrong-game music” redeem is irrelevant outside specific games. A “make me drink water” reminder doesn’t fit a quick variety night where you’re going to be in the BRB scene half the time anyway.

The fix isn’t to delete those redeems. The fix is to enable them only when the context matches.

Most channel-point automation tools handle this. In Streamer.bot, you’d group redeems and use a Stream Update trigger that fires when your category changes; the trigger toggles the right group on and the others off. In Mix It Up, the channel-point command system lets you enable and disable redeems through the action chain on category change. In Firebot, trigger conditions on the redemption event filter by current game category. In BetterStreams, reward profiles (“RewardSets”) group redeems by context and auto-toggle entire sets based on conditions like stream category, OBS scene, or time of day.

Either way: the dead-during-the-wrong-game problem isn’t a redeem-design problem. It’s a configuration problem. Fix it once and forget it.

Discoverable

The fourth thing every working redeem has is that viewers can actually find it. A redeem can hit visible feedback, fair pricing, and context-aware activation, and still die if nobody ever sees it.

Where viewers actually find your redeems

Most streamers’ redeems live in one place: the Twitch native channel-point menu. That menu is a flat list, has no descriptions, and viewers don’t open it unless they already know there’s something they want.

Five real options for surfacing your redeems to viewers, ordered roughly by visibility.

Option 1: Twitch’s native channel-point menu

What it is: built into every Twitch chat. Viewers click the channel-points icon next to the chat input to see the list.

Strengths: zero setup. Comes free with Affiliate. Every Twitch viewer technically has access.

Weaknesses: flat list. No descriptions, no images, no categorization. Viewers have to know to look. New viewers usually don’t. Long lists scroll off-screen and get ignored.

When it’s enough: small redeem lists with self-explanatory names. If you have five redeems and they’re all named clearly, the native menu does the job.

Option 2: !commands chat command

What it is: a chat command set up in Nightbot, StreamElements, MixItUp, or Firebot that posts a list of available redeems and chat commands when typed.

Strengths: discoverable to anyone reading chat. Lets you include descriptions. Free.

Weaknesses: recursive. Viewers have to know to type !commands to learn about commands. Long lists clutter chat. Doesn’t naturally show channel-point-specific context like cost or current availability.

When it’s enough: chat-active streams where viewers will type to discover. Less useful for transient or new viewers who don’t know the convention.

Option 3: Pinned chat message

What it is: pin a message at the top of chat with your redeem list.

Strengths: visible at the top of chat for everyone. Survives across viewers without re-running a command.

Weaknesses: decays fast. Long lists are unreadable in a single pinned message. The pin itself gets ignored after a few minutes of chat activity. Manually maintained, so it goes out of sync the moment you change a redeem.

When it’s enough: stream announcements, special events, subathon menus. Not for permanent menus.

Option 4: In-stream overlay or sticky widget

What it is: a custom-built overlay panel that shows your redeems on the stream itself.

Strengths: maximally visible. Every viewer sees it the moment they load the stream. You control the styling and presentation.

Weaknesses: requires a custom build. Streamers either pay for an overlay package (Streamlabs themes, OWN3D) or write their own with HTML and CSS as an OBS browser source. Adds visual clutter to the broadcast. Has to be maintained as your redeem list changes.

When it’s enough: branded streams with a dedicated overlay budget. Events like subathons where you want the menu front-and-center. Less useful as an always-on solution because the on-stream real-estate cost adds up.

Option 5: A Twitch extension panel

What it is: a Twitch extension is a panel or component installed on your channel that runs alongside the stream player. It can sit as an under-video panel on your channel page, or as a configurable overlay on the player itself. Extensions are first-party Twitch UI surfaces, built on Twitch’s Extensions API.

A well-designed extension shows viewers your redeems with descriptions, costs, and current availability without them having to scroll a chat menu, type a command, or read a pinned message. It lives where viewers are already looking.

There are extensions in the streaming category for various purposes. Streamer.bot has community-built extensions. StreamElements has theirs. BetterStreams ships a Twitch Extension that surfaces every redeem and trigger you’ve configured, with descriptions, in the Guide tab on your channel page. If you’ve enabled the Bits tab, viewers can also activate specific triggers with Bits directly from the panel.

Compared to the four options above, the extension panel is the only one that combines panel-level visibility with descriptions and zero ongoing maintenance:

• Option 1 (native menu) has visibility but no descriptions.
• Options 2, 3, 4 have descriptions but require viewer effort or streamer maintenance.

The extension is the cleanest answer to the discovery problem if you’re willing to install one. The trade-off is the install. Viewers don’t have to do anything, but you do (a one-time install through Twitch’s Extensions Manager).

If you’re already using BetterStreams, the Twitch Extension is included on every plan. Install it from the extension page.

If you’re not on BetterStreams yet, see how it handles redeems and discovery.

Putting it together

If you’ve made it this far and you have channel points that nobody uses, here’s the order to fix them in.

1. Diagnose, don’t delete. Start counting redemptions for two weeks before removing anything. The redeem you’re about to delete might be one a few quiet viewers love. Or it might genuinely be dead. Right now, you don’t know. Counting tells you.

2. Fix discovery first, design second. Discovery problems are usually one configuration change away. If you have BetterStreams, install the extension. That solves the discovery problem in one step. If you don’t, write a !commands response in your chatbot and pin it; that’s the highest-leverage discovery fix outside of an extension. Design problems require rework. Discovery fixes will sometimes resurrect “dead” redeems on their own, because viewers were just never seeing them.

3. Test one design fix at a time. If a redeem is dying for a design reason, change one thing. Add a sound effect. Lower the cost. Narrow the context. Then run two streams and recount. If you change three things at once you won’t know which fix worked.

4. Match redeems to your stream’s actual energy. A horror-stream pack, a chill-stream pack, a community-day pack. Use whatever automation tool you have to swap them with the context, instead of leaving everything on always. Streamers who get this right all do some version of this.

5. Read the published posts that go deeper:

• How to Price Your Channel Point Rewards covers the cost-side of design in detail, including the earn-rate math and cost scaling.
• What Twitch Doesn’t Tell You About Your Channel Point Rewards covers why the data gap exists in the first place and how to track manually.
• Variety Streamers: Stop Manually Toggling 50 Reward Slots covers the context-swap mechanics if you stream multiple games or formats.

The nine redeems sitting at zero in your dashboard right now aren’t all bad. Some of them are invisible. Viewers would use them if they could find them. Some of them are dead and need a redesign or a quiet retirement. You’ll know which is which in two weeks if you start counting tonight.