Streams
Named dashboards that aggregate game events. Every player is tied to one stream — pick names you'll recognize on the Analytics page.
Streams keep analytics clean. If you operate one brand on three surfaces (blog, app, partner portal), don't squash everything into one chart — split into three streams and switch between them in the Hub.
How they're wired
- A player has exactly one stream.
- Every game event from that player flows into the linked stream.
- The Analytics page filters by stream; you flip between dashboards from a single dropdown.
Streams are managed at the player level. You don't reference a stream directly from your embed — pick or create one when you set up the player.
Creating one
Hub → Configuration → Streams → New stream. Pick a name you'll spot on the dropdown — Acme blog, Acme app, Partner portal Q1.
States
- Active — receives events; appears in the player's Analytics dropdown.
- Archived — kept for historical analytics but hidden from selectors. Restore at any time.
Stream IDs
Streams have an analytics_id (ana_…) you can copy from the Hub. You'll see this referenced in webhook payloads and analytics exports — it's the same ID you assigned to the player.