One reward event.
Your chosen channel.
Every delivery should carry the same event ID, source link, observed time, deadline state, and correction behavior. Presentation changes; truth does not.
Campaign ending soon
Dead by Daylight: Jason · archived fixture
scenario lead time: 6h · source: StreamDrops
Browser push
A short notice with a source link after an explicit user gesture. Production must support per-device revocation, quiet hours, expiry, and a visible permission reset.
One network Discord bot
One install represents the whole Stream Empire network. A server selects games, publishers, badges or creator channels; StreamAlert owns the bot token, permissions, commands and delivery receipts. Other verticals only deep-link to this setup.
event: campaign.ending_soon scope: game/dead-by-daylight observed: archived fixture source: streamdrops.app/… correction: supported viewer_progress: never included
Public feed & syndication
one event, many outputsCanonical public event
A human-readable “happening now” item carries the event ID, source/freshness, reward requirements, eligible-channel scope, time remaining and claim path. RSS, Discord, webhooks and future operator-owned social accounts link to that canonical item.
No parallel content operation
Social posts are projections of the same graph event, with attribution and no platform-partnership implication. Durable analysis and campaign-history articles remain outside StreamAlert.
Email digest
reduce notification fatigueDiscoveries
New campaigns for followed games and publishers.
Deadlines
Only known earning and claim windows inside the selected horizon.
Corrections
Previously delivered facts that changed or were retracted.
Control
Frequency, quiet hours, unsubscribe, export, and deletion.
Generic webhook
advanced delivery · laterSigned and replay-safe
Production payloads need an event ID, schema version, timestamp, signature, retry count, and source/retraction coordinates. Consumers acknowledge delivery; retries preserve the same ID.
Private endpoint boundary
Reject credential-bearing URLs, private-network targets, redirects to unsafe origins, oversized responses, and unverified destinations. Endpoint secrets never enter alert content.