| Customer data | Profiles are ingested and stored through SDKs, APIs and warehouse connections; zero-copy options can use warehouse data without writing it to profiles. | No customer database to import or sync. Notifizz keeps only what sending requires (identifiers, addresses, preferences, delivery history); everything else is read from your systems when the message is built. |
|---|
| Channels | Email, SMS/MMS/RCS, WhatsApp, LINE, KakaoTalk, mobile and web push, in-app messages, Content Cards, Banners, landing pages and webhooks. | Email and Notification Center are available. Web push is in closed beta and Intercom in pilot; SMS and WhatsApp are coming soon. |
|---|
| Live personalization | Connected Content calls an API when the message is rendered, alongside stored profiles. | Enrichers read your systems when the message is built, with a short cache: one hour by default, configurable per source. |
|---|
| Campaign creation | Marketers build campaigns and Canvas journeys in a no-code, drag-and-drop builder; BrazeAI Operator can draft them from a brief. | Marketing and product create in a shared workspace; engineering implements what is missing. |
|---|
| Developer work | Integrate Braze SDKs and data ingestion (REST API or Cloud Data Ingestion); Currents is an optional export of engagement events. | Connect events and enrichers. Reuse existing requirements; implement the missing ones. |
|---|
| Review and versions | An optional approval workflow for campaigns and Canvases, Canvas drafts and Canvas version history. | Editing, Implementation, Review and Live. Nothing goes Live until someone on your team publishes it. New campaigns go through Review first, and so do updates that change a campaign’s logic (event, steps, conditions, recipients, channels or data); text-only edits can be published directly. |
|---|
| Email delivery | Email is sent through Braze’s email service providers (Amazon SES by default for new setups, SendGrid or SparkPost), from dedicated IPs organized in IP pools. | Your own domain, a spam score on Review test sends, and delivery and bounce data from the provider. |
|---|
| Hosting and privacy | Profiles are stored in Braze data centers; EU data centers in Frankfurt are available. | Hosted in the EU (France). US subprocessors: Cloudflare (network), Postmark (email delivery) and Anthropic (AI). The AI designs campaigns from the structure of your events, never their values; a test run you ask it to debug is shared with it. No contact database sync. Suppressed addresses are kept as keyed hashes. |
|---|