Marketing Automation
Braze
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Braze, Inc. · www.braze.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Braze at a glance
- Vendor
- Braze, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates Braze 3/5, the mean of 6 judges. Braze presents itself as a consumer engagement platform, and the bench scored it strongest on journey orchestration and channel coverage, both clustering at 8-9: branching on real-time behaviour, exit criteria the moment a contact converts, versioned post-launch edits, and email, SMS/RCS, WhatsApp, LINE and KakaoTalk run from one first-party profile with audience sync to major ad networks. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Braze presents itself as a consumer engagement platform, and the bench scored it strongest on journey orchestration and channel coverage, both clustering at 8-9: branching on real-time behaviour, exit criteria the moment a contact converts, versioned post-launch edits, and email, SMS/RCS, WhatsApp, LINE and KakaoTalk run from one first-party profile with audience sync to major ad networks. CRM and data follows at 6-7 on bi-directional warehouse flows and identity resolution. Lead management is the weakest area, scores spanning 0 to 3: no public information on lead scoring, lifecycle stages or handover to sales, and the documented propensity targeting serves ad audiences. Sovereignty scored 0 to 2, where the judges diverged in method — the data protection officer gave 2 on the finding that the contracting entity on the legal pages is Braze, Inc., described elsewhere as Nasdaq-listed, while the others recorded no public information on residency, hosting, a processing agreement or subprocessors. Consent and profiling scored 3-4; the buying path shown is a free trial and Contact Sales.
Speaks for it
- Journey orchestration scores cluster at 8-9 on branching paths, exit criteria the moment a contact converts, and versioned post-launch edits.
- Channel coverage scores cluster at 8-9 across email, SMS/RCS, WhatsApp, LINE and KakaoTalk, with audience sync to major ad networks.
- Message priority rules set once apply across every campaign and Canvas, alongside cross-channel frequency capping and global control groups for uplift measurement.
- CRM and data scores cluster at 6-7 on bi-directional flows to warehouses, cloud storage and CDPs, with identity resolution on email, phone and custom IDs.
- Intelligent channel delivery picks the channel a customer is most likely to engage with based on past interactions.
Held against it
- Lead management scores span 0 to 3, and no public information was found on lead scoring, lifecycle stages or handover to sales.
- Sovereignty scores span 0 to 2, and the contracting entity named on the legal pages is Braze, Inc., described elsewhere as Nasdaq-listed, with no public information on data residency, hosting, a data processing agreement or subprocessor locations.
- Consent and profiling scores cluster at 3-4, with no public information on double opt-in, consent timestamps and sources stored per contact, or retention for inactive records.
- No CRM is named among the 180+ turnkey partner integrations, and no public information was found on field-level conflict resolution, sync error logs or documented API rate limits.
- The buying path shown is a free trial and Contact Sales, and no public prices appear on the captured pages.
Best for
- You run consumer lifecycle marketing across many owned channels and need journeys that branch on real-time behaviour, with priority rules and frequency capping applied across the whole programme.
- You spend on paid media and want first-party audience sync to the major networks, with ads suppressed the moment a customer converts on any channel.
- Your source of truth lives in a warehouse or CDP and you need bi-directional sync plus identity resolution that merges anonymous visitors into known profiles.
Avoid if
- You need scored, routed leads — lifecycle or pipeline stages, qualification and handover to sales with follow-up expectations — rather than consumer messaging.
- Your procurement must see a data processing agreement, data residency or subprocessor locations before signature.
- Your compliance model requires double opt-in, per-contact consent timestamps and sources, and defined retention for inactive records.
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 4.5 of 5 |
| Lead scoring, routing & lifecycle | 1.5 of 5 |
| Channels & personalisation | 4.5 of 5 |
| Consent, tracking & profiling | 1.5 of 5 |
| CRM integration & data model | 3 of 5 |
| European sovereignty | 1 of 5 |
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and journeys documented and readable months later.
The Demand Gen Lead
Canvas Flow brings Action, Audience and Decision Split branching, exit criteria on conversion, frequency capping across channels, priority rules set once and applied across every campaign and Canvas, versioning with post-launch edits, and Global Control Groups for uplift measurement — programme-level arbitration plus holdouts, which is what I buy. Per-step reporting is only described in general terms, so I stop just short of full marks. 2 3 4 8
The Sales Ops Manager
Orchestration is the best-evidenced area: branching on real-time behaviour and attributes, exit criteria the moment a contact converts, versioning with post-launch edits, testing at journey, step and message level, and frequency capping on or across channels. What pushed it high is programme-level control — priority rules set once and applied across every campaign and Canvas, plus global control groups for uplift measurement. I held back a point because per-contact journey state and per-step reporting appear only as a generic analytics statement. 2 3 4 8
The Data Protection Officer
The captured product pages document a no-code visual journey builder with branching, real-time cross-channel and external-stack triggers, exit criteria on conversion, frequency capping, and message priority rules set once and applied across every campaign and Canvas, plus post-launch edits with versioning, journey-level testing, and Global Control Groups for uplift measurement. That is coherent whole-programme orchestration with a single priority layer and holdout groups; we found no public information on per-contact journey state and reporting per step. 2 3 4 5
The Lifecycle Marketer
Journeys branch on real-time behaviour and cross-channel interactions, exit people the instant they convert, and message priority rules set once apply across every campaign and Canvas — a programme-level arbitration layer rather than per-flow tuning, which is exactly what I want to see. Frequency capping across channels, versioning with post-launch edits, testing at the journey, step and message level, and turnkey Global Control Groups for measuring engagement uplift cover most of what I look for. The one gap in the captured pages is per-contact journey state and step-level reporting, which is not spelled out. 2 3 4
The Solution Architect
Canvas Flow gives decision splits, action and audience paths, exit criteria the moment someone converts, versioning with post-launch edits, and testing at journey, step and message level; global control groups cover holdout measurement, and priority rules set once and applied across every campaign and journey are the cross-journey arbitration a live programme needs. We found no public information on per-contact journey state or per-step reporting, so it sits just short of the top. 2 3 4
The Skeptic
Canvas Flow with Action Paths, Audience Paths and Decision Split, exit criteria that pull a contact out the moment they convert, post-launch edits with version history, and testing at the journey, step and message level covers my checklist for a mature builder. Frequency capping on or across channels and message priority rules applied to every campaign and Canvas mean a contact qualifying for several journeys is handled rather than left to chance. I found no public information stating per-contact journey state or reporting per step, which holds this just below the top band. 2 3 4
Lead scoring, routing & lifecycle
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.
0 — No scoring, lifecycle or lead handling at all; the product is a sending tool for lists.
3 — A rule-based lead score from attributes or engagement, or lifecycle stages set by tags or fields.
5 — Configurable lead scoring on attributes and behaviour, lifecycle or pipeline stages, and qualified leads assigned or notified to sales.
8 — Multiple scoring models per product or region, negative scoring and score decay, account-level scoring alongside contact-level, routing rules to owners or teams with follow-up SLAs, and score history visible per contact.
10 — Scoring is explainable and accountable: the contribution of each signal visible per record, model changes versioned with their effect on the funnel, routing rules auditable, and predictive scoring — where offered — documented well enough for a DPO to assess it as automated decision-making.
The Demand Gen Lead not rated — no public information
We found no public information on lead scoring, lifecycle stages or handover to sales. What the captured pages do document — 100+ segmentation filters, propensity-based ad targeting and predictive recommendations — serves messaging decisions, not a scored, routed lead with an owner and a follow-up SLA. 8 9
The Sales Ops Manager not rated — no public information
We found no public information on lead scoring, lifecycle stages, qualification or handover to sales. The nearest capability on the captured pages is purchase-propensity targeting for paid advertising, which is an ad-spend function rather than sales routing. 8 9
The Data Protection Officer
The pages show purchase-propensity targeting and predictive recommendations, so individuals are scored on behaviour, but we found no public information on lead scoring models, lifecycle or pipeline stages, qualification, or routing and handover to sales. The predictive scoring is documented nowhere near the level a controller would need to assess it as automated decision-making, which is the first thing I look for. 8 9
The Lifecycle Marketer not rated — no public information
We found no public information on lead scoring, qualification models, lifecycle stages or handover to sales with follow-up obligations. The captured product pages describe engagement journeys and propensity-based ad targeting, which is adjacent but is not lead management. 2 4 8 9
The Solution Architect not rated — no public information
We found no public information on lead scoring, lifecycle stages, qualification, or handover to sales on any page we read. The captured pages describe a consumer engagement platform; the closest material is purchase-propensity targeting for paid ads, which is not lead management. 1 2 4 8 9
The Skeptic
Purchase-propensity targeting and BrazeAI predictive intelligence are scoring of a kind, but they aim at ad audiences, not lead qualification or a handover to sales. We found no public information on lead scores, lifecycle stages, pipeline stages, or routing to owners with follow-up expectations; the captured pages present a consumer-engagement platform rather than a lead machine. 8 9
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can send and personalise — email, SMS, push, on-site content, ad audiences — judged on what shares one profile and one suppression list.
0 — Not a sending platform; the product cannot deliver messages on any channel.
3 — Email with merge-field personalisation, plus sign-up forms or landing pages.
5 — Email plus at least one further channel (SMS, push, or ad-audience sync) driven from the same contact profile, and dynamic content blocks based on contact data.
8 — Email, SMS and push from one profile with shared unsubscribe handling, on-site personalisation, ad-audience sync to the major networks, cross-channel frequency capping, and content personalised on behaviour rather than only on stored fields.
10 — Channel is a delivery detail: one profile and one consent state across every channel, next-best-channel selection, and personalisation that draws on the full behavioural record without the marketer assembling it by hand.
The Demand Gen Lead
Email, mobile and web messaging, SMS/RCS, WhatsApp, LINE and KakaoTalk plus audience sync to every major ad network, all from unified first-party profiles with cross-channel frequency capping and behaviour-based personalisation. Intelligent channel delivery picks the channel a person engages with — next-best-channel in practice; a single consent state across every channel is only implied by per-channel subscription handling. 2 4 5 8 9
The Sales Ops Manager
Email, SMS/RCS, push and web messaging plus WhatsApp and ad-audience sync to the major networks all run from one first-party profile, with cross-channel frequency capping, subscription status management, and intelligent channel delivery based on past interactions. Personalisation is behavioural — AI recommendations from behaviour and purchase history and catalog content pulled at send time — not just merge fields. One consent state across every channel is implied by shared subscription handling rather than stated outright, which is why I stopped short of the top. 2 4 5 8 9
The Data Protection Officer
Email, mobile and web messaging, SMS/RCS, WhatsApp, LINE and KakaoTalk run from one profile, with ad-audience sync to the major networks, cross-channel frequency capping, dynamic content from catalog data and send-time APIs, and intelligent channel delivery choosing the channel a customer is most likely to engage with. Opt-in and opt-out processing and subscription status management are documented per channel, but one consent state carried across every channel is not something these pages show, and that gap is what holds this down from my perspective. 4 5 8 9
The Lifecycle Marketer
Email, mobile push, web messaging, SMS/RCS, WhatsApp, LINE and KakaoTalk plus paid audience sync to Meta, Google, TikTok and the other major networks all hang off one first-party profile, with cross-channel frequency caps and paid ads suppressed the moment someone converts on any channel. Intelligent channel delivery based on past interactions and AI channel timing amount to next-best-channel selection, and personalisation draws on behaviour, purchase history and catalog data at send time rather than hand-built merge fields. What the captured pages do not show is a single consent state shared across every channel — subscription statuses are managed, but managed per channel. 2 4 5 8 9
The Solution Architect
Email, push, in-app, web, SMS/RCS, WhatsApp, LINE and KakaoTalk run from one profile with audience sync to every major ad network, cross-channel frequency capping, shared opt-in/opt-out and subscription handling, and behaviour-driven personalisation through catalog data and send-time API content. We found no public information on a single consent state spanning all channels, which is what the top level asks. 1 4 5 8 9
The Skeptic
Email, push, in-app and web messaging, SMS/RCS, WhatsApp, LINE and KakaoTalk, plus audience sync to Meta, Google, TikTok, Snapchat, Pinterest, LinkedIn, Criteo and The Trade Desk — all from one first-party profile, with cross-channel frequency capping and content that changes with behaviour — is the full plate. Intelligent channel delivery picks the channel a customer is most likely to engage with based on past interactions. I found no public information stating one consent state shared across every channel, so I hold just below the top. 2 4 5 9
Consent, tracking & profiling
Show reasoningHide reasoning
How this is scored
The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.
0 — The vendor states a practice that defeats consent, such as importing purchased lists or tracking named contacts with no opt-in mechanism at all.
3 — Double opt-in available and unsubscribe handled per contact.
5 — Double opt-in with the consent timestamp and source stored per contact, consent or subscription status per channel, and a documented way to answer access and erasure requests.
8 — Consent reproducible as evidence with the wording versioned, tracking switchable per contact or a cookieless or first-party tracking mode, profiling suppressible per person, retention for inactive records stated and executed per data category, and erasure covering derived scores.
10 — Built for the accountability principle: a per-contact history of what was tracked, scored and decided, automated decision-making documented well enough to support an Art. 22 DSGVO assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.
The Demand Gen Lead
The product processes opt-ins and opt-outs, manages subscription statuses per channel, and updates SMS subscription state in real time via keyword processing, and a GDPR FAQ page exists. We found no public information on double opt-in, consent timestamps and sources stored per contact, erasure request handling, profiling suppression or retention for the platform itself; the cookie policy detail on the captured pages concerns Braze's own website. 4 5 6 7
The Sales Ops Manager
Opt-ins and opt-outs are processed per contact with managed subscription statuses, a cookie consent manager discloses cookie durations, and a GDPR FAQ page exists. For a platform that profiles behaviour and predicts purchase propensity, the evidence runs thin beyond that: we found no public information on double opt-in, consent timestamps and sources stored per contact, retention for inactive records, or erasure covering derived scores. The vendor's own cookie page also states essential cookies cannot be switched off. 4 6 7 8
The Data Protection Officer
The documented consent machinery is opt-in and opt-out processing, subscription status management, and keyword-driven status changes for SMS, alongside a GDPR FAQ page and a cookie consent manager on Braze's own website — where essential cookies are stated to be non-switchable and session replay records clicks, movements and scrolls. We found no public information on double opt-in, stored consent timestamps and sources, per-contact switches for tracking or profiling, retention for inactive records, or deletion that removes derived scores — and the platform demonstrably computes derived scores through purchase-propensity targeting and predictive recommendations of named users. 4 5 6 7 9
The Lifecycle Marketer
Subscription statuses, opt-ins and opt-outs are managed with keyword processing updating SMS subscription state in real time, and a GDPR FAQ page is published — but we found no public information on double opt-in, on consent timestamp and source stored per contact, or on how access and erasure requests are answered for the service. The captured cookie policy governs the vendor's own website, including session replay of clicks, movements and scrolls with essential cookies that cannot be switched off, which says little about what a brand's end users experience. 4 5 6 7
The Solution Architect
On the product side the pages document opt-in and opt-out processing, subscription status management and keyword-based SMS opt-ins, and the legal pages add a GDPR FAQ plus ISO 27001 and SOC 2 claims. We found no public information on double opt-in, consent timestamp and source stored per contact, per-channel consent, retention for inactive records, or erasure covering derived scores — and the cookie policy for the vendor's own site describes session replay capturing clicks, movements and scrolls, with essential cookies that cannot be switched off. 4 5 6 7 8
The Skeptic
Subscription statuses, opt-in and opt-out processing, and SMS keyword-based status changes handle the unsubscribe side per contact, and a GDPR FAQ page is published. Beyond that I found no public information on double opt-in, on the consent timestamp and source stored per contact, on retention periods for contact data, or on suppressing profiling for an individual. The cookie policy that is captured concerns Braze's own website, where essential cookies cannot be switched off and session replay provided by Qualified records clicks, movements and scrolls. 4 5 6 7
CRM integration & data model
Show reasoningHide reasoning
How this is scored
The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.
0 — No way to get contact data in or out beyond typing it in.
3 — CSV import and export, and a sync or connector to a named CRM.
5 — Two-way sync with at least one major CRM (or a built-in CRM) with field mapping, duplicate handling, and a documented API.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry and an error log, and API rate limits documented.
10 — One record, two systems, no ambiguity: identity resolution across anonymous and known states, field-level ownership defined per system, replay of failed syncs, and a data model the customer can extend without vendor services.
The Demand Gen Lead
The data platform side is real: bi-directional flows to warehouses, cloud storage, CDPs and backends, custom field mapping, identity resolution merging records on email, phone and custom IDs, and profiles spanning anonymous-to-known users. We found no public information on a named CRM connector, per-field conflict resolution, account objects, custom objects, or documented rate limits and sync error logs, so the join to sales' system rests on generic APIs and 180-plus turnkey integrations. 1 8 9
The Sales Ops Manager
Bi-directional data flow with warehouses, CDPs and backend systems, automated identity resolution merging records on email, phone and custom IDs, custom field mapping, encrypted syncs and modern APIs are all documented. What I need before I trust a pipeline report is not on the captured pages: we found no public information on configurable conflict resolution per field, field-level ownership, a sync error log or retry, documented rate limits, or account-level objects — and no CRM is named among the 180+ turnkey integrations. 1 8 9
The Data Protection Officer
Bi-directional data flow with data warehouses, cloud storage, CDPs and backend systems, documented SDKs and APIs, custom field mapping, encrypted syncs, and automated identity resolution merging records on email, phone or custom IDs — including converting previously anonymous visitors — are all documented. We found no public information on conflict resolution, account-level or custom objects, sync retry and error logs, API rate limits, or field-level ownership between systems. 1 8 9
The Lifecycle Marketer
Bi-directional flows connect the platform to the data warehouse, cloud storage, CDP, digital properties and backend systems, with identity resolution merging records — including previously unknown users — on email, phone and custom identifiers, and a public developer guide behind the APIs. Zero-copy audiences built directly in the cloud warehouse avoid duplicating data, which is the right instinct for keeping one record in two systems. We found no public information on field-level conflict resolution, account-level objects alongside contacts, or documented API rate limits. 1 8 9
The Solution Architect
Bidirectional flows to warehouses, cloud storage and CDPs with custom field mapping, 180+ turnkey integrations, automated identity resolution on email, phone and custom IDs, and a documented path from anonymous visitor to known customer are exactly the joins I look for. We found no public information on field-level conflict resolution or ownership rules, account-level objects, custom objects, sync retry with an error log, or API rate limits — the places these implementations actually fail. 8 9
The Skeptic
Bi-directional flow with Redshift, Databricks, BigQuery, Snowflake, Azure and S3, custom field mapping, identity resolution merging records on email, phone and custom IDs, and converting previously anonymous visitors into known profiles make the data plumbing genuinely strong. But we found no public information on a connector to a named CRM, on conflict resolution per field, on sync retries and error logs, or on documented API rate limits; the CRM join this criterion turns on is not documented on the captured pages. 8 9
European sovereignty
panel opinion
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily. Dimensions the sources do not establish are unknown, not non-EU.
0 — Proven non-EU: a non-EU vendor and contracting entity with hosting and tracking stated outside the EU.
3 — One European element proven — an EU contracting entity or EU data residency stated — with the rest of the chain undocumented.
5 — An EU contracting entity and EU hosting both stated, and a data processing agreement offered.
8 — EU hosting on named infrastructure, EU contracting entity, a subprocessor list published with locations, and any non-EU processing (tracking, AI scoring, support access) named with its legal basis.
10 — Sovereign end to end and evidenced: every profile, event and derived score processed in the EU by European subprocessors, certification published, and no transfer requiring a Schrems II argument to survive.
The Demand Gen Lead not rated — no public information
We found no public information establishing the contracting entity's jurisdiction, data residency, hosting locations, a published subprocessor list or a data processing agreement. The GDPR FAQ page and the ISO 27001, SOC 2 Type 2 and GDPR compliance claims speak to compliance posture, not to where behavioural profiles of EU residents are processed. 6 7 8
The Sales Ops Manager not rated — no public information
We found no public information establishing where profiles of EU residents are processed, the contracting entity's jurisdiction, hosting or data residency, or a data processing agreement; every sovereignty dimension came back unestablished. The captured legal pages cover cookie consent and GDPR FAQs without naming platform subprocessor locations. 6 7 8
The Data Protection Officer
The contracting entity named on the legal pages is Braze, Inc., described elsewhere as Nasdaq-listed, so the vendor side of the chain is non-EU; data residency, hosting, a processing agreement, transfer impact assessment and subprocessor locations are all unstated on the pages we read, and no European element is established. Given the behavioural profiles of named people this platform processes, the silence across every other dimension is itself the finding. 3 6 8
The Lifecycle Marketer not rated — no public information
We found no public information establishing the contracting entity's jurisdiction, where behavioural profiles and events are hosted, a data processing agreement, or a published subprocessor list with locations. GDPR appears among the vendor's stated certifications and a GDPR FAQ page exists, but a claim of compliance is not evidence of where the profiling happens. 6 7 8
The Solution Architect not rated — no public information
We found no public information on the contracting entity's jurisdiction, hosting location, data residency, a data processing agreement, or subprocessor locations for customer profiles on any page captured. A GDPR FAQ and GDPR compliance claims exist, but nothing establishes where behavioural profiles of EU residents are processed, and given the depth of profiling here I weigh that heavily. 6 7 8
The Skeptic not rated — no public information
We found no public information on where behavioural profiles of EU residents are processed, on the contracting entity's jurisdiction, on hosting locations, on a data processing agreement, or on subprocessors; the sovereignty review marks every dimension unknown. The press release describes the company as Nasdaq-listed, which tells me who the vendor is but nothing about where EU data is processed. 3 7 8
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or a single tier with its contact limit.
5 — Prices per tier public with the billing period and contact limits stated, and which tier includes automation visible.
8 — Every tier priced publicly with contact and volume limits, feature boundaries, overage rates, onboarding costs, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given contact count, send volume and feature set, including overage, additional users and any implementation fee stated outright.
The Demand Gen Lead
The captured pages show a free trial and a Contact Sales button, and we found no public prices, tiers, contact limits or the tier where automation begins. From these pages a buyer cannot compute even a rough annual invoice — for a platform of this class, that is the first thing I want on the table. 1 2
The Sales Ops Manager
The only pricing-adjacent facts on the captured pages are a free trial and a Contact Sales route. We found no public information on tier prices, contact or send limits, or which tier includes automation, so a real annual invoice is not computable from these pages alone. 1 2
The Data Protection Officer
The only commercial information on the pages read is a free trial and a Contact Sales route; we found no public prices, tier structure, contact limits, billing periods, or overage and onboarding terms. A buyer cannot derive any annual invoice from these pages. 1 2
The Lifecycle Marketer
A free trial is offered publicly, but beyond that we found no public information on pricing: no tier prices, contact limits, send-volume costs, overage rates or onboarding fees appear on the captured pages, which point buyers to Contact Sales. A buyer cannot compute an annual invoice from what is published. 1 2
The Solution Architect
No price appears on any page we read; the buying path shown is a free trial and contacting sales. We found no public information on tiers, contact limits, the tier where automation begins, overage rates, or onboarding costs. 1 2
The Skeptic
The entry points shown are 'Contact Sales' and a free trial; we found no public information on prices per tier, contact or send limits, overage rates, or the tier where automation begins. A high-touch SMS onboarding process is described with no cost attached anywhere — exactly the sort of line item I expect to meet again on an invoice. Nothing in the captured pages lets a buyer approximate an annual cost. 1 2 5
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Braze
Is Braze European?
Not determined: the vendor’s pages as captured do not say where Braze is based.
Where does Braze store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Braze have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to Braze?
As of 3 Nov 2026, the panel rates HubSpot Marketing Hub (3/5), ActiveCampaign (Automation) (3/5) and Bloomreach Engagement (3/5) highest among the other 18 Marketing Automation products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Evalanche (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Braze alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 14 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.braze.com Checked 3 Nov 2026 Details →
- 2 Journeys & orchestration — found from sitemap www.braze.com Checked 3 Nov 2026 Details →
- 3 Journeys & orchestration — found from sitemap www.braze.com Checked 3 Nov 2026 Details →
- 4 Channels & personalisation — found from sitemap www.braze.com Checked 3 Nov 2026 Details →
- 5 Channels & personalisation — found from sitemap www.braze.com Checked 3 Nov 2026 Details →
- 6 Consent, tracking & profiling — found from sitemap www.braze.com Checked 3 Nov 2026 Details →
- 7 Consent, tracking & profiling — found from sitemap www.braze.com Checked 3 Nov 2026 Details →
- 8 CRM integration & data model — found from sitemap www.braze.com Checked 3 Nov 2026 Details →
- 9 CRM integration & data model — found from sitemap www.braze.com Checked 3 Nov 2026 Details →