streamlinx
docs

Best Practices

Optimize your Streamlinx setup with these proven tips and recommendations for Discord server administrators.

Channel Organization

Use Dedicated Notification Channels

Create separate channels specifically for stream notifications:

Recommended Names:

  • #stream-alerts
  • #live-now
  • #twitch-streams
  • #youtube-streams
  • #content-creators

Why:

  • Keeps general chat clutter-free
  • Members can mute notification channels if desired
  • Easier to find active streams
  • Better organization for larger communities

Organize by Platform

Separate notifications by platform for better organization:

/streamer add platform:Twitch username:shroud channel:#twitch-alerts
/streamer add platform:YouTube username:@MrBeast channel:#youtube-alerts

Benefits:

  • Platform-specific role mentions
  • Different channel permissions per platform
  • Easier to track platform-specific metrics

Organize by Category

Group streamers by game or content type by creating dedicated Discord channels and routing streamers to them:

/streamer add platform:Twitch username:valorant_pro channel:#valorant-streams
/streamer add platform:Twitch username:minecraft_creator channel:#minecraft-streams

Best For:

  • Gaming communities focused on specific titles
  • Content creator networks
  • Multi-game communities

Role Management

Create an Opt-In Role

Don't ping @everyone - create a dedicated role:

Setup:

  1. Create role: @Stream Alerts or @Streamer Notifications
  2. Make it mentionable
  3. Configure role mentions in the Web Portal under streamer settings
  4. Let members self-assign via reaction roles or Discord's role picker

Benefits:

  • Members can choose to receive notifications
  • Reduces notification fatigue
  • Better community engagement

Use Different Roles for Different Channels

With multiple notification channels, use different roles:

#twitch-alerts → @Twitch Fans
#youtube-alerts → @YouTube Watchers
#vip-streams → @VIP Members

How: Configure channel-specific settings in the Web Portal to set different ping roles for each channel.

Consider Time Zones

If your community spans multiple time zones:

Option 1: Region-Specific Roles

  • @NA Streams - North America
  • @EU Streams - Europe
  • @APAC Streams - Asia-Pacific

Option 2: Time-Based Channels

  • #morning-streams - 6AM-12PM
  • #afternoon-streams - 12PM-6PM
  • #evening-streams - 6PM-12AM

Requires manual organization but can be effective for global communities.

Notification Configuration

Enable Auto-Delete for Active Communities

If you track many streamers, enable auto-delete in the Web Portal:

  1. Go to /portal and open your server
  2. Navigate to streamer settings
  3. Enable auto-delete option

Benefits:

  • Keeps notification channels clean
  • Prevents clutter from offline streams
  • Members see only currently live streams

Requirements:

  • Bot needs "Manage Messages" permission
  • Won't work if members manually delete notifications

Use Custom Templates Sparingly

While templates are powerful, keep them simple. Configure templates in the Web Portal:

Good Template:

🔴 {streamer} is live!
Game: {game}
{url}

Too Complex:

🎮🔴🎮🔴 ALERT ALERT ALERT 🔴🎮🔴🎮
{streamer} is streaming {game}!
Title: {title}
Viewers: {viewer_count}
Platform: {platform}
🔗🔗🔗 {url} 🔗🔗🔗

Best Practices:

  • Keep it under 300 characters
  • Include essential info only: streamer, game, link
  • Use 1-2 emojis max
  • Preview templates in the Web Portal before saving

Customize Embed Colors

Match your server's brand by configuring embed colors in the Web Portal:

Recommended Colors:

  • Match your server icon color
  • Use platform colors: Twitch (#9146FF), YouTube (#FF0000), Kick (#53FC18)
  • Use category colors for game-specific channels

Streamer Selection

Prioritize Active Streamers

Focus on streamers who:

  • Stream regularly (3+ times per week)
  • Have engaged communities
  • Align with your server's interests

Avoid:

  • Inactive accounts (haven't streamed in 6+ months)
  • Streamers who rarely go live (once per month)
  • Channels that primarily upload pre-recorded content

Balance Platform Distribution

Don't exceed recommended ratios:

Free Tier:

  • Good: 5 Twitch + 5 YouTube + 5 Kick
  • Good: 3 Twitch + 3 YouTube + 3 Kick
  • Avoid: 5 Twitch + 0 YouTube + 0 Kick (limits growth to one platform)

Premium Tier:

  • Good: 150 Twitch + 10 YouTube + 25 Kick
  • Good: 100 Twitch + 10 YouTube + 20 Kick
  • Avoid: 300 Twitch + 0 YouTube + 0 Kick (platform dependency)

Track Your Community Members

Prioritize tracking your own community's streamers:

Benefits:

  • Supports your members
  • Builds community engagement
  • Members are more likely to watch each other
  • Creates networking opportunities

Setup:

/streamer add platform:Twitch username:YourMember channel:#member-streams

Premium Optimization

Use Analytics to Optimize

All users can access the Analytics Overview (notifications, hours, live stats). Premium unlocks the full dashboard with patterns and leaderboards. Review analytics monthly:

Check:

  • Top Streamers: Are you tracking the right people?
  • Notification Trends: When are most streams happening?
  • Platform Distribution: Is one platform dominating?

Optimize Based on Data:

  • Remove low-activity streamers
  • Add streamers during peak hours
  • Balance platform distribution

Leverage Custom Identity

Make notifications feel personal:

For Member Streams:

Name: "{streamer} is Live!"
Avatar: {streamer_avatar}

Makes it look like the streamer posted it themselves.

For Official Announcements:

Name: "YourServer Streams"
Avatar: {server_icon}

Branded notifications for your community.

For Platform Channels:

Name: "Twitch Alerts"
Avatar: [Twitch logo URL]

Clearly indicates source platform.

Create Multiple Notification Channels Strategically

Don't create too many channels:

Good (5-10 channels):

  • #twitch-streams
  • #youtube-streams
  • #member-streams
  • #vip-streamers
  • #gaming-streams

Too Many (15+ channels):

  • Overwhelming for members
  • Hard to manage
  • Most channels will be low-activity

Sweet Spot: 3-5 notification channels for most communities.

Performance & Reliability

Monitor Bot Permissions

Regularly check bot permissions:

Required Permissions:

  • ✅ Send Messages
  • ✅ Embed Links
  • ✅ Read Message History
  • ✅ Manage Webhooks (Premium)
  • ✅ Manage Messages (Auto-delete)

How to Check:

  • Right-click the notification channel
  • Permissions → Streamlinx bot
  • Verify green checkmarks for required permissions

Test Before Announcing

Before telling your community about Streamlinx:

  1. Add 1-2 test streamers
  2. Wait for them to go live naturally
  3. Verify notifications work correctly
  4. Check permissions and formatting
  5. Then add remaining streamers and announce

Use Role Hierarchy Wisely

Ensure Streamlinx bot role is positioned correctly:

Bot Role Should Be:

  • Above roles it needs to mention
  • Below admin/moderator roles
  • Above the @Stream Alerts ping role

Fix Issues:

  1. Server Settings → Roles
  2. Drag Streamlinx bot role to correct position
  3. Verify bot can mention configured roles

Community Engagement

Announce New Streamers

When adding community members as tracked streamers:

Good Practice:

📢 Announcement: We're now tracking @MemberName's streams!
When they go live, you'll see notifications in #member-streams.
Give them a follow! https://twitch.tv/membername

Benefits:

  • Shows appreciation for community members
  • Encourages follows
  • Builds excitement

Create Stream Events

Combine Streamlinx with Discord Events:

When Member Goes Live:

  1. Streamlinx posts notification
  2. Moderator creates Discord Event for the stream
  3. Members can RSVP and get reminders

Automation Ideas:

  • Use Discord's Scheduled Events
  • Link to stream URL
  • Set duration based on typical stream length

Reward Active Watchers

Recognize members who support streams:

Ideas:

  • Create @Stream Supporter role for active watchers
  • Monthly shoutouts for most engaged members
  • Stream-watching competitions
  • Partner with tracked streamers for giveaways

Server Settings

Set Up Proper Moderation

Configure notification channels with appropriate permissions:

Recommended:

@everyone:
  ✅ Read Messages
  ✅ Read Message History
  ❌ Send Messages (read-only)
  ❌ Add Reactions
 
@Moderators:
  ✅ Send Messages
  ✅ Manage Messages
  ✅ Embed Links
 
@Streamlinx:
  ✅ Send Messages
  ✅ Embed Links
  ✅ Manage Webhooks
  ✅ Manage Messages

Why:

  • Prevents spam in notification channels
  • Keeps channels clean
  • Members can still view and click links

Use Channel Topics

Set helpful channel topics:

Example:

#twitch-streams
Topic: 🔴 Live Twitch streams | Click links to watch | React with 👀 if watching

Pin Important Information

Pin a message in notification channels:

Example Pinned Message:

📺 Welcome to #stream-alerts!
 
This channel shows when tracked streamers go live.
• Click stream links to watch
• Get notified by grabbing the @Stream Alerts role in #roles
• Suggest streamers to track in #suggestions
 
Current trackers: 15/25 (Premium)

Scaling

Start Small, Grow Gradually

New Server:

  • Start with 2-3 streamers
  • Single notification channel
  • Gather feedback from members

Growing Server:

  • Add streamers based on member requests
  • Consider Premium when approaching 10 streamers
  • Plan per-streamer channel routing strategy

Established Server:

  • Optimize based on analytics
  • Multiple channels organized by category
  • Regular review and cleanup

Plan for Premium

If approaching Free tier limits:

Before Upgrading:

  1. Review current trackers - are all necessary?
  2. Estimate how many streamers you'll need
  3. Plan per-streamer channel routing strategy
  4. Calculate if $2.99/month is worthwhile

After Upgrading:

  • Don't immediately max out 310 streamers
  • Add gradually based on demand
  • Monitor analytics to optimize

Regular Maintenance

Monthly Tasks:

  • Review streamer list - remove inactive accounts
  • Check analytics (Premium) for usage patterns
  • Update templates/settings based on feedback
  • Verify bot permissions in all channels

Quarterly Tasks:

  • Review Premium subscription value
  • Audit notification channels - combine or split as needed
  • Update role mentions based on member preferences
  • Test disaster recovery (remove/re-add test streamer)

Common Mistakes to Avoid

❌ Don't Track Too Many Streamers

Problem: Tracking 25 random streamers "just because you can"

Solution: Focus on quality over quantity. Track streamers your community actually cares about.

❌ Don't Use @everyone

Problem: Pinging all server members for every stream

Solution: Create opt-in roles like @Stream Alerts

❌ Don't Ignore Permissions

Problem: Bot can't send messages, notifications fail silently

Solution: Regularly verify bot permissions in notification channels

❌ Don't Over-Customize Templates

Problem: 500-character template with excessive emojis

Solution: Keep templates simple and readable

❌ Don't Forget About Mobile Users

Problem: Templates/embeds look bad on mobile

Solution: Test notifications on mobile before finalizing

❌ Don't Set Up and Forget

Problem: Never reviewing configuration after initial setup

Solution: Monthly maintenance and optimization

❌ Don't Neglect Communication

Problem: Members don't understand how stream notifications work

Solution: Pin informational messages, update channel topics

Security & Privacy

Protect Bot Token

Never:

  • Share your bot token (you don't have direct access anyway)
  • Give admin permissions to Streamlinx (not needed)
  • Allow untrusted members to modify bot configuration

Review Permissions Regularly

Audit bot permissions quarterly:

Server Settings → Integrations → Streamlinx

Verify only necessary permissions are granted.

Use Server Subscriptions Safely

Best Practices:

  • Only server owner or trusted admins should manage subscriptions
  • Enable 2FA on Discord account managing subscriptions
  • Review Discord Server Settings → Server Subscriptions monthly

Getting Help

If you're stuck or need advice:

  1. Read Documentation: Streamlinx Documentation
  2. Check FAQ: FAQ Page
  3. Join Support Discord: Discord support server
  4. Ask Community: Other server admins can share their setups
  5. Email Support: support@streamlinx.io (Premium gets priority)

Summary

Top 10 Best Practices:

  1. ✅ Use dedicated notification channels
  2. ✅ Create opt-in ping roles
  3. ✅ Enable auto-delete for active communities
  4. ✅ Keep message templates simple
  5. ✅ Track active, relevant streamers
  6. ✅ Monitor bot permissions regularly
  7. ✅ Start small, scale gradually
  8. ✅ Review analytics monthly (Premium)
  9. ✅ Test before announcing to community
  10. ✅ Engage community around streams

Follow these practices and you'll have a well-organized, engaging stream notification system that your community will love!

Need Help?