Back to Details

sf-datacloud-segment

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

sf-datacloud-segment: Data Cloud Segment Phase

sf-datacloud-segment: Data Cloud 细分阶段

Use this skill when the user needs audience and insight work: segments, calculated insights, publish workflows, member counts, or troubleshooting Data Cloud segment SQL.
当用户需要进行受众与洞察相关工作时使用此Skill：细分群体管理、计算洞察、发布工作流、成员数量统计，或排查Data Cloud细分群体SQL问题。

When This Skill Owns the Task

此Skill负责的任务场景

Use 
sf-datacloud-segment
when the work involves:
  • sf data360 segment *
  • sf data360 calculated-insight *
  • segment publish workflows
  • member counts and segment troubleshooting
  • calculated insight execution and verification
Delegate elsewhere when the user is:
  • still building DMOs, mappings, or identity resolution → sf-datacloud-harmonize
  • activating a segment downstream → sf-datacloud-act
  • writing read-only SQL or search-index queries → sf-datacloud-retrieve
当工作涉及以下内容时，使用
sf-datacloud-segment
：
  • sf data360 segment *
  • sf data360 calculated-insight *
  • 细分群体发布工作流
  • 成员数量统计与细分群体问题排查
  • 计算洞察执行与验证
当用户进行以下工作时，委托给其他Skill：
  • 仍在构建DMO、映射或身份解析 → sf-datacloud-harmonize
  • 下游激活细分群体 → sf-datacloud-act
  • 编写只读SQL或搜索索引查询 → sf-datacloud-retrieve

Required Context to Gather First

首先需要收集的必要上下文

Ask for or infer:
  • target org alias
  • unified DMO or base entity name
  • whether the user wants create, publish, inspect, or troubleshoot
  • whether the asset is a segment or calculated insight
  • expected success metric: member count, aggregate value, or publish status
询问或推断：
  • 目标组织别名
  • 统一DMO或基础实体名称
  • 用户需求是创建、发布、查看还是排查问题
  • 资产类型是细分群体还是计算洞察
  • 预期成功指标：成员数量、聚合值或发布状态

Core Operating Rules

核心操作规则

  • Treat Data Cloud segment SQL as distinct from CRM SOQL.
  • Run the shared readiness classifier before mutating audience assets: 
    node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase segment --json
    .
  • Prefer reusable JSON definitions for repeatable segment and CI creation.
  • Use 
    --api-version 64.0
    when segment creation behavior is unstable on newer defaults.
  • Verify with counts or SQL after publish/run steps instead of assuming success.
  • Use SQL joins rather than 
    segment members
    when readable member details are needed.
  • 将Data Cloud细分群体SQL与CRM SOQL区分开。
  • 在修改受众资产前运行共享就绪度分类器：
    node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase segment --json
    。
  • 对于可重复的细分群体和CI创建，优先使用可复用的JSON定义。
  • 当新版本默认设置下细分群体创建行为不稳定时，使用
    --api-version 64.0
    。
  • 发布/运行步骤完成后，通过数量统计或SQL验证结果，不要默认操作成功。
  • 当需要可读的成员详情时，使用SQL连接而非
    segment members
    。

Recommended Workflow

推荐工作流

1. Classify readiness for segment work

1. 细分群体工作就绪度分类

bash
node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase segment --json
bash
node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase segment --json

2. Inspect current state

2. 查看当前状态

bash
sf data360 segment list -o <org> 2>/dev/null
sf data360 calculated-insight list -o <org> 2>/dev/null
bash
sf data360 segment list -o <org> 2>/dev/null
sf data360 calculated-insight list -o <org> 2>/dev/null

3. Create with reusable JSON definitions

3. 使用可复用JSON定义创建

bash
sf data360 segment create -o <org> -f segment.json --api-version 64.0 2>/dev/null
sf data360 calculated-insight create -o <org> -f ci.json 2>/dev/null
bash
sf data360 segment create -o <org> -f segment.json --api-version 64.0 2>/dev/null
sf data360 calculated-insight create -o <org> -f ci.json 2>/dev/null

4. Publish or run explicitly

4. 显式发布或运行

bash
sf data360 segment publish -o <org> --name My_Segment 2>/dev/null
sf data360 calculated-insight run -o <org> --name Lifetime_Value 2>/dev/null
bash
sf data360 segment publish -o <org> --name My_Segment 2>/dev/null
sf data360 calculated-insight run -o <org> --name Lifetime_Value 2>/dev/null

5. Verify with counts or SQL

5. 通过数量统计或SQL验证

bash
sf data360 segment count -o <org> --name My_Segment 2>/dev/null
sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "UnifiedssotIndividualMain__dlm"' 2>/dev/null
bash
sf data360 segment count -o <org> --name My_Segment 2>/dev/null
sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "UnifiedssotIndividualMain__dlm"' 2>/dev/null

High-Signal Gotchas

关键注意事项

  • Segment creation can require 
    --api-version 64.0
    .
  • segment members
    returns opaque IDs; use SQL joins when human-readable member details are needed.
  • Segment SQL is not SOQL.
  • Calculated insight assets and segment SQL have different limitations.
  • Publish/run steps may kick off asynchronous work even when the command returns quickly.
  • An empty segment or calculated-insight list usually means the module is reachable but unconfigured, not unavailable.
  • 细分群体创建可能需要使用
    --api-version 64.0
    。
  • segment members
    返回不透明ID；当需要人类可读的成员详情时，使用SQL连接。
  • 细分群体SQL不是SOQL。
  • 计算洞察资产和细分群体SQL有不同的限制。
  • 即使命令快速返回，发布/运行步骤可能会启动异步工作。
  • 空的细分群体或计算洞察列表通常意味着模块可访问但未配置，而非不可用。

Output Format

输出格式

text
Segment task: <segment / calculated-insight>
Action: <create / publish / inspect / troubleshoot>
Target org: <alias>
Artifacts: <definition files / commands>
Verification: <member count / query result / publish state>
Next step: <act / retrieve / follow-up>
text
Segment task: <segment / calculated-insight>
Action: <create / publish / inspect / troubleshoot>
Target org: <alias>
Artifacts: <definition files / commands>
Verification: <member count / query result / publish state>
Next step: <act / retrieve / follow-up>

References

参考资料

  • README.md
  • ../sf-datacloud/assets/definitions/calculated-insight.template.json
  • ../sf-datacloud/assets/definitions/segment.template.json
  • ../sf-datacloud/references/feature-readiness.md
  • ../sf-datacloud/UPSTREAM.md
  • README.md
  • ../sf-datacloud/assets/definitions/calculated-insight.template.json
  • ../sf-datacloud/assets/definitions/segment.template.json
  • ../sf-datacloud/references/feature-readiness.md
  • ../sf-datacloud/UPSTREAM.md