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

3. Create with reusable JSON definitions

4. Publish or run explicitly

5. Verify with counts or SQL

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

References

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

3. Create with reusable JSON definitions

4. Publish or run explicitly

5. Verify with counts or SQL

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.

Documentation

Documentation

segmenting-datacloud: Data Cloud Segment Phase

When This Skill Owns the Task

Required Context to Gather First

Core Operating Rules

Recommended Workflow

1. Classify readiness for segment work

2. Inspect current state

3. Create with reusable JSON definitions

4. Publish or run explicitly

5. Verify with counts or SQL

High-Signal Gotchas

Output Format

References

Documentation

segmenting-datacloud

Documentation

segmenting-datacloud: Data Cloud Segment Phase

When This Skill Owns the Task

Required Context to Gather First

Core Operating Rules

Recommended Workflow

1. Classify readiness for segment work

2. Inspect current state

3. Create with reusable JSON definitions

4. Publish or run explicitly

5. Verify with counts or SQL

High-Signal Gotchas

Output Format

References