Back to Details

sales-braze

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Braze Platform Help

Braze平台使用帮助

Help the user with Braze platform questions — from Canvas Flow journey orchestration and cross-channel campaigns through BrazeAI, Braze Data Platform, segmentation, Catalogs, Feature Flags, and REST API integrations.
为用户解答Braze平台相关问题——覆盖Canvas Flow旅程编排、跨渠道营销活动、BrazeAI、Braze数据平台、用户分群、Catalogs、Feature Flags以及REST API集成等全场景。

Step 1 — Gather context

步骤1 —— 收集上下文信息

Ask the user:
  1. What area of Braze do you need help with?
    • A) Canvas Flow — journey orchestration, multi-step cross-channel flows
    • B) Campaigns — single-send or API-triggered messages
    • C) Email — templates, drag-and-drop editor, Liquid, Connected Content
    • D) Push notifications — iOS, Android, web push, rich push (route to 
      /sales-push-notification
      for cross-platform strategy)
    • E) In-app messages / Content Cards — modals, slideups, persistent cards (route to 
      /sales-in-app-messaging
      for cross-platform strategy)
    • F) SMS / MMS / RCS / WhatsApp / LINE — mobile messaging channels
    • G) BrazeAI — predictive models, generative content, AI agents, Decisioning Studio
    • H) Segmentation — real-time segments, SQL segments, CDI Segments, filters
    • I) Braze Data Platform — Cloud Data Ingestion, Currents streaming, data transformation
    • J) Catalogs — product data, location data, dynamic personalization
    • K) Feature Flags — controlled rollouts, A/B testing features
    • L) Transactional email — dedicated API for time-sensitive 1:1 messages (route to 
      /sales-transactional-email
      for cross-platform)
    • M) Deliverability — domain auth, IP warmup, sender reputation (route to 
      /sales-deliverability
      for cross-platform)
    • N) REST API — endpoints, authentication, rate limits, SDKs
    • O) Integrations — Braze Alloys, CDP connectors, data warehouse sync
    • P) Liquid templating / Connected Content — dynamic personalization
    • Q) Admin — workspaces, API keys, SCIM, permissions, billing
    • R) Migration from Appboy or another platform
    • S) Something else — describe it
  2. What's your role?
    • A) Marketing / CRM / lifecycle marketer
    • B) Growth / product manager
    • C) Developer / engineer
    • D) Data / analytics
    • E) Admin / ops
    • F) Other
  3. What are you trying to accomplish? (describe your specific goal or question)
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.
向用户询问以下信息：
  1. 你需要Braze哪个模块的帮助？
    • A) Canvas Flow —— 旅程编排、多步骤跨渠道流程
    • B) 营销活动 —— 单次发送或API触发的消息
    • C) 邮件 —— 模板、拖拽编辑器、Liquid、Connected Content
    • D) 推送通知 —— iOS、Android、网页推送、富媒体推送（跨平台策略请跳转至
      /sales-push-notification
      ）
    • E) 应用内消息 / Content Cards —— 模态框、滑入消息、常驻卡片（跨平台策略请跳转至
      /sales-in-app-messaging
      ）
    • F) SMS / MMS / RCS / WhatsApp / LINE —— 移动端消息渠道
    • G) BrazeAI —— 预测模型、生成式内容、AI Agent、Decisioning Studio
    • H) 用户分群 —— 实时分群、SQL分群、CDI分群、筛选器
    • I) Braze数据平台 —— 云数据接入、Currents数据流、数据转换
    • J) Catalogs —— 商品数据、位置数据、动态个性化
    • K) Feature Flags —— 灰度发布、功能A/B测试
    • L) 事务性邮件 —— 用于时效型1对1消息的专用API（跨平台场景请跳转至
      /sales-transactional-email
      ）
    • M) 送达率 —— 域名认证、IP预热、发件人信誉（跨平台场景请跳转至
      /sales-deliverability
      ）
    • N) REST API —— 接口、鉴权、限流、SDK
    • O) 集成 —— Braze Alloys、CDP连接器、数仓同步
    • P) Liquid模板 / Connected Content —— 动态个性化
    • Q) 管理员功能 —— 工作空间、API密钥、SCIM、权限、账单
    • R) 从Appboy或其他平台迁移
    • S) 其他内容 —— 请描述具体问题
  2. 你的角色是什么？
    • A) 营销 / CRM / 用户生命周期运营
    • B) 增长 / 产品经理
    • C) 开发 / 工程师
    • D) 数据 / 分析
    • E) 管理员 / 运营
    • F) 其他
  3. 你想要实现什么目标？（描述你的具体需求或问题）
**如果用户的请求已经提供了大部分上下文信息，可以直接跳转到对应步骤。**优先基于合理假设（需明确说明假设内容）给出你能力范围内的最优解答，最后仅补充1-2个最关键的澄清问题即可。

Step 2 — Route or answer directly

步骤2 —— 跳转或直接解答

If the request maps to a specialized skill, route:
  • Push notification strategy → 
    /sales-push-notification
  • In-app messaging strategy → 
    /sales-in-app-messaging
  • Email marketing strategy (opt-in) → 
    /sales-email-marketing
  • Transactional email architecture → 
    /sales-transactional-email
  • Cross-platform deliverability → 
    /sales-deliverability
  • Tool integration architecture → 
    /sales-integration
  • Lead scoring models → 
    /sales-lead-score
  • Live chat / chatbot → 
    /sales-live-chat
  • Loyalty programs → 
    /sales-loyalty
Otherwise, answer directly from platform knowledge using the reference below.
如果用户请求属于其他专用技能的覆盖范围，请引导跳转：
  • 推送通知策略 → 
    /sales-push-notification
  • 应用内消息策略 → 
    /sales-in-app-messaging
  • 邮件营销策略（用户许可式） → 
    /sales-email-marketing
  • 事务性邮件架构 → 
    /sales-transactional-email
  • 跨平台送达率 → 
    /sales-deliverability
  • 工具集成架构 → 
    /sales-integration
  • 线索评分模型 → 
    /sales-lead-score
  • 实时聊天 / 聊天机器人 → 
    /sales-live-chat
  • 会员忠诚度计划 → 
    /sales-loyalty
否则，基于以下平台参考知识库直接解答用户问题。

Step 3 — Braze platform reference

步骤3 —— Braze平台参考指南

Canvas Flow (Journey Orchestration)

Canvas Flow（旅程编排）

  • What it is: Visual drag-and-drop journey builder for multi-step, cross-channel customer experiences
  • Key concepts: Canvas = a journey, Steps = individual actions (message, delay, decision split, experiment, audience sync, action paths, user update), Variants = A/B test branches
  • Channels in Canvas: Email, push (iOS/Android/web), in-app message, Content Card, SMS/MMS, WhatsApp, webhook
  • Triggers: Action-based (user does X), API-triggered, scheduled, event-triggered
  • Branching: Decision Split (filter-based), Action Paths (did user do X within Y time?), Audience Paths (segment membership), Experiment Path (A/B/n testing)
  • Entry controls: Entry schedule (scheduled, action-based, API-triggered), entry limits, rate limiting, re-eligibility, quiet hours
  • Canvas vs Campaign: Use Canvas for multi-step journeys with branching. Use Campaign for simple single-send messages. Canvas supports all channels Campaign does, plus more complex orchestration.
  • Best practices: Start with the simplest Canvas that achieves your goal. Use Decision Splits to personalize, not to create complexity. Set entry limits to prevent over-messaging. Use Experiment Paths to optimize.
  • 定义：可视化拖拽式旅程构建器，用于创建多步骤、跨渠道的客户体验流程
  • 核心概念：Canvas = 一个旅程，步骤 = 单个操作（消息、延迟、决策分支、实验、受众同步、动作路径、用户信息更新），变体 = A/B测试分支
  • Canvas支持的渠道：邮件、推送（iOS/Android/网页）、应用内消息、Content Card、SMS/MMS、WhatsApp、webhook
  • 触发方式：动作触发（用户完成指定行为）、API触发、定时触发、事件触发
  • 分支逻辑：决策分支（基于筛选条件）、动作路径（用户是否在Y时间内完成X行为）、受众路径（分群归属）、实验路径（A/B/n测试）
  • 进入控制：进入调度（定时、动作触发、API触发）、进入限制、流速控制、重入资格、静默时段
  • Canvas与营销活动的区别：需要带分支的多步骤旅程时使用Canvas，简单的单次发送消息使用营销活动。Canvas支持所有营销活动的渠道，还可实现更复杂的编排逻辑
  • 最佳实践：从能实现目标的最简Canvas开始搭建，使用决策分支做个性化而非增加不必要的复杂度，设置进入限制避免过度触达用户，使用实验路径做流程优化

Campaigns

营销活动

  • What it is: Single-step message sends across any channel
  • Types: Scheduled, action-based (event trigger), API-triggered
  • A/B testing: Test subject lines, content, send time, channel — Braze auto-selects winner
  • Multivariate: Up to 8 variants per campaign
  • API-triggered campaigns: 
    POST /campaigns/trigger/send
    — send with dynamic properties
  • Transactional campaigns: Dedicated endpoint for time-sensitive 1:1 messages with SLA guarantees
  • Best practices: Use campaigns for simple one-off sends. Move to Canvas when you need branching, delays, or multi-step logic.
  • 定义：跨任意渠道的单步骤消息发送
  • 类型：定时、动作触发（事件触发）、API触发
  • A/B测试：可测试主题、内容、发送时间、渠道——Braze会自动选择优胜版本
  • 多变量测试：单个营销活动最多支持8个变体
  • API触发营销活动：
    POST /campaigns/trigger/send
    —— 可传入动态属性发送
  • 事务性营销活动：专用接口，用于时效型1对1消息，提供SLA保障
  • 最佳实践：简单的单次发送使用营销活动，当需要分支、延迟或多步骤逻辑时迁移到Canvas

Email

邮件

  • Editor: Drag-and-drop editor, HTML editor, or plain text
  • Templating: Liquid templating engine — 
    {{${first_name}}}
    , conditionals, loops, filters
  • Connected Content: Pull dynamic data from external APIs at send time — 
    {% connected_content https://api.example.com/user/{{${user_id}}} :save response %}
  • Dynamic content: Conditional content blocks based on user attributes, catalog data, or Connected Content
  • AMP for email: Interactive email elements (forms, carousels, accordions)
  • Preference centers: Built-in subscription management UI
  • IP warming: Braze provides dedicated IPs and warmup scheduling assistance
  • Plan gates: AMP, advanced analytics, dedicated IPs available on Pro+
  • 编辑器：拖拽编辑器、HTML编辑器、纯文本编辑器
  • 模板：Liquid模板引擎 —— 
    {{${first_name}}}
    、条件判断、循环、过滤器
  • Connected Content：发送时从外部API拉取动态数据 —— 
    {% connected_content https://api.example.com/user/{{${user_id}}} :save response %}
  • 动态内容：基于用户属性、Catalog数据或Connected Content展示条件内容块
  • AMP for email：交互式邮件元素（表单、轮播、折叠面板）
  • 偏好中心：内置的订阅管理UI
  • IP预热：Braze提供专用IP和预热调度支持
  • 套餐门槛：AMP、高级分析、专用IP仅Pro+套餐可用

Push Notifications

推送通知

  • Platforms: iOS (APNs), Android (FCM), Web (Web Push), Kindle, Huawei
  • Rich push: Images, GIFs, action buttons, custom sounds
  • Push stories: Multi-page carousel push (iOS and Android)
  • Notification channels: Android notification channel management
  • Silent push: Background data sync without user-visible notification
  • Push primers: In-app message asking for push permission before the OS prompt (increases opt-in rates)
  • TTL and priority: Configurable time-to-live and delivery priority
  • Best practices: Always use a push primer before the OS prompt. Segment by push-enabled status. Respect quiet hours.
  • 支持平台：iOS（APNs）、Android（FCM）、网页（Web Push）、Kindle、华为
  • 富媒体推送：图片、GIF、动作按钮、自定义音效
  • 推送故事：多页轮播推送（支持iOS和Android）
  • 通知渠道：Android通知渠道管理
  • 静默推送：后台数据同步，不会展示用户可见的通知
  • 推送授权引导：在系统权限弹窗之前展示应用内消息询问用户推送授权（可提升授权率）
  • TTL与优先级：可配置存活时间和送达优先级
  • 最佳实践：系统权限弹窗之前一定要先展示推送授权引导，按推送授权状态做用户分群，遵守静默时段规则

In-App Messages

应用内消息

  • Types: Modal, Slideup, Fullscreen, HTML Custom, Survey
  • Triggers: Session start, custom event, purchase event, push click, or API
  • Display rules: Show once, show on every session, show after X sessions, show after delay
  • Dark mode: Automatic dark mode support
  • Custom HTML: Full HTML/CSS/JS for complex in-app experiences
  • Best practices: Use for onboarding, feature announcements, surveys, and permission priming. Don't overuse — one in-app message per session max.
  • 类型：模态框、滑入消息、全屏消息、自定义HTML、问卷
  • 触发方式：会话启动、自定义事件、购买事件、推送点击、API
  • 展示规则：仅展示一次、每次会话展示、X次会话后展示、延迟后展示
  • 暗黑模式：自动适配暗黑模式
  • 自定义HTML：支持完整HTML/CSS/JS实现复杂的应用内体验
  • 最佳实践：用于新手引导、功能公告、问卷、权限引导，不要过度使用——单会话最多展示1条应用内消息

Content Cards

Content Cards

  • What it is: Persistent content feed within your app — like a personalized inbox
  • Types: Classic (image + text), Banner (image only), Captioned Image
  • Key difference from in-app: Content Cards persist until dismissed or expired. In-app messages show once and disappear.
  • Use cases: Promotions, personalized recommendations, onboarding checklists, notification center
  • Pinning: Pin important cards to the top of the feed
  • Expiration: Set card expiry (default 30 days)
  • Best practices: Use Content Cards for persistent content users can revisit. Use in-app messages for time-sensitive interruptions.
  • 定义：应用内的常驻内容流——类似个性化收件箱
  • 类型：经典款（图文）、横幅款（仅图片）、带标题图片款
  • 与应用内消息的核心区别：Content Cards会常驻直到被用户关闭或过期，应用内消息仅展示一次就消失
  • 使用场景：促销活动、个性化推荐、新手引导清单、通知中心
  • 置顶：可将重要卡片固定在信息流顶部
  • 过期设置：可设置卡片过期时间（默认30天）
  • 最佳实践：需要用户可回溯的常驻内容使用Content Cards，时效型的弹窗通知使用应用内消息

SMS / MMS / RCS

SMS / MMS / RCS

  • SMS: Two-way messaging, subscription management, keyword handling (STOP, HELP, custom)
  • MMS: Images, GIFs, video, audio in messages
  • RCS: Rich Communication Services — rich media, carousels, suggested actions (Android)
  • Subscription groups: Manage SMS opt-in/opt-out per subscription group
  • Short codes / long codes / toll-free: Configure sender numbers by country
  • Smart encoding: Automatic GSM-7 vs UCS-2 detection
  • Quiet hours: Configurable no-send windows per timezone
  • Plan gates: SMS/RCS available on Pro+ plan
  • SMS：双向消息、订阅管理、关键词处理（STOP、HELP、自定义关键词）
  • MMS：消息可包含图片、GIF、视频、音频
  • RCS：富通信服务——支持富媒体、轮播、建议动作（仅Android）
  • 订阅组：按订阅组管理SMS的订阅/退订
  • 短码 / 长码 / 免费电话：可按国家配置发件号码
  • 智能编码：自动检测GSM-7/UCS-2编码
  • 静默时段：可按时区配置禁发窗口
  • 套餐门槛：SMS/RCS仅Pro+套餐可用

WhatsApp

WhatsApp

  • What it is: WhatsApp Business API messaging via Braze
  • Templates: Must be Meta-approved before sending (24-48hr review)
  • Conversation types: Marketing, utility, service conversations — different pricing per type
  • Media: Images, documents, video, location, interactive buttons/lists
  • Two-way: Receive and respond to user messages within 24hr service window
  • 定义：Braze集成的WhatsApp Business API消息能力
  • 模板：发送前必须经过Meta审核（审核周期24-48小时）
  • 会话类型：营销类、工具类、服务类会话——不同类型定价不同
  • 媒体支持：图片、文档、视频、位置、交互式按钮/列表
  • 双向消息：24小时服务窗口内可接收并回复用户消息

LINE

LINE

  • What it is: LINE messaging for APAC markets (Japan, Taiwan, Thailand, Indonesia)
  • Message types: Text, image, video, sticker, rich menu, flex message
  • Use case: Primary engagement channel for brands with APAC presence
  • 定义：面向亚太市场（日本、中国台湾、泰国、印度尼西亚）的LINE消息能力
  • 消息类型：文本、图片、视频、贴纸、富菜单、flex消息
  • 使用场景：面向亚太地区用户的品牌主要触达渠道

BrazeAI

BrazeAI

  • Predictive Suite: Churn prediction, purchase prediction, event prediction — ML models that score users 0-100
  • Intelligent Timing: Send at the optimal time for each user (learned from behavior)
  • Intelligent Channel: Predict which channel each user is most likely to engage with
  • Intelligent Selection: Automatic A/B test winner selection based on Bayesian optimization
  • AI Copywriting: Generate email/push/SMS copy from prompts
  • AI Image Generation: Create images from text descriptions
  • Decisioning Studio: 1:1 personalization engine — picks the best message/offer per user at send time
  • AI Agents: Autonomous agents that optimize campaigns continuously
  • Plan gates: Predictive Suite requires Pro+. Decisioning Studio requires Enterprise.
  • 预测套件：流失预测、购买预测、事件预测——机器学习模型会给用户打0-100的分数
  • 智能发送时间：基于用户行为学习，为每个用户选择最优发送时间
  • 智能渠道：预测每个用户最可能互动的渠道
  • 智能选择：基于贝叶斯优化自动选择A/B测试优胜版本
  • AI文案生成：基于Prompt生成邮件/推送/SMS文案
  • AI图片生成：基于文本描述生成图片
  • Decisioning Studio：1对1个性化引擎——发送时为每个用户选择最优的消息/优惠
  • AI Agent：可自动持续优化营销活动的自治智能体
  • 套餐门槛：预测套件需要Pro+套餐，Decisioning Studio需要企业版套餐

Braze Data Platform

Braze数据平台

  • Cloud Data Ingestion (CDI): Sync user attributes, events, and purchases from Snowflake, Redshift, BigQuery, Databricks, or Microsoft Fabric directly into Braze
  • CDI Segments: Build segments directly from warehouse data without importing (zero-copy)
  • Currents: Real-time event streaming — export engagement events (opens, clicks, purchases, custom events) to data warehouses, CDPs, or analytics tools
  • Currents destinations: Amazon S3, Azure Blob Storage, Google Cloud Storage, Snowflake, Segment, mParticle, Amplitude, Mixpanel, Treasure Data
  • Data transformation: Transform incoming webhook data before ingesting into Braze
  • Connected Content: Pull external data into messages at send time via HTTP API calls
  • 云数据接入（CDI）：将Snowflake、Redshift、BigQuery、Databricks、Microsoft Fabric中的用户属性、事件、购买数据直接同步到Braze
  • CDI分群：无需导入数据，直接基于数仓数据构建用户分群（零拷贝）
  • Currents：实时事件流——将互动事件（打开、点击、购买、自定义事件）导出到数仓、CDP或分析工具
  • Currents支持的目的地：Amazon S3、Azure Blob Storage、Google Cloud Storage、Snowflake、Segment、mParticle、Amplitude、Mixpanel、Treasure Data
  • 数据转换：接入Braze前可对传入的webhook数据做转换
  • Connected Content：发送时通过HTTP API调用将外部数据拉取到消息中

Segmentation

用户分群

  • Real-time segments: Auto-updating based on user attributes, behavior, events, purchases
  • Filters: 50+ filter types — demographics, behavior, engagement, custom events, purchase history, location, technology
  • SQL Segment Extensions: Write SQL queries against your warehouse (CDI Segments) to build segments
  • Predictive segments: Based on BrazeAI predictions (churn risk, purchase likelihood)
  • Segment Analytics: Size, growth, engagement overlap
  • Best practices: Start with behavioral segments (what users did), not just demographic (who they are). Layer engagement recency to keep segments fresh.
  • 实时分群：基于用户属性、行为、事件、购买记录自动更新
  • 筛选器：50+种筛选类型——人口属性、行为、互动、自定义事件、购买历史、位置、技术属性
  • SQL分群扩展：可针对数仓（CDI分群）编写SQL查询构建分群
  • 预测分群：基于BrazeAI的预测结果（流失风险、购买可能性）构建
  • 分群分析：规模、增长、互动重叠度
  • 最佳实践：优先基于行为分群（用户做了什么）而非仅基于人口属性分群（用户是谁），叠加互动时效性维度保持分群有效性

Catalogs

Catalogs

  • What it is: Store non-user data (products, promotions, locations, restaurants, events) in Braze for personalization
  • Use cases: Product recommendations, location-based content, dynamic promotion cards, personalized menus
  • Access in Liquid: 
    {% catalog_items your_catalog_name {{${user_attribute}}} %}
  • API management: Create, update, delete catalog items via REST API
  • Limits: Up to 100 catalogs, 100M items across all catalogs
  • 定义：在Braze中存储非用户数据（商品、促销、位置、餐厅、活动）用于个性化
  • 使用场景：商品推荐、LBS内容、动态促销卡片、个性化菜单
  • Liquid中调用方式：
    {% catalog_items your_catalog_name {{${user_attribute}}} %}
  • API管理：可通过REST API创建、更新、删除Catalog条目
  • 限制：最多100个Catalog，所有Catalog总条目最多1亿条

Feature Flags

Feature Flags

  • What it is: Control feature visibility and rollout without code deploys
  • Use cases: Gradual rollouts, A/B test features, kill switches, user-segment-targeted features
  • Canvas integration: Enable/disable features as a Canvas step
  • Properties: Attach key-value properties to feature flags for configuration
  • 定义：无需部署代码即可控制功能可见性和发布节奏
  • 使用场景：灰度发布、功能A/B测试、开关、面向指定用户分群开放功能
  • Canvas集成：可作为Canvas步骤启用/禁用功能
  • 属性：可给Feature Flags附加键值对属性用于配置

Transactional Email

事务性邮件

  • Endpoint: 
    POST /transactional/v1/campaigns/{campaign_id}/send
  • Purpose: Time-sensitive 1:1 emails (password resets, order confirmations, OTP)
  • SLA: Designed for high reliability with delivery guarantees
  • Separate from marketing: Transactional campaigns don't count against marketing rate limits
  • 接口：
    POST /transactional/v1/campaigns/{campaign_id}/send
  • 用途：时效型1对1邮件（密码重置、订单确认、一次性验证码）
  • SLA：高可靠性设计，提供送达保障
  • 与营销类隔离：事务性营销活动不计入营销类限流额度

Data model quick reference

数据模型速查表

ObjectKey fieldsNotes
Userexternal_id, email, phone, attributes, events, purchasesCentral entity — all engagement ties to users
Campaignname, channel, schedule, segments, messagesSingle-step message send
Canvasname, steps, variants, entry_schedule, tagsMulti-step journey orchestration
Segmentname, filtersAuto-updating audience
Content Cardtitle, description, image, url, extras, expirationPersistent in-app content
Catalogname, fields, itemsNon-user data for personalization
Subscription Groupname, type (email/SMS), statusOpt-in/opt-out management per channel
Currentsconnector_type, destination, eventsReal-time event streaming export
Feature Flagid, name, enabled, propertiesControlled feature rollout
对象核心字段说明
用户external_id, email, phone, attributes, events, purchases核心实体——所有互动行为都关联到用户
营销活动name, channel, schedule, segments, messages单步骤消息发送
Canvasname, steps, variants, entry_schedule, tags多步骤旅程编排
分群name, filters自动更新的受众群体
Content Cardtitle, description, image, url, extras, expiration常驻应用内内容
Catalogname, fields, items用于个性化的非用户数据
订阅组name, type (email/SMS), status按渠道管理订阅/退订
Currentsconnector_type, destination, events实时事件流导出
Feature Flagid, name, enabled, properties可控的功能发布

API quick reference

API速查表

  • Base URL: 
    https://rest.{instance}.braze.com
    (instance-specific — check dashboard for yours)
  • Auth: 
    Authorization: Bearer YOUR_REST_API_KEY
  • Rate limit: 250,000 requests/hour default
  • Key endpoints: 
    /users/track
    , 
    /users/export/ids
    , 
    /messages/send
    , 
    /campaigns/trigger/send
    , 
    /canvas/trigger/send
    , 
    /catalogs
    , 
    /templates/email/create
    , 
    /segments/list
  • SDKs: iOS, Android, Web (JS), React Native, Flutter, Unity, Roku, Unreal Engine
  • Full reference: See 
    references/braze-api-reference.md
  • 基础URL：
    https://rest.{instance}.braze.com
    （实例专属——可在后台查看你的地址）
  • 鉴权：
    Authorization: Bearer YOUR_REST_API_KEY
  • 限流：默认每小时25万次请求
  • 核心接口：
    /users/track
    、
    /users/export/ids
    、
    /messages/send
    、
    /campaigns/trigger/send
    、
    /canvas/trigger/send
    、
    /catalogs
    、
    /templates/email/create
    、
    /segments/list
  • SDK：iOS、Android、Web (JS)、React Native、Flutter、Unity、Roku、Unreal Engine
  • 完整参考：查看
    references/braze-api-reference.md

Integrations (Braze Alloys)

集成（Braze Alloys）

  • CDPs: Segment, mParticle, Tealium, Rudderstack, Census, Hightouch, Amperity, Amplitude
  • Data warehouses: Snowflake (bidirectional), Redshift, BigQuery, Databricks, Microsoft Fabric
  • Analytics: Mixpanel, Amplitude, Looker, Tableau
  • Attribution: Adjust, AppsFlyer, Branch, Kochava, Singular
  • CRM: Salesforce (via partners/Zapier)
  • E-commerce: Shopify, Talon.One, Voucherify
  • Total: 140+ technology partnerships
  • CDP：Segment、mParticle、Tealium、Rudderstack、Census、Hightouch、Amperity、Amplitude
  • 数仓：Snowflake（双向同步）、Redshift、BigQuery、Databricks、Microsoft Fabric
  • 分析工具：Mixpanel、Amplitude、Looker、Tableau
  • 归因工具：Adjust、AppsFlyer、Branch、Kochava、Singular
  • CRM：Salesforce（通过合作伙伴/Zapier）
  • 电商：Shopify、Talon.One、Voucherify
  • 总数：140+技术合作伙伴

Step 4 — Actionable guidance

步骤4 —— 可落地的指导建议

Based on the user's area, provide:
  1. Step-by-step instructions — exact Braze UI paths or API calls
  2. Configuration recommendations — settings, plan considerations, gotchas
  3. Verification steps — how to confirm the setup works
  4. Next steps — what to do after the immediate task
根据用户的需求场景，提供以下内容：
  1. 分步操作指南——明确的Braze后台操作路径或API调用方式
  2. 配置建议——设置项、套餐注意事项、常见陷阱
  3. 验证步骤——如何确认配置生效
  4. 后续步骤——完成当前任务后的下一步操作建议

Common setup workflows

常用配置工作流

First-time setup checklist:
  1. Configure SDK integration (iOS/Android/Web) — install SDK, set API key and endpoint
  2. Set up user identification — 
    changeUser()
    with external_id
  3. Track custom events and attributes — define your event taxonomy
  4. Set up email domain authentication (SPF/DKIM/DMARC)
  5. Configure push credentials (APNs certificate, FCM key)
  6. Create your first segment based on user behavior
  7. Build a simple campaign to test each channel
  8. Set up Currents for data export (if needed)
Canvas Flow quickstart:
  1. Dashboard → Messaging → Canvas → Create Canvas
  2. Set entry schedule (action-based, scheduled, or API-triggered)
  3. Add entry audience (segment or filters)
  4. Build flow: add message steps, delays, decision splits
  5. Add variants for A/B testing if desired
  6. Set conversion events to track success
  7. Review, test with internal users, then launch
API key setup:
  1. Dashboard → Settings → APIs and Identifiers
  2. Create New API Key — name it descriptively
  3. Select only the permissions this key needs (principle of least privilege)
  4. Note your REST endpoint (instance-specific URL)
  5. Test: 
    curl -H "Authorization: Bearer YOUR_KEY" https://rest.{instance}.braze.com/users/export/ids -d '{"external_ids": ["test_user"]}'
首次搭建检查清单：
  1. 配置SDK集成（iOS/Android/Web）——安装SDK，设置API密钥和端点
  2. 设置用户标识——传入external_id调用
    changeUser()
  3. 埋点自定义事件和属性——定义你的事件分类体系
  4. 配置邮件域名认证（SPF/DKIM/DMARC）
  5. 配置推送凭证（APNs证书、FCM密钥）
  6. 基于用户行为创建你的第一个分群
  7. 搭建简单的营销活动测试每个渠道
  8. 配置Currents用于数据导出（如果需要）
Canvas Flow快速入门：
  1. 后台 → 消息中心 → Canvas → 创建Canvas
  2. 设置进入调度（动作触发、定时或API触发）
  3. 设置进入受众（分群或筛选条件）
  4. 搭建流程：添加消息步骤、延迟、决策分支
  5. 如果需要A/B测试添加对应变体
  6. 设置转化事件用于衡量效果
  7. 审核流程，用内部用户测试，然后正式发布
API密钥配置：
  1. 后台 → 设置 → API与标识
  2. 创建新API密钥——设置清晰的描述性名称
  3. 仅勾选该密钥需要的权限（最小权限原则）
  4. 记录你的REST端点（实例专属URL）
  5. 测试：
    curl -H "Authorization: Bearer YOUR_KEY" https://rest.{instance}.braze.com/users/export/ids -d '{"external_ids": ["test_user"]}'

Gotchas

常见陷阱

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  1. Instance-specific endpoints: Braze has 10+ regional instances (US-01 through US-10, EU-01/02, AU-01, etc.). Using the wrong instance URL for your API calls will silently fail. Always check your dashboard for the correct REST endpoint.
  2. Canvas vs Campaign confusion: Braze has both "Campaigns" (single-step) and "Canvas" (multi-step). Users asking about "sequences" or "journeys" want Canvas, not Campaign. Users asking about "blasts" or "one-time sends" want Campaign.
  3. MAU-based pricing can spike unexpectedly: Braze charges by Monthly Active Users, not contacts. If you run a reactivation campaign that wakes up dormant users, your MAU count (and bill) will increase. Warn users about this when designing win-back campaigns.
  4. Liquid vs Handlebars: Braze uses Liquid templating (like Shopify), NOT Handlebars (like SendGrid/Postmark). Syntax is 
    {{${first_name}}}
    not 
    {{first_name}}
    . The double-dollar-sign wrapping is Braze-specific Liquid.
  5. Connected Content rate limits: Connected Content API calls happen at send time. If you send to 1M users and each message calls an external API, that's 1M API calls to your server. Implement caching (
    {% connected_content ... :cache_max_age 300 %}
    ) and ensure your API can handle the load.
基于调研整理的最佳实践——请留意这些内容，尤其是套餐限制功能和集成相关的过时问题。
  1. 实例专属端点：Braze有10+区域实例（US-01到US-10、EU-01/02、AU-01等），API调用使用错误的实例URL会无提示失败，一定要在后台确认正确的REST端点地址。
  2. Canvas与营销活动混淆：Braze同时有「营销活动（单步骤）」和「Canvas（多步骤）」两个功能，用户询问「序列」或「旅程」时对应Canvas而非营销活动，用户询问「群发」或「单次发送」时对应营销活动。
  3. MAU定价可能意外上涨：Braze按月活用户数收费而非联系人数量，如果你运行的召回活动唤醒了沉睡用户，你的MAU数值（和账单）会上涨。设计召回活动时要提醒用户注意该风险。
  4. Liquid与Handlebars的区别：Braze使用Liquid模板（和Shopify一致），而非Handlebars（和SendGrid/Postmark一致）。语法是
    {{${first_name}}}
    而非
    {{first_name}}
    ，双美元符包裹是Braze特有的Liquid语法。
  5. Connected Content限流：Connected Content API调用在发送时执行，如果你给100万用户发消息且每条消息都调用外部API，就会向你的服务器发起100万次API请求。请实现缓存（
    {% connected_content ... :cache_max_age 300 %}
    ）并确保你的API能承受对应负载。

Step 5 — Related skills

步骤5 —— 相关技能

  • /sales-push-notification
    — Push notification strategy across platforms
  • /sales-in-app-messaging
    — In-app messaging and content card strategy across platforms
  • /sales-email-marketing
    — Opt-in email marketing strategy across platforms
  • /sales-transactional-email
    — Transactional/triggered email delivery strategy
  • /sales-deliverability
    — Cross-platform email deliverability (SPF/DKIM/DMARC, warmup, reputation)
  • /sales-integration
    — Connect Braze with data warehouses, CDPs, and other tools
  • /sales-live-chat
    — Live chat and chatbot strategy
  • /sales-loyalty
    — Customer loyalty program design
  • /sales-lead-score
    — Lead/engagement scoring models
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install: 
    npx skills add sales-skills/sales --skills sales-do
  • /sales-push-notification
    —— 跨平台推送通知策略
  • /sales-in-app-messaging
    —— 跨平台应用内消息和Content Card策略
  • /sales-email-marketing
    —— 跨平台许可式邮件营销策略
  • /sales-transactional-email
    —— 事务性/触发式邮件送达策略
  • /sales-deliverability
    —— 跨平台邮件送达率优化（SPF/DKIM/DMARC、预热、信誉管理）
  • /sales-integration
    —— 对接Braze与数仓、CDP和其他工具
  • /sales-live-chat
    —— 实时聊天和聊天机器人策略
  • /sales-loyalty
    —— 客户忠诚度计划设计
  • /sales-lead-score
    —— 线索/互动评分模型
  • /sales-do
    —— 不确定用哪个技能？该路由可匹配任意销售目标到对应技能。安装命令：
    npx skills add sales-skills/sales --skills sales-do

Examples

示例

Example 1: Building an onboarding Canvas

示例1：搭建新手引导Canvas

User says: "How do I create a 7-day onboarding journey in Braze for new app users?" Skill does: Guides through creating a Canvas with action-based entry (session start, first time = true) → Day 0 welcome push + in-app → Day 1 email with getting started guide → Day 3 Decision Split (completed setup? yes → feature highlight Content Card, no → reminder push) → Day 7 survey in-app message. Includes setting conversion events and A/B variant setup. Result: Complete onboarding Canvas with branching, multi-channel messages, and success metrics
用户提问：「我要怎么在Braze里给新应用用户创建一个7天的新手引导旅程？」 技能响应：指导用户创建Canvas，设置动作触发进入（会话启动、首次访问=是）→ 第0天欢迎推送+应用内消息 → 第1天发送带入门指南的邮件 → 第3天决策分支（是否完成注册？是→发送功能亮点Content Card，否→发送提醒推送）→ 第7天发送应用内问卷。包含转化事件设置和A/B变体配置指导。 结果：包含分支逻辑、多渠道消息和成功指标的完整新手引导Canvas

Example 2: Setting up Currents data export

示例2：配置Currents数据导出

User says: "I need to stream Braze engagement events to our Snowflake data warehouse" Skill does: Walks through Dashboard → Data Settings → Currents → Create New Current → Snowflake → configure connection credentials, select events to stream (email opens, push clicks, in-app impressions, purchases), set data format. Explains the Snowflake Data Sharing alternative for zero-ETL access. Result: Real-time engagement data flowing from Braze to Snowflake
用户提问：「我需要把Braze的互动事件流式同步到我们的Snowflake数仓」 技能响应：引导用户操作：后台 → 数据设置 → Currents → 创建新Current → 选择Snowflake → 配置连接凭证，选择要同步的事件（邮件打开、推送点击、应用内曝光、购买），设置数据格式。说明零ETL访问的Snowflake数据共享替代方案。 结果：Braze的实时互动数据持续流入Snowflake

Example 3: Using Connected Content for personalized recommendations

示例3：使用Connected Content实现个性化推荐

User says: "How do I pull product recommendations from our API into Braze email at send time?" Skill does: Shows Connected Content syntax: 
{% connected_content https://api.example.com/recs/{{${user_id}}} :save recs :cache_max_age 900 %}
→ iterate with 
{% for item in recs.products %}
→ build product cards in email. Covers error handling (
{% if connected_content_status == 200 %}
), caching, and load testing. Result: Dynamically personalized product recommendation emails pulling from external API
用户提问：「我要怎么在发送Braze邮件时从我们的API拉取商品推荐？」 技能响应：展示Connected Content语法：
{% connected_content https://api.example.com/recs/{{${user_id}}} :save recs :cache_max_age 900 %}
→ 使用
{% for item in recs.products %}
循环 → 在邮件中构建商品卡片。覆盖错误处理（
{% if connected_content_status == 200 %}
）、缓存和压测相关内容。 结果：可从外部API拉取数据的动态个性化商品推荐邮件

Troubleshooting

故障排查

Canvas not sending to expected audience

Canvas没有向预期受众发送消息

Symptom: Canvas shows 0 entries or far fewer users than expected Cause: Entry audience filters too restrictive, rate limiting too aggressive, re-eligibility disabled, or entry schedule not matching expected trigger Solution: 1) Check entry audience — preview the segment size. 2) Verify the trigger event is actually firing (check user profile event log). 3) Check rate limiting settings. 4) Ensure re-eligibility is enabled if users should enter multiple times. 5) For API-triggered Canvas, verify the API call includes the correct 
canvas_id
.
症状：Canvas显示0条进入记录或远少于预期的用户数 原因：进入受众筛选条件太严格、流速限制太严格、重入资格未开启、进入调度与预期触发方式不匹配 解决方案：1）检查进入受众——预览分群规模。2）确认触发事件确实在上报（查看用户档案的事件日志）。3）检查流速限制设置。4）如果用户需要多次进入Canvas，确认已开启重入资格。5）API触发的Canvas要确认API调用包含正确的
canvas_id
。

Push notifications not delivering

推送通知无法送达

Symptom: Push campaigns show sends but low/zero deliveries Cause: Invalid push tokens, expired APNs certificate, incorrect FCM key, or users unsubscribed Solution: 1) Check push token validity in user profiles. 2) Verify APNs certificate or FCM key in Dashboard → Settings → App Settings. 3) Check push subscription status — filter segment by "Push Enabled". 4) For iOS, ensure push primer was shown and user accepted. 5) Test with a known-good device first.
症状：推送营销活动显示已发送但送达率极低/为0 原因：推送token无效、APNs证书过期、FCM密钥错误、用户已退订推送 解决方案：1）在用户档案中检查推送token有效性。2）在后台 → 设置 → 应用设置中确认APNs证书或FCM密钥正确。3）检查推送订阅状态——分群筛选「推送已启用」的用户。4）iOS端要确认已展示推送授权引导且用户已同意。5）先用已知可用的设备测试。

Connected Content returning errors

Connected Content返回错误

Symptom: Emails rendering with blank personalization or error fallbacks Cause: External API unreachable at send time, rate limited, or returning unexpected format Solution: 1) Test the API URL manually with a sample user_id. 2) Add error handling: 
{% if connected_content_status == 200 %}
. 3) Add caching: 
:cache_max_age 300
to reduce API calls. 4) Ensure your API can handle the send volume (1 call per recipient). 5) Add a fallback: 
{% else %}Default content here{% endif %}
.
症状：邮件渲染的个性化内容为空或展示错误 fallback 原因：发送时外部API无法访问、触发限流、返回格式不符合预期 解决方案：1）用示例user_id手动测试API URL。2）添加错误处理：
{% if connected_content_status == 200 %}
。3）添加缓存：
:cache_max_age 300
减少API调用次数。4）确认你的API能承受发送量级（每个收件人1次调用）。5）添加 fallback 内容：
{% else %}默认内容{% endif %}
。