Skip to content

Braze Connection

The Braze connection lets you push player data directly into Braze using the /users/track API. Every trigger event sends both user attributes and a custom event to Braze, so you can build segments, trigger campaigns, and orchestrate Canvas flows based on game activity.


Requirement Where to find it
Braze REST API Key Braze Dashboard → SettingsAPI Keys (needs users.track permission)
REST Endpoint Braze Dashboard → SettingsAPI Keys (e.g. https://rest.iad-01.braze.com)

  1. Go to Connections from the main navigation
  2. Click Add Connection and choose Braze
  3. Enter your API Key and REST Endpoint
  4. Save the connection
  5. Link it to a stream and choose your trigger events

DailyPlay identifies users in Braze through URL parameters passed when a player accesses the stream. Braze supports two identifier types:

URL Parameter Braze API Field Description
braze_id braze_id Braze’s internal user identifier
external_id external_id Your system’s user ID mapped into Braze
user_id external_id Alias — treated the same as external_id

DailyPlay checks for identifiers in priority order: braze_idexternal_iduser_id. If none are present in the URL parameters, the player’s DailyPlay player_uuid is used as the external_id.

https://app.dailyplay.ai/stream/my-org/my-stream?external_id=usr_123

Each trigger event updates the user profile in Braze with the following custom attributes:

Attribute Type Description
country string Player’s country code (detected automatically)
device_type string Device type used by the player (e.g. mobile, desktop)

All DailyPlay-specific attributes are grouped under a dailyplay object on the user profile:

Attribute Type Description
dailyplay.last_game_id string ID of the most recently played game
dailyplay.last_stream_name string Name of the stream the game belongs to
dailyplay.last_stream_slug string URL slug of the stream
dailyplay.last_play_date string ISO 8601 timestamp of the last interaction
dailyplay.stream_<stream_slug> string Event type recorded for this stream (e.g. play_complete) — useful for funnel tracking
dailyplay.last_game_score number Player’s score (only on play_complete events)
dailyplay.last_play_duration number Play duration in seconds (only on play_complete events)