Segmenting Datacloud

segmenting-datacloud: Data Cloud Segment Phase

Use this skill when the user needs audience and insight work: segments, calculated insights, publish workflows, member counts, or troubleshooting Data Cloud segment SQL.

When This Skill Owns the Task

Use segmenting-datacloud 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 Data Model Objects (DMOs), mappings, or identity resolution → harmonizing-datacloud
• activating a segment downstream → activating-datacloud
• writing read-only SQL or search-index queries → retrieving-datacloud

---

Required Context to Gather First

Ask for or infer:

• target org alias
• unified DMO (Data Model Object) 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

---

Core Operating Rules

• Treat Data Cloud segment SQL as distinct from CRM SOQL.
• Run the shared readiness classifier from the orchestrating-datacloud skill before mutating audience assets: node ../orchestrating-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.

---

Recommended Workflow

1. Classify readiness for segment work

node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase segment --json

2. Inspect current state

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

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

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

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.

---

Output Format

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
• ../orchestrating-datacloud/assets/definitions/calculated-insight.template.json
• ../orchestrating-datacloud/assets/definitions/segment.template.json
• ../orchestrating-datacloud/references/feature-readiness.md
• ../orchestrating-datacloud/UPSTREAM.md

Credits & Acknowledgments

This skill is part of the *-datacloud family of skills covering the Salesforce Data Cloud workflow phases. Shared definitions, templates, and readiness scripts for this family live in the orchestrating-datacloud skill directory.

segmenting-datacloud

Audience and insight workflows for Salesforce Data Cloud.

Use this skill for

• creating and publishing segments
• managing calculated insights
• checking segment counts
• troubleshooting segment SQL
• understanding why a segment is empty or unexpectedly large

Example requests

"Create a high-value customer segment in Data Cloud"
"Why is my segment returning zero members?"
"Run this calculated insight and help me verify it"
"Show me how to get member counts for this segment"

Common commands

sf data360 segment list -o myorg 2>/dev/null
sf data360 segment create -o myorg -f segment.json --api-version 64.0 2>/dev/null
sf data360 segment publish -o myorg --name High_Value_Customers 2>/dev/null
sf data360 calculated-insight list -o myorg 2>/dev/null

References

• SKILL.md
• ../orchestrating-datacloud/assets/definitions/calculated-insight.template.json
• ../orchestrating-datacloud/assets/definitions/segment.template.json
• CREDITS.md