The problem
Why this system needed to exist.
A growing sponsored-creator program needed more than a manually checked snapshot. Teams needed to know which creators were live, how each session changed over time, and when a product or campaign code appeared in chat or transcript text.
The first implementation also had to work before one platform offered a supported public API, while remaining adaptable when official APIs became available.
The system
How the pieces work together.
EventBridge checks a configurable creator roster on a schedule. Offline checks stay cheap; when a creator is live, the system claims a unique session and starts a Step Functions execution.
The state machine loops while the stream remains active, collecting normalized metadata, viewer snapshots, optional chat and transcript events, and product mentions into a partitioned event store. It then finalizes per-session metrics.