Back to Details

sales-mparticle

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

mParticle Platform Help

mParticle平台帮助

Step 1 — Gather context

步骤1 — 收集上下文

If 
references/learnings.md
exists, read it first for accumulated platform knowledge.
  1. What's your situation?
    • A) Setting up mParticle for the first time
    • B) SDK or API integration issues (events not sending, errors)
    • C) Identity resolution problems (wrong merges, duplicate profiles)
    • D) Audience/segmentation not working as expected
    • E) Connection to a destination failing or delayed
    • F) Data planning / schema validation issues
    • G) Privacy / DSR / compliance questions
    • H) Pricing, plan limits, or cost optimization
    • I) Migrating to/from mParticle
    • J) Other — describe it
  2. Which APIs/SDKs are you using?
    • A) Web SDK
    • B) Mobile SDK (iOS, Android, React Native, Flutter)
    • C) Events HTTP API (server-side)
    • D) Platform API (account/workspace management)
    • E) Profile API (querying user profiles)
    • F) Data Planning API
    • G) IDSync API
    • H) Not sure / haven't started yet
  3. What's your mParticle pod?
    • A) US1 (default)
    • B) US2
    • C) EU1
    • D) AU1
    • E) Not sure
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
若
references/learnings.md
文件存在，请先阅读以获取积累的平台相关知识。
  1. 你的场景是？
    • A) 首次设置mParticle
    • B) SDK或API集成问题（事件无法发送、报错）
    • C) 身份解析问题（错误合并、重复用户档案）
    • D) 受众/细分功能未按预期工作
    • E) 与目标平台的连接失败或延迟
    • F) 数据规划/ schema验证问题
    • G) 隐私/DSR/合规相关问题
    • H) 定价、计划限制或成本优化
    • I) 迁移至/从mParticle迁移
    • J) 其他——请描述
  2. 你正在使用哪些API/SDK？
    • A) Web SDK
    • B) 移动SDK（iOS、Android、React Native、Flutter）
    • C) Events HTTP API（服务器端）
    • D) Platform API（账户/工作区管理）
    • E) Profile API（查询用户档案）
    • F) Data Planning API
    • G) IDSync API
    • H) 不确定/尚未开始使用
  3. 你的mParticle集群是？
    • A) US1（默认）
    • B) US2
    • C) EU1
    • D) AU1
    • E) 不确定
跳过规则：如果用户的提问已包含足够上下文，直接跳转至步骤2。

Step 2 — Route or answer directly

步骤2 — 路由或直接解答

Problem domainRoute to
Choosing between CDPs (mParticle vs Segment vs others)
/sales-cdp {user's question}
CRM data dedup without a CDP
/sales-data-hygiene {user's question}
Connecting mParticle to email platforms
/sales-integration {user's question}
Retargeting with mParticle audiences
/sales-retargeting {user's question}
Contact enrichment before feeding to mParticle
/sales-enrich {user's question}
When routing, provide the exact command.
问题领域路由至
CDP选型（mParticle vs Segment等）
/sales-cdp {用户问题}
无CDP情况下的CRM数据去重
/sales-data-hygiene {用户问题}
mParticle与邮件平台连接
/sales-integration {用户问题}
利用mParticle受众进行重定向
/sales-retargeting {用户问题}
导入mParticle前的联系人信息补充
/sales-enrich {用户问题}
路由时，请提供准确的命令。

Step 3 — mParticle platform reference

步骤3 — mParticle平台参考

Read 
references/platform-guide.md
 for the full platform reference — modules, pricing, integrations, data model, API overview, workflows.
Read 
references/mparticle-api-reference.md
 for detailed API endpoints, authentication, request/response formats.
Answer the user's question using only the relevant section. Don't dump the full reference.
**阅读
references/platform-guide.md
**获取完整平台参考——模块、定价、集成、数据模型、API概述、工作流。
**阅读
references/mparticle-api-reference.md
**获取详细API端点、认证方式、请求/响应格式。
仅使用相关章节内容解答用户问题，不要直接输出完整参考文档。

Step 4 — Actionable guidance

步骤4 — 可落地指导

You no longer need the platform guide — focus on the user's specific situation.
Quick decision framework:
  • First-time setup: Start with one data source (web or mobile SDK) → one destination. Get events flowing end-to-end before adding more sources.
  • SDK issues: Check pod-specific endpoint, API key/secret pair, and that the SDK is initialized before logging events.
  • Identity problems: Review your Identity Strategy in the dashboard. Test with 
    /identify
    endpoint before relying on automatic resolution.
  • Audience sync delays: Connections can take up to 48 hours on initial setup. Check connection status in the dashboard. Real-time forwarding ≠ real-time destination processing.
  • Cost optimization: Monitor event volume in Usage dashboard. Use Data Plans to filter noise events before they count toward billing.
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
无需再查阅平台指南——聚焦用户的具体场景。
快速决策框架：
  • 首次设置：从一个数据源（Web或移动SDK）开始→连接一个目标平台。在添加更多数据源前，先实现端到端的事件流转。
  • SDK问题：检查集群专属端点、API密钥/密钥对，确保SDK在记录事件前已完成初始化。
  • 身份解析问题：在控制台中查看你的Identity Strategy（身份策略）。在依赖自动解析前，先用
    /identify
    端点进行测试。
  • 受众同步延迟：首次设置连接最长可能需要48小时。在控制台中检查连接状态。实时转发≠目标平台实时处理。
  • 成本优化：在使用量控制台中监控事件量。使用数据计划在事件计入账单前过滤无效事件。
如果发现
references/learnings.md
中未涵盖的注意事项、临时解决方案或技巧，请补充至该文件。

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  1. Connection setup can take up to 48 hours — the UI shows "connected" but backend provisioning may still be running. Only a CSM will tell you this; it's not documented in-product.
  2. Calculated attributes are very basic — no multiply, divide, or arithmetic operations. If you need complex computed fields, do them in your warehouse and sync back.
  3. Token expiry is 8 hours with no revocation — Platform/Profile API OAuth tokens can't be revoked, only expire. Cache them and refresh proactively; initial token requests take 1-3 seconds.
  4. Pod-specific endpoints are required — using the wrong regional endpoint (US1 vs US2 vs EU1 vs AU1) silently drops events. Verify your pod in Workspace Settings.
  5. Bulk events endpoint accepts up to 100 batches — but returns 202 even if individual batches fail. Validate batch structure before sending; check quarantine for failures.
  6. Events API rate limit is 250 events/sec — contact support for higher limits. No self-serve rate limit increases.
  7. Profile API has 15 RPS limit — intended for testing, not production. Implement a backend personalization service as intermediary.
  8. No self-serve pricing — enterprise-only, typically $40K-$375K+/year. Consumption-based on events, storage, and activation credits.
基于研究的最佳实践——请仔细查看，尤其是关于计划专属功能和可能过时的集成注意事项。
  1. 连接设置最长可能需要48小时——UI显示“已连接”但后端配置可能仍在运行。只有客户成功经理（CSM）会告知这一点，产品内无相关文档说明。
  2. 计算属性功能非常基础——不支持乘法、除法或算术运算。如果需要复杂计算字段，请在数据仓库中处理后再同步回来。
  3. 令牌有效期为8小时且不可撤销——Platform/Profile API的OAuth令牌无法撤销，只能到期失效。请缓存令牌并主动刷新；初始令牌请求耗时1-3秒。
  4. 必须使用集群专属端点——使用错误的区域端点（US1 vs US2 vs EU1 vs AU1）会导致事件被静默丢弃。在工作区设置中确认你的集群。
  5. 批量事件端点最多接受100个批次——但即使个别批次失败，仍会返回202状态码。发送前请验证批次结构；在隔离区中检查失败情况。
  6. Events API速率限制为250事件/秒——如需更高限制请联系支持团队。不支持自助提升速率限制。
  7. Profile API速率限制为15请求/秒——仅用于测试，不适合生产环境。请实现后端个性化服务作为中间层。
  8. 无自助定价选项——仅面向企业客户，通常年费为4万美元至37.5万美元以上。基于事件量、存储量和激活点数按使用量计费。

Related skills

相关技能

  • /sales-cdp
    — CDP comparison and selection strategy — choosing between mParticle, Tealium, Segment, RudderStack, and others
  • /sales-tealium
    — Tealium platform help — enterprise CDP with 1,300+ connectors and tag management
  • /sales-rudderstack
    — RudderStack platform help — warehouse-native CDP, open-source, Reverse ETL
  • /sales-blueconic
    — BlueConic CDP — marketer-first profile unification and audience activation
  • /sales-treasuredata
    — Treasure Data enterprise CDP — AI Marketing Cloud, 400+ connectors
  • /sales-data-hygiene
    — CRM data quality — clean your data before feeding it to mParticle
  • /sales-integration
    — Tool integration — connecting mParticle to CRM, email, ad platforms
  • /sales-enrich
    — Contact enrichment — augment mParticle profiles with third-party data
  • /sales-retargeting
    — Retargeting strategy — activate mParticle audiences to ad platforms
  • /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 --skill sales-do
  • /sales-cdp
    — CDP对比与选型策略——在mParticle、Tealium、Segment、RudderStack等产品中选择
  • /sales-tealium
    — Tealium平台帮助——拥有1300+连接器和标签管理的企业级CDP
  • /sales-rudderstack
    — RudderStack平台帮助——数据仓库原生CDP，开源，支持反向ETL
  • /sales-blueconic
    — BlueConic CDP——面向营销人员的档案统一与受众激活平台
  • /sales-treasuredata
    — Treasure Data企业级CDP——AI营销云，拥有400+连接器
  • /sales-data-hygiene
    — CRM数据质量——在导入mParticle前清理数据
  • /sales-integration
    — 工具集成——将mParticle与CRM、邮件、广告平台连接
  • /sales-enrich
    — 联系人信息补充——用第三方数据丰富mParticle用户档案
  • /sales-retargeting
    — 重定向策略——将mParticle受众激活至广告平台
  • /sales-do
    — 不确定使用哪个技能？该路由工具可将任何销售目标匹配至合适技能。安装：
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: Events not reaching destination

示例1：事件未送达目标平台

User says: "I set up a Facebook connection in mParticle but no events are showing up in Facebook" Skill does: Checks connection status (may take up to 48 hours), verifies pod-specific endpoint, confirms data filter settings aren't blocking the events, reviews connection configuration for correct Facebook credentials. Result: User identifies that the connection was still provisioning and events flow after backend setup completes.
用户提问：“我在mParticle中设置了Facebook连接，但没有事件显示在Facebook中” 技能处理：检查连接状态（可能需要长达48小时），验证集群专属端点，确认数据过滤设置未拦截事件，检查连接配置中的Facebook凭证是否正确。 结果：用户发现连接仍在配置中，后端设置完成后事件正常流转。

Example 2: Identity resolution merging wrong profiles

示例2：身份解析合并错误档案

User says: "mParticle is merging two different customers into one profile because they shared a device" Skill does: Reviews Identity Strategy configuration, explains deterministic vs probabilistic matching, recommends switching to a stricter strategy that prioritizes authenticated identifiers over device IDs. Suggests testing with the 
/identify
and 
/search
endpoints. Result: User adjusts their Identity Strategy to prevent false merges from shared devices.
用户提问：“mParticle因为两个客户共用一台设备，将他们合并成了一个档案” 技能处理：查看Identity Strategy配置，解释确定性匹配与概率性匹配的区别，建议切换至更严格的策略，优先使用已认证标识符而非设备ID。建议使用
/identify
和
/search
端点进行测试。 结果：用户调整身份策略，避免因共用设备导致的错误合并。

Example 3: Server-side event ingestion

示例3：服务器端事件导入

User says: "How do I send purchase events from my backend to mParticle?" Skill does: Walks through Events API setup — pod-specific endpoint, Basic auth with API key/secret, batch structure with commerce events, product actions. Recommends using 
/v2/bulkevents
for efficiency and explains the 128KB batch size limit. Result: User has working server-side event ingestion with proper authentication and batch formatting.
用户提问：“如何从我的后端向mParticle发送购买事件？” 技能处理：逐步讲解Events API设置——集群专属端点、使用API密钥/密钥对的基础认证、包含商业事件的批次结构、产品操作。推荐使用
/v2/bulkevents
以提高效率，并说明128KB的批次大小限制。 结果：用户成功实现服务器端事件导入，具备正确的认证和批次格式。

Troubleshooting

故障排查

Events API returning 403

Events API返回403

Symptom: Server-side events return 403 Forbidden Cause: Wrong API key/secret pair, or using Platform API credentials instead of Events API credentials Solution: Events API uses separate credentials from the Platform API. Go to Setup > Inputs > select your platform > copy the API Key and Secret specifically for that input. Use Basic auth, not OAuth.
症状：服务器端事件返回403 Forbidden（禁止访问） 原因：API密钥/密钥对错误，或使用了Platform API凭证而非Events API凭证 解决方案：Events API使用与Platform API不同的凭证。前往设置>输入>选择你的平台>复制该输入专属的API密钥和密钥。使用基础认证，而非OAuth。

Audiences not syncing to destination

受众未同步至目标平台

Symptom: Audience created in mParticle but destination shows no members Cause: Connection provisioning delay, data filter blocking audience attributes, or destination credentials expired Solution: Check connection status (allow up to 48 hours for new connections). Verify data filters aren't blocking user attributes or identities the destination needs. Re-authenticate the destination connection if credentials expired.
症状：在mParticle中创建了受众，但目标平台无成员显示 原因：连接配置延迟、数据过滤拦截了受众属性、或目标平台凭证过期 解决方案：检查连接状态（新连接最多允许48小时配置时间）。验证数据过滤未拦截目标平台所需的用户属性或身份信息。如果凭证过期，请重新认证目标平台连接。

Data Plan validation rejecting valid events

数据计划验证拒绝有效事件

Symptom: Events quarantined even though they look correct Cause: Schema mismatch between Data Plan version and actual event structure — often a property type mismatch or missing required field Solution: Check quarantine for specific validation errors. Compare your event payload against the Data Plan's JSON Schema. Use the 
/validate
endpoint to test batches before sending. Rate limits: 3,000 req/min per account, 6,000 req/min per org.
症状：事件被隔离，但看起来格式正确 原因：数据计划版本与实际事件结构不匹配——通常是属性类型不匹配或缺少必填字段 解决方案：在隔离区中查看具体的验证错误。将你的事件负载与数据计划的JSON Schema进行对比。发送前使用
/validate
端点测试批次。速率限制：每个账户3000请求/分钟，每个组织6000请求/分钟。