Back to Details

sales-iterable

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Iterable Platform Help

Iterable 平台帮助

Help the user with Iterable platform questions — from Studio journey creation and campaign configuration through channel setup (email, SMS, push, in-app, web push, WhatsApp), AI features, data integration, experiments, and API usage.
为用户解答Iterable平台相关问题——涵盖Studio旅程创建、营销活动配置、渠道设置（邮件、SMS、推送、应用内、网页推送、WhatsApp）、AI功能、数据集成、实验、API使用等全场景。

Step 1 — Gather context

步骤1——收集上下文

Ask the user:
  1. What area do you need help with?
    • A) Studio — journey workflows, tiles, branching, delays
    • B) Campaigns — single-send or triggered messages
    • C) Email — templates, dynamic content, editor
    • D) SMS/MMS — setup, two-way, media messages
    • E) Push notifications — iOS, Android, web push
    • F) In-app messages — modals, banners, Mobile Inbox, Embedded Messages
    • G) WhatsApp — template setup, message types
    • H) Experiments — A/B testing, multivariate
    • I) AI features — Brand Affinity, STO, Frequency Optimization, Journey Assist
    • J) Data — Smart Ingest, Snowflake, Catalog, user profiles, events
    • K) Segmentation — audiences, filters, dynamic lists
    • L) Integrations — webhooks, API, Zapier, third-party
    • M) Analytics & reporting — campaign performance, engagement
    • N) Something else — describe it
  2. What's your role?
    • A) Marketer / campaign manager
    • B) Developer / engineer
    • C) Data / analytics
    • D) Marketing ops / admin
  3. What's the goal?
    • A) Set something up for the first time
    • B) Optimize or improve existing setup
    • C) Troubleshoot a problem
    • D) Understand how something works
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. 你需要哪个领域的帮助？
    • A) Studio——旅程工作流、组件、分支、延迟设置
    • B) 营销活动——单次发送或触发式消息
    • C) 邮件——模板、动态内容、编辑器
    • D) SMS/MMS——设置、双向通讯、媒体消息
    • E) 推送通知——iOS、Android、网页推送
    • F) 应用内消息——弹窗、横幅、移动收件箱、嵌入式消息
    • G) WhatsApp——模板设置、消息类型
    • H) 实验——A/B测试、多变量测试
    • I) AI功能——Brand Affinity、STO、频次优化、Journey Assist
    • J) 数据——Smart Ingest、Snowflake、目录、用户档案、事件
    • K) 分群——受众、筛选器、动态列表
    • L) 集成——webhook、API、Zapier、第三方工具
    • M) 分析与报表——营销活动表现、用户互动
    • N) 其他——请描述
  2. 你的角色是什么？
    • A) 营销人员/活动运营
    • B) 开发/工程师
    • C) 数据/分析人员
    • D) 营销运营/管理员
  3. 你的目标是什么？
    • A) 首次搭建相关功能
    • B) 优化现有配置
    • C) 排查问题
    • D) 了解功能用法
如果用户的请求已经提供了大部分上下文，可以直接跳转到对应步骤。 优先基于合理假设（需明确说明假设内容）给出尽可能完善的回答，最后仅补充1-2个最关键的澄清问题即可。

Step 2 — Route or answer directly

步骤2——分流或直接解答

If the question is about general strategy rather than Iterable-specific config, route to the appropriate skill:
Question typeRoute to
Email marketing strategy (not Iterable-specific)
/sales-email-marketing
Push notification strategy across tools
/sales-push-notification
In-app messaging strategy across tools
/sales-in-app-messaging
Transactional email provider comparison
/sales-transactional-email
SPF/DKIM/DMARC setup across tools
/sales-deliverability
Connecting Iterable to CRM via Zapier/Make
/sales-integration
Otherwise, answer directly with Iterable-specific guidance below.
如果问题属于通用策略而非Iterable专属配置，请引导到对应的技能：
问题类型分流到
邮件营销策略（非Iterable专属）
/sales-email-marketing
跨工具推送通知策略
/sales-push-notification
跨工具应用内消息策略
/sales-in-app-messaging
事务性邮件服务商对比
/sales-transactional-email
跨工具SPF/DKIM/DMARC设置
/sales-deliverability
通过Zapier/Make对接Iterable和CRM
/sales-integration
否则，参考下方Iterable专属指南直接解答。

Step 3 — Iterable platform reference

步骤3——Iterable平台参考

Studio (Journey Builder)

Studio（旅程构建器）

Studio is Iterable's visual journey orchestration tool. Key concepts:
  • Journey tiles: Send (email, push, SMS, in-app, WhatsApp, web push), Delay, Filter, Experiment, Update User Profile, Webhook, Create Event, A/B Split
  • Entry sources: List-triggered, event-triggered (custom events, purchases), segment-triggered, API-triggered
  • Branching: Filter tiles split users by attributes, events, or channel engagement. Use "Has received" / "Has opened" / "Has clicked" filters for engagement-based routing.
  • Delays: Fixed (wait X hours/days) or dynamic (wait until specific date field)
  • Exit criteria: Define conditions that remove users from the journey (e.g., purchase made, unsubscribed)
  • Journey Assist (AI): Describe a journey in natural language → Iterable generates the workflow. Review and refine before activating.
  • Lifecycle journeys: Welcome → onboarding → activation → retention → winback. Each as a separate Studio journey with entry/exit criteria.
Studio是Iterable的可视化旅程编排工具，核心概念：
  • 旅程组件：发送（邮件、推送、SMS、应用内、WhatsApp、网页推送）、延迟、筛选、实验、更新用户档案、Webhook、创建事件、A/B分流
  • 进入源：列表触发、事件触发（自定义事件、购买）、分群触发、API触发
  • 分支逻辑：筛选组件可根据用户属性、事件或渠道互动情况拆分用户，可使用「已接收」/「已打开」/「已点击」筛选器实现基于互动的分流
  • 延迟设置：固定延迟（等待X小时/天）或动态延迟（等待到指定日期字段的时间）
  • 退出条件：定义将用户移出旅程的条件（例：完成购买、取消订阅）
  • Journey Assist（AI）：用自然语言描述旅程需求，Iterable自动生成工作流，激活前可审核和调整
  • 生命周期旅程：欢迎→新用户引导→激活→留存→召回，每个阶段作为独立的Studio旅程设置独立的进入/退出条件

Campaigns

营销活动

  • Blast campaigns: One-time sends to a list or segment
  • Triggered campaigns: Fired by API call, custom event, or purchase event
  • Proof campaigns: Test sends to internal list before launching
  • Recurring campaigns: Scheduled to repeat daily/weekly/monthly
  • Multi-channel: A single campaign can target email, push, SMS, in-app, web push, or WhatsApp
  • 批量推送活动：向列表或分群一次性发送消息
  • 触发式活动：通过API调用、自定义事件或购买事件触发发送
  • 测试活动：正式上线前向内部列表发送测试消息
  • 周期性活动：按日/周/月定时重复发送
  • 多渠道：单个活动可覆盖邮件、推送、SMS、应用内、网页推送或WhatsApp渠道

Channels

渠道

ChannelKey capabilities
EmailDrag-and-drop editor, HTML editor, dynamic content with Handlebars, AMP email, snippets (reusable content blocks), preview/test across clients
SMS/MMSTwo-way messaging, media-rich (images, GIFs), keyword opt-in/out, short codes and long codes, quiet hours
Push (iOS/Android)Rich push (images, action buttons, sounds), deep linking, silent push for background data sync, push action buttons
Web pushChrome, Firefox, Opera, Safari via FCM. Browser permission prompt, icon/image support
In-app messagesCenter, top, bottom, full placement. Custom HTML/CSS. Trigger on app open, custom event, or journey
Mobile InboxPersistent message list — users browse, read, delete. Messages stay until expiry or dismissal. Similar to Braze Content Cards
Embedded MessagesInline native content — no overlay or popup. Renders in your app's native UI. Requires SDK integration
WhatsAppMarketing, Utility, Service message types. Quick reply buttons, CTA buttons. Meta-approved templates required
渠道核心能力
邮件拖拽编辑器、HTML编辑器、基于Handlebars的动态内容、AMP邮件、片段（可复用内容块）、跨客户端预览/测试
SMS/MMS双向消息、富媒体（图片、GIF）、关键词订阅/退订、短码/长码、静默时段设置
推送（iOS/Android）富推送（图片、操作按钮、音效）、深度链接、用于后台数据同步的静默推送、推送操作按钮
网页推送通过FCM支持Chrome、Firefox、Opera、Safari，支持浏览器权限申请、图标/图片展示
应用内消息居中、顶部、底部、全屏展示位置，支持自定义HTML/CSS，可通过应用打开、自定义事件或旅程触发
移动收件箱持久化消息列表，用户可浏览、阅读、删除，消息到期或用户主动删除前保留，类似Braze Content Cards
嵌入式消息行内原生内容，无覆盖层或弹窗，在应用原生UI中渲染，需要SDK集成
WhatsApp支持营销、实用工具、服务三类消息，支持快速回复按钮、CTA按钮，需使用Meta审核通过的模板

Iterable AI Suite

Iterable AI套件

FeatureWhat it does
Brand AffinityScores each user's engagement level (Loyal, Positive, Neutral, Negative, Never Engaged). Use as segmentation filter or journey branch condition
Send Time Optimization (STO)Per-user optimal send time based on historical engagement. Enable per campaign or journey step
Frequency OptimizationAI-chosen cap on messages per user per channel per time window. Prevents over-messaging
Predictive GoalsPredict likelihood of user taking a specific action (purchase, churn, etc.) within a time window
Journey AssistNatural language → Studio journey. Describe what you want, AI generates the workflow
Copy AssistAI-generated subject lines and email copy suggestions
Smart SegmentationAI-suggested segments based on user behavior patterns
功能作用
Brand Affinity为每个用户的互动水平打分（忠诚、积极、中立、消极、从未互动），可作为分群筛选条件或旅程分支条件
Send Time Optimization (STO)基于历史互动数据为每个用户计算最优发送时间，可按活动或旅程步骤开启
Frequency OptimizationAI自动为每个用户设置各渠道单位时间内的消息发送上限，避免过度发送
Predictive Goals预测用户在指定时间窗口内完成特定动作（购买、流失等）的概率
Journey Assist自然语言转Studio旅程，描述需求后AI自动生成工作流
Copy AssistAI生成邮件主题和文案建议
Smart SegmentationAI基于用户行为模式推荐分群

Data & Integration

数据与集成

Smart Ingest (co-built with Hightouch):
  • Sync from 23+ data sources: Snowflake, BigQuery, Redshift, Databricks, PostgreSQL, S3, and more
  • Sync types: Users, Events, Catalog items, Lists
  • Frequency: Up to every 15 minutes
  • Configure in Iterable dashboard under Integrations > Smart Ingest
Snowflake Secure Data Sharing:
  • Export Iterable data (user profiles, campaign data, events) to your Snowflake account
  • Join Iterable data with your warehouse data for BI/analytics
  • No ETL required — uses Snowflake's native data sharing
Catalog:
  • Store product data, content, recommendations in Iterable
  • Reference catalog items in templates for dynamic product recommendations
  • Sync via Smart Ingest or API (
    POST /api/catalogs/{catalogName}/items
    )
User profiles & events:
  • Update users: 
    POST /api/users/update
    with 
    email
    or 
    userId
    + 
    dataFields
  • Track events: 
    POST /api/events/track
    with 
    eventName
    + 
    dataFields
  • Bulk operations: 
    POST /api/users/bulkUpdate
    , 
    POST /api/events/trackBulk
    (rate limit: 10 req/s)
Smart Ingest（与Hightouch联合打造）：
  • 支持同步23+数据源：Snowflake、BigQuery、Redshift、Databricks、PostgreSQL、S3等
  • 同步类型：用户、事件、目录项、列表
  • 同步频率：最快每15分钟一次
  • 配置入口：Iterable控制台的集成 > Smart Ingest
Snowflake安全数据共享：
  • 可将Iterable数据（用户档案、活动数据、事件）导出到你的Snowflake账户
  • 可将Iterable数据与数仓数据关联用于BI/分析
  • 无需ETL，基于Snowflake原生数据共享能力实现
目录：
  • 在Iterable中存储商品数据、内容、推荐信息
  • 可在模板中引用目录项实现动态商品推荐
  • 可通过Smart Ingest或API（
    POST /api/catalogs/{catalogName}/items
    ）同步
用户档案与事件：
  • 更新用户：
    POST /api/users/update
    ，需传入
    email
    或
    userId
    + 
    dataFields
  • 事件埋点：
    POST /api/events/track
    ，需传入
    eventName
    + 
    dataFields
  • 批量操作：
    POST /api/users/bulkUpdate
    、
    POST /api/events/trackBulk
    （限流：10次请求/秒）

Data model

数据模型

ObjectKey fieldsNotes
User
email
, 
userId
, 
dataFields
(custom attributes), 
phoneNumber
email
or 
userId
is the primary identifier
Event
email
/
userId
, 
eventName
, 
dataFields
, 
createdAt
Custom events power triggers and segmentation
Campaign
id
, 
name
, 
type
(blast/triggered/recurring), 
messageMedium
One campaign = one channel
List
id
, 
name
, 
listType
(static/dynamic)		Static: manual membership. Dynamic: rule-based
Catalog
catalogName
, items with custom fields		Product data for personalization
Template
templateId
, 
name
, 
messageMedium
Email, push, SMS, in-app, web push templates
Experiment
experimentId
, variants, metrics		A/B or multivariate testing
对象核心字段说明
用户
email
、
userId
、
dataFields
（自定义属性）、
phoneNumber
email
或
userId
为主键
事件
email
/
userId
、
eventName
、
dataFields
、
createdAt
自定义事件可用于触发和分群
活动
id
、
name
、
type
（批量/触发/周期）、
messageMedium
一个活动对应一个渠道
列表
id
、
name
、
listType
（静态/动态）		静态：手动维护成员；动态：基于规则自动更新
目录
catalogName
、带自定义字段的条目		用于个性化的商品数据
模板
templateId
、
name
、
messageMedium
邮件、推送、SMS、应用内、网页推送模板
实验
experimentId
、变体、指标		A/B或多变量测试

Experiments

实验

  • Campaign experiments: A/B test subject lines, content, send time, channel within a campaign
  • Journey experiments: Experiment tile in Studio — split traffic between journey branches
  • Holdout groups: Measure lift by withholding messages from a control group
  • Winning criteria: Open rate, click rate, conversion event, custom metric
  • Statistical significance: Iterable calculates significance — wait for sufficient sample before declaring a winner
  • 活动实验：在单个活动内A/B测试主题、内容、发送时间、渠道
  • 旅程实验：Studio中的实验组件，可在不同旅程分支之间分流
  • 对照组：通过不给对照组用户发消息来衡量活动提升效果
  • 获胜判定标准：打开率、点击率、转化事件、自定义指标
  • 统计显著性：Iterable自动计算显著性，样本量足够后再判定获胜版本

Segmentation

分群

  • Static lists: Manual membership — upload CSV, API subscribe, or journey action
  • Dynamic lists: Rule-based — auto-update based on user attributes, events, engagement
  • Filters: Combine user attributes, event history, campaign engagement, Brand Affinity labels, catalog interactions
  • Cohorts: Time-based user groups (e.g., "signed up in last 30 days")
  • 静态列表：手动维护成员，可通过CSV上传、API订阅、旅程动作添加
  • 动态列表：基于规则自动更新，根据用户属性、事件、互动情况自动调整成员
  • 筛选器：可组合用户属性、事件历史、活动互动、Brand Affinity标签、目录交互等条件
  • 同期群：基于时间的用户组（例：「过去30天注册的用户」）

API quick reference

API快速参考

ActionMethod & endpoint
Update user
POST /api/users/update
Bulk update users
POST /api/users/bulkUpdate
Track event
POST /api/events/track
Bulk track events
POST /api/events/trackBulk
Send email
POST /api/email/target
Send push
POST /api/push/target
Send SMS
POST /api/sms/target
Send in-app
POST /api/inApp/target
Create list
POST /api/lists
Subscribe to list
POST /api/lists/subscribe
Unsubscribe from list
POST /api/lists/unsubscribe
Export users
GET /api/export/data.csv
Get campaigns
GET /api/campaigns
Catalog items
POST /api/catalogs/{catalogName}/items
  • Base URLs: 
    https://api.iterable.com
    (US), 
    https://api.eu.iterable.com
    (EU)
  • Auth: 
    Api-Key
    header. Optional JWT for client-side keys (Bearer token in 
    Authorization
    header).
  • Rate limits: Varies by endpoint. Bulk track: 10 req/s. Export: 4 req/min. 429 status on limit — implement exponential backoff.
操作方法与端点
更新用户
POST /api/users/update
批量更新用户
POST /api/users/bulkUpdate
上报事件
POST /api/events/track
批量上报事件
POST /api/events/trackBulk
发送邮件
POST /api/email/target
发送推送
POST /api/push/target
发送SMS
POST /api/sms/target
发送应用内消息
POST /api/inApp/target
创建列表
POST /api/lists
订阅列表
POST /api/lists/subscribe
取消订阅列表
POST /api/lists/unsubscribe
导出用户
GET /api/export/data.csv
获取活动列表
GET /api/campaigns
操作目录项
POST /api/catalogs/{catalogName}/items
  • 基础地址：
    https://api.iterable.com
    （美区）、
    https://api.eu.iterable.com
    （欧区）
  • 鉴权：请求头携带
    Api-Key
    ，客户端密钥可选JWT鉴权（
    Authorization
    头中携带Bearer token）
  • 限流：不同端点限流规则不同，批量事件上报为10次/秒，导出为4次/分钟，触发限流返回429状态码，请实现指数退避重试逻辑

Integrations

集成

  • Smart Ingest: 23+ data sources (Snowflake, BigQuery, Redshift, Databricks, etc.)
  • Snowflake Secure Data Sharing: Export Iterable data to Snowflake
  • System webhooks: Email send/open/click, push send/open, SMS send/bounce, list subscribe/unsubscribe. Configure at Integrations > System Webhooks. Auth: None, Basic, or OAuth 2.0.
  • Journey webhooks: Webhook tile in Studio — call external APIs at any point in a journey
  • Native integrations: Shopify (product sync, cart events, purchase tracking), Segment, Hightouch, Movable Ink, Facebook Custom Audiences, Google Ads, Mixpanel, Amplitude
  • Zapier: Triggers and actions for user updates, events, campaigns
  • SDKs: iOS (Swift), Android (Kotlin/Java), React Native, Web (JavaScript)
  • Smart Ingest：支持23+数据源（Snowflake、BigQuery、Redshift、Databricks等）
  • Snowflake安全数据共享：将Iterable数据导出到Snowflake
  • 系统Webhook：邮件发送/打开/点击、推送发送/打开、SMS发送/退信、列表订阅/退订事件触发，配置入口：集成 > 系统Webhook，鉴权方式：无、Basic、OAuth 2.0
  • 旅程Webhook：Studio中的Webhook组件，可在旅程任意节点调用外部API
  • 原生集成：Shopify（商品同步、购物车事件、购买埋点）、Segment、Hightouch、Movable Ink、Facebook自定义受众、Google Ads、Mixpanel、Amplitude
  • Zapier：支持用户更新、事件、活动相关的触发和动作
  • SDK：iOS（Swift）、Android（Kotlin/Java）、React Native、Web（JavaScript）

Pricing

定价

As of March 2026 — verify current pricing with Iterable sales:
  • No free tier or self-serve signup — enterprise sales process
  • MAU-based pricing with channel-specific usage fees
  • Growth: ~$3K-$6K/mo for 10K-50K MAUs (core channels, basic segmentation, workflows)
  • Enterprise: Custom pricing ($10K+/mo) — all channels, AI suite, Smart Ingest, dedicated support
  • SMS and push may carry additional per-message or per-MAU costs beyond base plan
2026年3月版本，请以Iterable销售的最新定价为准：
  • 无免费版或自助注册，仅支持企业级销售流程
  • 基于MAU（月活跃用户）定价，不同渠道有单独的使用费
  • 增长版：1万-5万MAU约3000-6000美元/月，包含核心渠道、基础分群、工作流能力
  • 企业版：自定义定价（1万美元/月起），包含全渠道、AI套件、Smart Ingest、专属支持
  • SMS和推送可能在基础套餐外额外收取单条消息或MAU费用

Step 4 — Actionable guidance

步骤4——可落地的指导

Getting started checklist

入门检查清单

  1. Set up data center — confirm US or EU data center for your project (affects API base URL and data residency)
  2. Configure channels — authenticate sending domains (email), set up FCM/APNs (push), provision SMS numbers, configure web push
  3. Integrate SDK — install iOS/Android/Web SDK for push, in-app, Mobile Inbox, Embedded Messages, and event tracking
  4. Import users — bulk upload via CSV, API (
    /api/users/bulkUpdate
    ), or Smart Ingest from your data warehouse
  5. Define events — map your key user actions (signup, purchase, feature_used, cart_abandoned) and implement tracking via SDK or API
  6. Build segments — create dynamic lists for key audiences (active, lapsed, high-value, new users)
  7. Create templates — design email, push, SMS, and in-app templates with dynamic Handlebars content
  8. Build first journey — start with a welcome journey in Studio: entry on signup event → email → delay → push → branch on engagement
  9. Set up experiments — A/B test subject lines and send times on your first campaign
  10. Enable AI — turn on Brand Affinity, STO, and Frequency Optimization once you have 30+ days of engagement data
  11. Configure webhooks — set up system webhooks for delivery monitoring and CRM sync
  12. Connect data warehouse — set up Snowflake Secure Data Sharing or Smart Ingest for bidirectional data flow
  1. 设置数据中心：确认项目使用美区还是欧区数据中心（影响API基础地址和数据存储地域）
  2. 配置渠道：认证发件域名（邮件）、设置FCM/APNs（推送）、申请SMS号码、配置网页推送
  3. 集成SDK：安装iOS/Android/Web SDK，实现推送、应用内消息、移动收件箱、嵌入式消息能力和事件埋点
  4. 导入用户：通过CSV批量上传、API（
    /api/users/bulkUpdate
    ）或从数仓通过Smart Ingest同步导入用户
  5. 定义事件：梳理核心用户动作（注册、购买、使用功能、放弃购物车），通过SDK或API实现埋点
  6. 搭建分群：为核心受众（活跃、流失、高价值、新用户）创建动态列表
  7. 创建模板：设计带Handlebars动态内容的邮件、推送、SMS、应用内消息模板
  8. 搭建首个旅程：从Studio的欢迎旅程开始：注册事件触发进入→发送欢迎邮件→延迟1天→发送推送→按互动情况分支
  9. 设置实验：在首个活动中对主题和发送时间做A/B测试
  10. 开启AI能力：积累30天以上的互动数据后，开启Brand Affinity、STO和频次优化
  11. 配置Webhook：设置系统Webhook用于送达监控和CRM同步
  12. 对接数仓：配置Snowflake安全数据共享或Smart Ingest实现双向数据流

Key metrics to track

核心监控指标

MetricWhere in IterableBenchmark
Email open rateCampaign analytics20-25%
Email click rateCampaign analytics2-5%
Push open rateCampaign analytics5-15%
In-app click rateCampaign analytics15-30%
SMS delivery rateCampaign analytics> 95%
Journey completion rateStudio analyticsVaries by journey
Brand Affinity distributionAI > Brand AffinityHealthy: majority Positive/Loyal
Experiment significanceExperiment resultsWait for 95% confidence
指标Iterable查看入口基准值
邮件打开率活动分析20-25%
邮件点击率活动分析2-5%
推送打开率活动分析5-15%
应用内消息点击率活动分析15-30%
SMS送达率活动分析> 95%
旅程完成率Studio分析不同旅程差异较大
Brand Affinity分布AI > Brand Affinity健康状态：大部分用户为积极/忠诚
实验显著性实验结果等待95%置信度再判定结果

Gotchas

坑点提示

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  1. Campaign = one channel only. Unlike Braze (where a Canvas can send email + push + in-app), an Iterable campaign targets one message channel. To send across multiple channels, use Studio journeys with multiple Send tiles — don't try to make a single campaign multi-channel.
  2. Brand Affinity needs data. Brand Affinity labels won't be accurate until you have 30+ days of engagement data across campaigns. Don't use Brand Affinity for segmentation in your first month — you'll get mostly "Neutral" and "Never Engaged" labels.
  3. API rate limits vary by endpoint and are per-project. Bulk track events is 10 req/s, exports are 4 req/min. Multiple API consumers on the same project share the per-project rate limit. Implement exponential backoff for 429 responses.
  4. Smart Ingest syncs are not real-time. The fastest Smart Ingest sync interval is 15 minutes. For real-time data, use the REST API (
    /api/users/update
    , 
    /api/events/track
    ) instead. Smart Ingest is best for periodic warehouse syncs, not event streaming.
  5. In-app messages require SDK integration. Unlike email or push, in-app messages, Mobile Inbox, and Embedded Messages require the Iterable SDK installed in your app. They won't work if you're only using the REST API for server-side messaging.
基于调研整理，请务必核对，尤其是套餐限制功能和集成相关的坑点可能会过时
  1. 一个活动仅对应一个渠道。和Braze的Canvas可以同时发邮件+推送+应用内消息不同，一个Iterable活动仅能选择一个消息渠道。如需跨渠道发送，请在Studio旅程中添加多个发送组件，不要尝试让单个活动支持多渠道。
  2. Brand Affinity需要足够数据支撑。积累30天以上的跨活动互动数据后Brand Affinity标签才会准确，上线首月不要用Brand Affinity做分群，此时大部分用户会被标记为「中立」或「从未互动」。
  3. API限流按端点和项目区分。批量事件上报限流10次/秒，导出限流4次/分钟，同一个项目下的多个API调用方共享项目级限流，收到429响应请实现指数退避重试。
  4. Smart Ingest同步不是实时的。Smart Ingest最快同步间隔为15分钟，实时数据请使用REST API（
    /api/users/update
    、
    /api/events/track
    ），Smart Ingest适合定期数仓同步，不适合事件流传输。
  5. 应用内消息需要SDK集成。和邮件或推送不同，应用内消息、移动收件箱、嵌入式消息需要在应用中安装Iterable SDK，仅用REST API做服务端消息发送无法使用这些功能。

Related skills

相关技能

  • /sales-email-marketing
    — Email marketing strategy across platforms (not Iterable-specific)
  • /sales-push-notification
    — Push notification strategy (opt-in, rich push, frequency capping across tools)
  • /sales-in-app-messaging
    — In-app messaging strategy (message types, trigger design, onboarding across tools)
  • /sales-transactional-email
    — Transactional email delivery (provider comparison, API integration)
  • /sales-deliverability
    — Email deliverability (SPF/DKIM/DMARC, warmup, sender reputation)
  • /sales-integration
    — Connect Iterable to CRM, data warehouse, and other tools
  • /sales-braze
    — Braze platform help (primary competitor — for Braze-specific questions)
  • /sales-customerio
    — Customer.io platform help (another cross-channel platform)
  • /sales-klaviyo
    — Klaviyo platform help (e-commerce-focused engagement)
  • /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-email-marketing
    ——跨平台邮件营销策略（非Iterable专属）
  • /sales-push-notification
    ——推送通知策略（跨工具的订阅、富推送、频次上限设置）
  • /sales-in-app-messaging
    ——应用内消息策略（跨工具的消息类型、触发设计、新用户引导）
  • /sales-transactional-email
    ——事务性邮件送达（服务商对比、API集成）
  • /sales-deliverability
    ——邮件送达率（SPF/DKIM/DMARC、域名预热、发件人信誉）
  • /sales-integration
    ——对接Iterable与CRM、数仓等其他工具
  • /sales-braze
    ——Braze平台帮助（Iterable主要竞品，解答Braze专属问题）
  • /sales-customerio
    ——Customer.io平台帮助（另一款跨渠道营销平台）
  • /sales-klaviyo
    ——Klaviyo平台帮助（面向电商的用户互动平台）
  • /sales-do
    ——不确定该用哪个技能？路由工具会将任何销售目标匹配到合适的技能。安装命令：
    npx skills add sales-skills/sales --skills sales-do

Examples

示例

Example 1: Building a welcome journey in Studio

示例1：在Studio中搭建欢迎旅程

User says: "How do I create a multi-step welcome journey for new users in Iterable?" Skill does: Walks through creating a Studio journey: entry trigger on "signup" custom event → Send email (welcome + value prop) → Delay 1 day → Filter (opened welcome email?) → Yes branch: Send push (feature highlight) → Delay 2 days → Send in-app (onboarding tooltip). No branch: Send email (re-engagement). Exit criteria: user completes onboarding event. Includes template recommendations and Brand Affinity filtering for later stages. Result: Complete Studio journey with multi-channel onboarding flow
用户提问：「我怎么在Iterable中为新用户创建多步骤欢迎旅程？」 技能响应：讲解创建Studio旅程的流程：进入触发条件为「注册」自定义事件→发送欢迎邮件（介绍价值主张）→延迟1天→筛选（是否打开欢迎邮件？）→是分支：发送推送（核心功能亮点）→延迟2天→发送应用内消息（新用户引导提示）；否分支：发送重激活邮件。退出条件：用户完成新用户引导事件。同时给出模板建议，以及后续阶段可以加入Brand Affinity筛选的提示。 结果：完整的多渠道新用户引导Studio旅程

Example 2: Setting up experiments

示例2：设置实验

User says: "How do I A/B test email subject lines in Iterable?" Skill does: Explains two approaches: 1) Campaign-level experiment — create a blast campaign, add experiment with 2-4 subject line variants, set winning metric (open rate), sample size (20%), and auto-send winner timing. 2) Journey experiment — add Experiment tile in Studio to split traffic between two email Send tiles with different subjects. Recommends minimum 1,000 recipients per variant for statistical significance. Result: A/B test configured with proper sample sizing and winning criteria
用户提问：「我怎么在Iterable中对邮件主题做A/B测试？」 技能响应：讲解两种方案：1）活动级实验：创建批量推送活动，添加2-4个主题变体，设置获胜指标（打开率）、样本量（20%）、自动发送获胜版本的时间。2）旅程实验：在Studio中添加实验组件，将流量分流到两个使用不同主题的邮件发送组件。建议每个变体最少1000个收件人保证统计显著性。 结果：配置完成的符合样本量和获胜标准要求的A/B测试

Example 3: Integrating with Snowflake via Smart Ingest

示例3：通过Smart Ingest对接Snowflake

User says: "How do I sync our user data from Snowflake into Iterable?" Skill does: Walks through Smart Ingest setup: Integrations > Smart Ingest > Create Connection > Select Snowflake > Configure credentials (account, warehouse, database, schema) > Map sync type (Users) > Map fields (email → email, custom attributes → dataFields) > Set sync frequency (every 15 min or hourly) > Test and activate. Mentions Snowflake Secure Data Sharing for the reverse direction (Iterable → Snowflake). Result: Bidirectional Snowflake-Iterable data pipeline configured
用户提问：「我怎么把Snowflake里的用户数据同步到Iterable？」 技能响应：讲解Smart Ingest的配置流程：集成 > Smart Ingest > 创建连接 > 选择Snowflake > 配置凭证（账户、数仓、数据库、schema）> 选择同步类型（用户）> 字段映射（email→email，自定义属性→dataFields）> 设置同步频率（每15分钟或每小时）> 测试并激活。同时说明反向同步（Iterable→Snowflake）可以用Snowflake安全数据共享实现。 结果：配置完成的Snowflake-Iterable双向数据管道

Troubleshooting

问题排查

Push notifications not delivering on iOS

iOS推送无法送达

Symptom: Push campaigns show sends but no deliveries on iOS devices Cause: APNs certificate expired, sandbox/production mismatch, or SDK not properly initialized Solution: 1) Check APNs certificate expiry in Iterable Settings > Mobile Apps. 2) Verify you're using the correct APNs environment (sandbox for TestFlight, production for App Store). 3) Confirm the Iterable SDK is initialized with the correct API key and push registration is calling 
registerForRemoteNotifications()
. 4) Check that the device token is being sent to Iterable via 
setDeviceToken()
. 5) Test with a fresh app install to generate a new token.
症状：推送活动显示已发送，但iOS设备没有收到 原因：APNs证书过期、沙箱/生产环境不匹配、SDK未正确初始化 解决方案：1）在Iterable设置 > 移动应用中检查APNs证书有效期。2）确认使用了正确的APNs环境（TestFlight用沙箱，App Store用生产环境）。3）确认Iterable SDK使用正确的API key初始化，且推送注册调用了
registerForRemoteNotifications()
。4）确认设备token通过
setDeviceToken()
上传到了Iterable。5）重装应用生成新的token测试。

Smart Ingest sync failing

Smart Ingest同步失败

Symptom: Smart Ingest connection shows errors or no data syncing Cause: Credential issues, query timeout, or field mapping mismatch Solution: 1) Verify Snowflake/BigQuery credentials are still valid and have SELECT permissions on the source table. 2) Check that the source query returns data (run it directly in your warehouse). 3) Verify field mapping — email or userId must be mapped to identify users. 4) Check for data type mismatches (e.g., string field mapped to number). 5) Review Smart Ingest logs in Iterable for specific error messages.
症状：Smart Ingest连接报错或没有数据同步 原因：凭证问题、查询超时、字段映射不匹配 解决方案：1）确认Snowflake/BigQuery凭证有效，且对源表有SELECT权限。2）直接在数仓中运行源查询确认有返回数据。3）确认字段映射正确，必须映射email或userId作为用户标识。4）检查数据类型不匹配问题（例：字符串字段映射到数字类型）。5）查看Iterable中的Smart Ingest日志获取具体报错信息。

Low Brand Affinity accuracy

Brand Affinity准确率低

Symptom: Most users showing as "Neutral" or "Never Engaged" in Brand Affinity Cause: Insufficient engagement data — Brand Affinity needs historical cross-channel interaction data to generate meaningful scores Solution: 1) Ensure you've been sending campaigns across multiple channels for 30+ days. 2) Verify that open/click tracking is enabled for email campaigns. 3) Check that push notification open tracking is working (SDK properly configured). 4) Brand Affinity recalculates periodically — wait for the next refresh cycle after adding more engagement data. 5) In the meantime, use traditional engagement-based segmentation (opened in last 30 days) instead of Brand Affinity labels.
症状：大部分用户在Brand Affinity中显示为「中立」或「从未互动」 原因：互动数据不足，Brand Affinity需要历史跨渠道互动数据才能生成有意义的分数 解决方案：1）确认你已经跨多个渠道发送活动超过30天。2）确认邮件活动开启了打开/点击跟踪。3）确认推送通知打开跟踪正常（SDK配置正确）。4）Brand Affinity会定期重算，新增互动数据后等待下一个刷新周期。5）在此期间使用传统的基于互动的分群（过去30天打开过消息）替代Brand Affinity标签。