Back to Details

sales-tealium

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Tealium Platform Help

Tealium平台帮助

Step 1 — Gather context

步骤1 — 收集上下文

If 
references/learnings.md
exists, read it first for accumulated platform knowledge.
  1. What do you need help with?
    • A) Setting up Tealium (iQ Tag Management, utag.js, mobile SDK)
    • B) Identity resolution / visitor switching / profile merging
    • C) EventStream — server-side event processing, feeds, connectors
    • D) AudienceStream — audience segmentation, enrichments, badges
    • E) Connector Marketplace — setting up or troubleshooting a connector
    • F) API integration (Collect HTTP API v3, Visitor Profile API, Visitor Privacy API)
    • G) Composable CDP / CloudStream — warehouse integration (Snowflake, BigQuery, Databricks)
    • H) Consent management and privacy (GDPR, CCPA)
    • I) Tag performance — tags slowing down my site, rogue tags
    • J) Choosing Tealium vs another CDP (Segment, mParticle, BlueConic)
    • K) Other — describe it
  2. What's your role?
    • A) Marketer — I use AudienceStream UI for segments and audiences
    • B) Developer — I'm integrating via API, SDK, or utag.js
    • C) Data/analytics — I work with EventStream, data layer, or warehouse sync
    • D) Admin — I manage users, publish profiles, configure connectors
  3. Which Tealium products are you using?
    • A) iQ Tag Management only
    • B) AudienceStream CDP
    • C) EventStream API Hub
    • D) Composable / CloudStream (warehouse-native)
    • E) Full stack (iQ + AudienceStream + EventStream)
    • F) Evaluating — haven't purchased yet
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
如果
references/learnings.md
存在，请先阅读其中积累的平台知识。
  1. 你需要哪方面的帮助？
    • A) 设置Tealium（iQ标签管理、utag.js、移动SDK）
    • B) 身份解析/访客切换/档案合并
    • C) EventStream — 服务器端事件处理、数据源、连接器
    • D) AudienceStream — 受众细分、数据 enrichment、badges
    • E) 连接器市场 — 设置或排查连接器问题
    • F) API集成（Collect HTTP API v3、访客档案API、访客隐私API）
    • G) 可组合CDP/CloudStream — 数据仓库集成（Snowflake、BigQuery、Databricks）
    • H) 同意管理与隐私合规（GDPR、CCPA）
    • I) 标签性能 — 标签拖慢网站速度、异常标签
    • J) 在Tealium与其他CDP之间做选择（Segment、mParticle、BlueConic）
    • K) 其他 — 请描述具体问题
  2. 你的角色是什么？
    • A) 营销人员 — 我使用AudienceStream UI创建细分群体和受众
    • B) 开发人员 — 我通过API、SDK或utag.js进行集成
    • C) 数据/分析师 — 我负责EventStream、数据层或数据仓库同步
    • D) 管理员 — 我管理用户、发布配置文件、配置连接器
  3. 你正在使用哪些Tealium产品？
    • A) 仅使用iQ标签管理
    • B) AudienceStream CDP
    • C) EventStream API Hub
    • D) 可组合/CloudStream（数据仓库原生）
    • E) 全栈（iQ + AudienceStream + EventStream）
    • F) 评估中 — 尚未购买
跳过规则：如果用户的提示已包含足够上下文，直接跳至步骤2。

Step 2 — Route or answer directly

步骤2 — 路由或直接解答

Problem domainRoute to
Email campaign strategy
/sales-email-marketing
— then come back for Tealium audience activation
CRM data dedup without Tealium
/sales-data-hygiene
— Tealium is a CDP, not a CRM dedup tool
Retargeting ad strategy
/sales-retargeting
— then come back for Tealium audience sync
Connecting Tealium to other toolsAnswer here using connector reference
Tool integration architecture
/sales-integration
— for webhook/Zapier patterns beyond Tealium connectors
Choosing between CDPs
/sales-cdp
— cross-platform CDP comparison and selection
When routing to another skill, provide the exact command: "This is a {problem domain} question — run: 
/sales-{skill} {user's original question}
"
问题领域路由至
电子邮件营销活动策略
/sales-email-marketing
— 之后再回来处理Tealium受众激活
不涉及Tealium的CRM数据去重
/sales-data-hygiene
— Tealium是CDP，而非CRM去重工具
重定向广告策略
/sales-retargeting
— 之后再回来处理Tealium受众同步
将Tealium与其他工具连接在此处使用连接器参考文档解答
工具集成架构
/sales-integration
— 用于Tealium连接器之外的webhook/Zapier模式
CDP选型
/sales-cdp
— 跨平台CDP对比与选型
当路由至其他技能时，请提供准确命令："这属于{问题领域}问题 — 执行：
/sales-{skill} {用户原始问题}
"

Step 3 — Tealium platform reference

步骤3 — Tealium平台参考

Read 
references/platform-guide.md
 for the full platform reference — products, modules, pricing, integrations, data model, connector setup, identity resolution.
Answer the user's question using only the relevant section. Don't dump the full reference.
**阅读
references/platform-guide.md
**获取完整平台参考信息——产品、模块、定价、集成、数据模型、连接器设置、身份解析。
仅使用相关章节解答用户问题，不要直接输出完整参考内容。

Step 4 — Actionable guidance

步骤4 — 可操作指导

You no longer need the platform guide — focus on the user's specific situation.
  • For iQ setup: Walk through utag.js installation, data layer definition, tag configuration, load rules
  • For identity resolution: Explain Visitor Switching modes, cross-device stitching, anonymous-to-known progression
  • For connectors: Identify the right connector, configure actions, map attributes, set frequency capping
  • For EventStream: Help configure event feeds, filters, transformations, and connector triggers
  • For API questions: Point to the right API (Collect v3 for ingestion, Visitor Profile for lookups, Visitor Privacy for GDPR)
  • For warehouse sync: Walk through Composable CDP or CloudStream setup with Snowflake/BigQuery/Databricks
If you discover a gotcha, workaround, or tip not covered in 
references/learnings.md
, append it there.
此时无需依赖平台指南——聚焦用户的具体场景。
  • 针对iQ设置：引导完成utag.js安装、数据层定义、标签配置、加载规则
  • 针对身份解析：解释访客切换模式、跨设备关联、匿名到已知身份的转换流程
  • 针对连接器：确定合适的连接器、配置操作、映射属性、设置频次限制
  • 针对EventStream：帮助配置事件数据源、过滤器、转换规则和连接器触发器
  • 针对API问题：指向正确的API（数据摄入用Collect v3、档案查询用访客档案API、GDPR合规用访客隐私API）
  • 针对数据仓库同步：引导完成可组合CDP或CloudStream与Snowflake/BigQuery/Databricks的设置
如果发现
references/learnings.md
中未涵盖的注意事项、解决方法或技巧，请将其添加到该文档中。

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
  1. Implementation takes weeks to months — unlike Segment (days for POC), Tealium requires careful data layer planning, tag configuration, and connector mapping. Budget 4-12 weeks for a production deployment.
  2. Collect HTTP API rate limit is 100 events/sec — this includes bulk events (10 per call × 10 calls = 100 events). Exceeding returns HTTP 429. For higher throughput, contact your account manager.
  3. JWT bearer tokens expire after 30 minutes — cache and reuse the token until expiry. Re-authenticating too frequently triggers throttling.
  4. Identity resolution default configs often fail complex scenarios — visitor switching with shared devices (householding) or guest transactions can blur individual profiles. Test identity rules in QA before production.
  5. Event-based pricing scales unpredictably — costs increase significantly as event volumes rise. Monitor event counts and set alerts before hitting overage thresholds.
  6. iQ tags load asynchronously by default — but third-party tags can still block page rendering. Use the tag timeout feature to cancel slow tags. Place analytics tags first in the load order.
  7. Connector retry logic is 1min → 5min → 30min — if all three retries fail, the request is dropped. Monitor error rates in the connector dashboard. Errors above threshold trigger automatic throttling.
  8. Can't open two tabs in the admin UI simultaneously — and the session frequently expires, requiring re-login. This is a known UX limitation.
基于研究的最佳实践——请仔细查看，尤其是关于功能权限限制和可能过时的集成注意事项。
  1. 实施周期需数周至数月——与Segment（POC仅需数天）不同，Tealium需要精心规划数据层、配置标签和映射连接器。生产环境部署需预留4-12周时间。
  2. Collect HTTP API速率限制为100事件/秒——包括批量事件（每次调用10个事件 × 10次调用 = 100个事件）。超出限制将返回HTTP 429错误。如需更高吞吐量，请联系客户经理。
  3. JWT承载令牌30分钟后过期——缓存并重用令牌直至过期。过于频繁的重新认证会触发限流。
  4. 默认身份解析配置在复杂场景下常失效——共享设备（家庭共用）或访客交易场景下的访客切换可能导致个人档案混淆。请在生产环境部署前在QA环境测试身份规则。
  5. 基于事件的定价会不可预测地增长——随着事件量增加，成本会显著上升。请监控事件计数并在达到超额阈值前设置告警。
  6. iQ标签默认异步加载——但第三方标签仍可能阻塞页面渲染。使用标签超时功能取消加载缓慢的标签。将分析标签放在加载顺序的首位。
  7. 连接器重试逻辑为1分钟→5分钟→30分钟——若三次重试均失败，请求将被丢弃。请在连接器仪表板监控错误率。错误率超过阈值会触发自动限流。
  8. 无法同时在管理UI中打开两个标签页——且会话经常过期，需要重新登录。这是已知的UX限制。

Related skills

相关技能

  • /sales-cdp
    — CDP comparison and selection strategy across Tealium, Segment, BlueConic, mParticle, Treasure Data
  • /sales-blueconic
    — BlueConic CDP — profile unification, segmentation, audience activation
  • /sales-treasuredata
    — Treasure Data enterprise CDP — profile unification, 400+ connectors, AI Marketing Cloud
  • /sales-data-hygiene
    — CRM data quality, deduplication, enrichment automation
  • /sales-retargeting
    — Retargeting strategy, audience activation to ad platforms
  • /sales-integration
    — Connect sales tools with webhooks, Zapier/Make, APIs
  • /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
    — 跨Tealium、Segment、BlueConic、mParticle、Treasure Data的CDP对比与选型策略
  • /sales-blueconic
    — BlueConic CDP — 档案统一、细分、受众激活
  • /sales-treasuredata
    — Treasure Data企业级CDP — 档案统一、400+连接器、AI营销云
  • /sales-data-hygiene
    — CRM数据质量、去重、 enrichment自动化
  • /sales-retargeting
    — 重定向广告策略、受众向广告平台激活
  • /sales-integration
    — 通过webhook、Zapier/Make、API连接销售工具
  • /sales-do
    — 不确定使用哪个技能？该路由工具可将任何销售目标匹配到合适的技能。安装命令：
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: Connector data not flowing

示例1：连接器数据无法流动

User says: "I set up a Facebook connector in EventStream but no audiences are appearing in Facebook Ads Manager." Skill does: Walks through connector diagnostics — check the connector run history for errors, verify segment has matching profiles, confirm attribute mapping between Tealium and Facebook Custom Audiences, check sync frequency, and test with a manual trigger. Result: User identifies the misconfigured field mapping and gets audiences flowing.
用户提问：“我在EventStream中设置了Facebook连接器，但Facebook广告管理器中没有显示任何受众。” 技能操作：引导进行连接器诊断——检查连接器运行历史中的错误、验证细分群体是否有匹配的档案、确认Tealium与Facebook自定义受众之间的属性映射、检查同步频率、并通过手动触发进行测试。 结果：用户发现字段映射配置错误，受众数据恢复正常流动。

Example 2: Tags slowing down the site

示例2：标签拖慢网站速度

User says: "Our site load time increased by 3 seconds after we added Tealium iQ. How do I fix this?" Skill does: Explains async loading best practices, tag timeout configuration, load rule optimization, and tag prioritization. Recommends moving high-priority analytics tags to the top and setting 5-second timeouts on slower vendor tags. Result: User reduces tag-related page load impact from 3 seconds to under 500ms.
用户提问：“添加Tealium iQ后，我们的网站加载时间增加了3秒。如何解决？” 技能操作：讲解异步加载最佳实践、标签超时配置、加载规则优化和标签优先级设置。建议将高优先级分析标签放在首位，并为加载缓慢的供应商标签设置5秒超时。 结果：用户将标签对页面加载的影响从3秒降低至500毫秒以下。

Example 3: Choosing Tealium vs Segment

示例3：选择Tealium还是Segment

User says: "We're evaluating Tealium and Segment for our CDP. We have a 10-person marketing team and need audience activation." Skill does: Routes to 
/sales-cdp
for cross-platform comparison, noting Tealium's marketer-friendly AudienceStream vs Segment's developer-first approach, implementation timelines, and pricing models. Result: User has a clear framework for choosing based on their team composition and use case.
用户提问：“我们正在评估Tealium和Segment作为CDP。我们有10人的营销团队，需要受众激活功能。” 技能操作：路由至
/sales-cdp
进行跨平台对比，指出Tealium面向营销人员的AudienceStream与Segment面向开发人员的定位差异、实施周期和定价模型。 结果：用户获得了基于团队构成和使用场景的清晰选型框架。

Troubleshooting

故障排查

Visitor profiles not merging across channels

跨渠道访客档案未合并

Symptom: Same customer has multiple Tealium visitor profiles (one from web, one from mobile, one from email) Cause: No shared identifier connecting the profiles. Visitor Switching requires a matched identifier (typically email or customer ID). Solution: Implement progressive identification — capture email/login on web, pass customer ID in mobile SDK. Review Visitor Switching configuration in AudienceStream. Test merge rules in QA environment before deploying to production.
症状：同一客户拥有多个Tealium访客档案（一个来自网页、一个来自移动端、一个来自邮件） 原因：没有共享标识符连接这些档案。访客切换需要匹配的标识符（通常是邮箱或客户ID）。 解决方案：实施渐进式身份识别——在网页端捕获邮箱/登录信息，在移动SDK中传递客户ID。检查AudienceStream中的访客切换配置。在部署到生产环境前，在QA环境测试合并规则。

Connector action failing with 429 errors

连接器操作返回429错误

Symptom: Connector shows high error rate, destination system receiving no data Cause: Tealium's overload protection is throttling due to destination rate limits being exceeded Solution: Enable frequency capping on the connector action to spread requests over time. Check destination's rate limits and configure Tealium to stay within them. If the destination supports bulk endpoints, switch to batch mode.
症状：连接器错误率高，目标系统未收到数据 原因：Tealium的过载保护因超出目标系统速率限制而触发限流 解决方案：在连接器操作中启用频次限制，将请求分散到不同时间。检查目标系统的速率限制，配置Tealium使其保持在限制范围内。如果目标系统支持批量端点，切换到批量模式。

iQ utag.js not loading on SPA

iQ utag.js在单页应用（SPA）中未加载

Symptom: Tags fire on initial page load but not on subsequent route changes in React/Angular/Vue Cause: Tealium doesn't detect client-side route changes by default Solution: Call 
utag.view(data_layer_object)
after each SPA route change. In React, use a 
useEffect
hook that triggers on route change. Ensure the data layer object includes updated page_name and page_type values for each virtual page view.
症状：标签在初始页面加载时触发，但在React/Angular/Vue的后续路由变更时未触发 原因：Tealium默认无法检测客户端路由变更 解决方案：每次SPA路由变更后调用
utag.view(data_layer_object)
。在React中，使用
useEffect
钩子监听路由变更。确保数据层对象包含每个虚拟页面视图的更新后的page_name和page_type值。