Startup entity
Every one of those 1 sits in a single category, market-trends. Of the tracked stories, 1 of 1 also mention Aramark, the most common co-covered peer. The 5 average consequence score is below the beat benchmark of 6.6 in the same window.
Last mentioned: Mar 25, 2026
Entity pulse
Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.
Every one of those 1 sits in a single category, market-trends. Of the tracked stories, 1 of 1 also mention Aramark, the most common co-covered peer. The 5 average consequence score is below the beat benchmark of 6.6 in the same window. Each story carries 2 original sources on average, compared with 2.6 for the broader beat in this window. We currently track 1 Startup story that mention Braze, all published on March 25, 2026.
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 46 Startup stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Other entities that clear the same relevance threshold in stories also covering Braze. Shared-story counts are live from our verified record — not editorial picks.
Market Reaction
BRZE shares gap up 23% in pre-market and early trading sessions.
Analyst Revisions
Multiple investment banks raise price targets for Braze, citing strong bookings momentum.
Q4 Earnings Release
Braze reports Q4 2026 results after market close, beating revenue and EPS estimates.
Braze (BRZE) shares skyrocketed 23% following a dominant Q4 2026 earnings report characterized by surging bookings and optimistic forward guidance. The performance serves as a critical bellwether for the customer engagement and marketing automation sectors, suggesting a robust rebound in enterprise software spending.
Braze is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.
