Data Overview
Braze exposes data across campaigns, canvases, segments, events, content cards, and platform-level KPIs. Each entity type has a list/metadata variant, an analytics variant (time-series performance metrics), and in some cases a details variant (configuration and structure).
Entity types
Campaigns
✅
✅
✅
Canvases
✅
✅
✅
Events
✅
✅
—
Cards
✅
✅
—
Segments
✅
✅
✅
KPIs
—
✅ (3 KPI entities)
—
Campaigns
Campaigns — list fields
id
Unique campaign identifier
name
Campaign name
is_active
Whether the campaign is currently active
last_edited
Timestamp of last edit
tags
Tags applied to the campaign
Campaigns analytics fields
sends
Total messages sent
deliveries
Successfully delivered messages
opens
Total opens (unique and total)
clicks
Total clicks
bounces
Hard and soft bounces
unsubscribes
Unsubscribe events
conversions
Conversion events tied to the campaign
revenue
Revenue attributed to the campaign
Canvases
Canvases analytics fields
entries
Users who entered the canvas
revenue
Revenue attributed to the canvas
exits
Users who exited
conversions
Conversion events per canvas
steps_data
Per-step breakdown of sends, opens, clicks
Events
Events analytics fields
event_name
Name of the custom event
total
Total event occurrences in the time window
date
Date of the data point
KPIs
KPI fields (all three KPI entities)
date
Date of the data point
new_users
New user registrations (KPI daily new users)
dau
Daily active users (KPI daily active users)
uninstalls
App uninstalls (KPI daily app uninstalls)
Cards
Cards analytics fields
impressions
Number of times the card was viewed
clicks
Number of clicks on the card
dismissals
Number of times the card was dismissed
enrollments
Users who received the card
Segments
Segments analytics fields
date
Date of the data point
size
Number of users in the segment on that date
Segments details fields
id
Segment identifier
name
Segment name
creation_time
When the segment was created
filters
Filter logic defining the segment
Common metric combinations
Campaign deliverability:
sends+deliveries+bouncesto monitor inbox placement healthEngagement funnel:
opens+clicks+unsubscribes+conversionsper campaignGrowth KPIs: Join
kpi_daily_new_users+kpi_daily_active_users+kpi_daily_app_uninstallsinto a single time-series table using AppendSegment size trends:
segments_analyticsover time to track audience growth or churn within key segmentsCanvas vs. campaign ROI: Join
campaigns_analyticsandcanvases_analyticson date to compare revenue attribution across both channel types
Use cases by role
Pull
campaigns_analyticsandcanvases_analyticsinto Google Sheets or Looker Studio to build live performance dashboards without manual exportsUse
segments_analyticsto track how audience sizes change week over week — useful for monitoring churn or growth in key cohortsSend campaign performance snapshots to ChatGPT or Claude for AI-assisted analysis and copy recommendations
Combine
kpi_daily_new_users,kpi_daily_active_users, andkpi_daily_app_uninstallsusing Append to build a unified growth KPI table in BigQueryTrack
events_analyticsover time to measure feature adoption through custom event countsJoin segment data with external user data in BigQuery to identify which segments drive the most revenue
Load all Braze entities into BigQuery to build a centralized marketing data warehouse
Use Aggregate transformation to summarize campaign performance by tag, channel, or time period
Join
campaigns(metadata) withcampaigns_analytics(metrics) using the campaign ID to build enriched reporting tables
Platform-specific notes
Braze REST endpoints vary by region — make sure you use the correct endpoint for your account (e.g.,
rest.iad-01.braze.comvs.rest.fra-01.braze.com)Analytics entities return time-series data; the granularity is daily
The
start_dateparameter controls how far back data is fetched — if left unset, Braze may return a limited default windowcampaigns_detailsandcanvases_detailsreturn structural/configuration data, not performance metrics — useful for auditing or documentation, not trend analysisSegment filter logic in
segments_detailsis returned as a nested JSON structure that may need flattening depending on your destination
Last updated
Was this helpful?
