Skip to content

Streams Overview

Streams are campaign containers that let you group multiple games into a single, shareable experience. Use streams to build marketing funnels, run time-limited promotions, drive team engagement at live events, or guide players through a sequence of games.

A stream is a collection of games bundled together under one link. Instead of sharing individual games, you can share a stream that presents players with multiple games — either in a fixed order or randomized.

Key capabilities:

  • Group multiple games into one campaign
  • Set start and end dates to schedule promotions
  • Control game ordering (sequential or random)
  • Limit total plays or plays per user
  • Organize streams into funnel stages for pipeline visualization
  • Run social/team mode with real-time leaderboards
  • Connect webhooks and integrations for real-time event tracking
  • Track UTM parameters for marketing attribution

Streams follow a lifecycle with the following statuses:

StatusDescription
DraftStream is being set up, not yet visible
ScheduledStream is configured with a future start date
ActiveStream is live and accepting plays
PausedStream is temporarily stopped
CompletedStream has reached its end date or play limit
ArchivedStream is retired and no longer accessible
  1. Navigate to your organization dashboard
  2. Click Streams in the sidebar
  3. Click Create Stream
  4. Enter a name and optional description
  5. Add games to the stream (see Adding Games)
  6. Configure scheduling and settings
  7. Publish the stream

Set a start and end date to control when your stream is available:

  • Start date (start_at) — The stream becomes playable at this time
  • End date (end_at) — The stream stops accepting plays after this time
  • Timezone — All dates are interpreted in the selected timezone

If a player visits the stream before the start date, they see a countdown timer. After the end date, the stream shows a completion message.

Stream scheduling settings

Add games to your stream from your organization’s published games:

  1. Open your stream
  2. Click Add Games
  3. Select one or more games from your library
  4. Arrange the display order (drag to reorder)

Each game within a stream can have its own availability window:

  • Available from — When the game becomes playable within the stream
  • Available until — When the game is no longer playable

This lets you drip-release games over the duration of a campaign.

Choose how games are presented to players:

  • Sequential — Players see games in the order you set. Useful for guided journeys or multi-step funnels.
  • Random — Games are shuffled for each player. Useful for variety packs or A/B testing.

Game ordering options

Control how many times games can be played:

  • Max plays per user — Limit each player to a set number of plays
  • Max total plays — Cap the total number of plays across all users

Play limit settings

Streams support UTM parameters for marketing attribution:

  • utm_source
  • utm_medium
  • utm_campaign
  • utm_content
  • utm_term

These are passed through to your webhook events and analytics.

UTM tracking settings

Every stream has a unique public URL:

https://app.dailyplay.ai/stream/[org-slug]/[stream-slug]

Sharing options include:

  • Direct link — Copy the stream URL to share via email, SMS, or social media
  • QR code — Generate a scannable QR code for print materials or in-store displays
  • Embed (iframe) — Embed the stream directly on your website with a responsive 450×800 portrait frame
  • JavaScript snippet — Dynamically insert the stream player into any webpage

For access control:

Attach connections to a stream to receive real-time events when players interact with your games. Supported integrations include Braze, Zapier, MailChimp, HubSpot, Salesforce, Segment, and custom webhooks.

Common use cases:

  • CRM updates on game completion
  • Email triggers on prize redemption
  • Analytics tracking across your marketing stack
  • Lead capture and audience segmentation

You can configure which trigger events fire for each connection (e.g., play_complete, prize_redemption).