Managing Segment Maps and Segments

On the Segments page, you can rename, copy, delete, and open (for editing) a segment map. You can also rename and open a segment. When you open a segment map, the entire map diagram is centered and scaled to fit within the window. You can right-click the area around the nodes in the map to zoom to specific areas in the map or to select a node in the map. For more information, see Navigate the Map.

Note: The count that is displayed above the Segment Maps and Segments table indicates the number of rows for both segment maps and segments.

Selecting Actions on the Segment Maps and Segments Table

Select the segment map or segment in the Segment Maps and Segments table and select the appropriate action.

To rename a segment map or segment, click and select Rename.
You cannot rename a segment with a status of Completed or Ended. If you rename a segment map that is published, it becomes out of sync and must be republished.
To copy a segment map, click and select Copy.
Note: This action is not available for segments.
To open a segment map or segment for editing, click .
Alternatively, click the name of the segment map or segment in the list.
To delete a segment map, click .
You can delete a segment map that is published.

Note: This action is not available for segments.

TipAfter you rename a segment that is included in a segment map, when you return to the segment map, you might need to click Refresh

to see the change.

Using Save As to Create a Segment Map

To save a segment map with a different file name, open the segment map, click Options , and then select Save As. Enter a name and click Save. You can also save a segment map with a different file name by opening a segment that is being used by the segment map from the Segment Maps and Segments table and then clicking Options .

When you use Save As to create a segment map, new IDs are generated for the nodes in the new map.

Note: You cannot save a segment with a different file name.

Understanding Node Status

The nodes in your segment map might include a status icon that provides the following information about that node.

Segment Map Node Statuses
Status Icon	Description
No status icon (blank)	The node contains criteria, but the count is not calculated.
	The node is complete and contains a count.
	A node with this icon is incomplete. An example of an incomplete node is a node that does not contain criteria. For example, when you first add a node, it is incomplete until you open the node and add criteria to it. Note: While a node is incomplete, you cannot update the node counts on the segment map.
	The member count failed. You can choose to update the count on the segment map to try again.
	The member count is currently being calculated.

View Counts

A node count represents the number of people who satisfy the criteria listed in the node.

When an on-premises segment map is executed, the following nodes always produce a count:

a node that is marked as a segment. For more information, see Mark Node as a Segment.
a node with the Always generate a count for this node option selected. For more information, see Specify That a Count Is Always Generated.
Note: This option is available for the Criteria, AND, and OR nodes only.
all Process nodes.
all Export nodes. The count appears at the top of the Properties window for the node.
nodes that are marked as linkable when a static list needs to be uploaded for the segment map (that is, when the Use the most current data when referenced by a link setting is not selected). For more information, see Enable Current Data to Be Used by Linked Nodes.

Note: Counts are generated for the nodes that are directly upstream from nodes that run stored processes. The counts for these upstream nodes generate input tables that the stored processes must run code against. If a Criteria node is connected to only AND and OR nodes, and if neither of these nodes is connected to any other node, the Criteria, AND, and OR nodes might be optimized such that only the final node in the sequence produces a count.

To update the segment count for all nodes in your map, click More options and select Update counts from the drop-down menu. To update counts, all nodes must be Complete Node status, complete .

To update the count for a single node, open the node and click Update counts .

To view node counts for independent branches in the same segment map, right-click a Criteria node in each path and select Update counts each time. Independent branches are sets of nodes that do not share an upstream node. The counts are returned independently to the map after the execution has completed for a branch or node. Multiple count requests for independent branches reduces the wait time that is required for all the components of an on-premises segment map.

To obtain a partial update of counts in a segment map:

Update the criteria for a node in the map and save your changes. The existing count for the node is cleared.
Select the updated node.
Click Update counts.
Counts are updated in the selected node and in any nodes that are downstream from the node. The counts for upstream nodes are not changed.

To display the detailed progress of an ongoing count update, click More options and select Show update counts progress from the drop-down menu. On the Update Counts Progress page, a progress bar indicates the percent completion status for the count update. To create a record of count updates, click Download Details to download a JSON that contains the information from the Progress table.

Note:

The total completion time that is displayed for the count update represents the time interval for only the on-premises processing of items. The time interval for processing of items by the cloud is not included in the displayed completion time. Therefore, the node in your segment map could show that it is still processing even after the count update is complete.
Progress information is cleared after the count update is completed and the Update Counts Progress page is closed.
If a user saves a segment map after requesting an updated count and then either closes the map or the user's session times out, the new count for the map is saved and displayed the next time that the map is opened.
When a scheduled segment map runs while it is in the Active status and Out of Sync status, the nodes in the segment map are not updated with new counts.
If a user manually runs a segment map and then saves the segment map before the run completes, the counts for only the nodes that have completed processing are updated and saved. The user has the option to update the counts for the remaining nodes when the segment map is reopened.

You can reset the counts on all nodes at any time by clicking Clear counts.

Opening a Segment Map That Is Running Counts

If you open a segment map that is in the process of running node counts, you can modify only the portions of the segment map that are not running counts. To enable counts in the segment map to continue running until completion, click Continue Counts. To abandon counts in the segment map that is still running, click Abandon Counts.

Note: The Abandon Counts button is not visible when the segment map is locked by another user while the node counts are running.

Navigate the Map

Click More options and select More to specify one of the following actions:

Pan: moves the map so that different parts of it are displayed.
Snap to grid: aligns nodes with each other when nodes are added or moved.
Overview Window: displays a navigation window for your map.
Create summary report: creates an .xlxs file that contains summary information about the segment map.
Group: collapses selected nodes into a single group node. For more information, see Using Groups.
Ungroup: expands individual nodes that are in a group node. For more information, see Using Groups.

You can right-click the area around the nodes to see a complete set of actions that you can take on the map. The following additional options are available by right-clicking the map workspace:

Select all nodes.
Zoom to make the map larger or smaller.
Select a different Layout to change the orientation of the map.
Click Find item to quickly select a node in your map.

Work with Nodes and Paths

You can right-click a node or path to see a set of actions that you can take. For example, by right-clicking a node, you can select one of these actions:

Note: Some actions might not be available for a selected node.

Open to display the properties of the node.
Update counts to reset the counts for the node.
Add (Before) and Add (After) to add nodes either as input or output nodes.
Combine output to combine the output for Split nodes after pressing the Ctrl key while clicking each node. To undo the creation of a Split node with combined output, right-click the Split output node that was previously combined and select Separate output. For more information, see Set Properties for a Split Node.
Copy (Ctrl+C) and Cut (Ctrl+X). For more information, see Copying and Pasting Nodes.
Show summary to show the summary of the targeting criteria for the node.
Select Mark node as segment to save the members of the node in your flow as a segment. Because the segment that is created from a node is associated with the larger segment flow, it inherits the status of that segment map. As a result, when you change the status of the segment map, the node segment status is updated automatically on the Segment Maps and Segments page.
The segment appears on the Segments tab in the segment map and in the table on the Segment Maps and Segments page. For more information, see Mark Node as a Segment.

Note: By default, there is a 5,000 daily limit on the number of on-premises segments that can be processed. If you need this limit adjusted, contact SAS Technical Support.
Unmark node as segment to undo the Mark node as segment action.
Mark node as linkable to enable the node to link to other segments.
Unmark node as linkable to undo the Mark node as linkable action.
Run export to execute an Export node without publishing the segment map.
Run process to execute a Process node without publishing the segment map.

Copying and Pasting Nodes

You can copy and paste nodes into the same on-premises segment map or into a different on-premises segment map. Copying and pasting can increase productivity because you can reuse complex node settings and selected sections of the segment map instead of re-creating existing items.

You cannot copy and paste nodes between on-premises segment maps that are in different business contexts. You must copy and paste nodes within the same browser tab.

To copy a selected node, click Options on the Segment Map tab and select Copy (Ctrl+C). To paste a copied node, click Options on the Segment Map tab and select Paste (Ctrl+V).

The following considerations apply when you copy and paste nodes into an on-premises segment map:

All nodes

A pasted node is named nodename (n), where n is an incremented number (for example, Employed = Full Time 1) unless the name of the source node ends in a number. If the source node ends in a number, another number is appended to the name (for example, Employed = Full Time 1 1).

When nodes are pasted, settings are retained, but the node status is reset and counts are cleared.

When a pasted node references a variable and the source of the variable is not copied, the node status is Incomplete ( Node Status, Incomplete ).

When you copy and paste a node in a segment map, new codes are created for the new nodes if SAS Customer Intelligence 360 is configured to use the Automatic Editable or Automatic Not-Editable code settings. If SAS Customer Intelligence 360 is configured to use the Manual code setting, the new node has the same code as the source node. For more information, see Code Settings in SAS Customer Intelligence 360: Administration Guide.

AND node

If an AND node is copied and the upstream nodes are not included, the subject is undefined and no items appear in the Input Nodes table in the pasted node. In this instance, the status of the AND node is Incomplete.

Export node

You cannot change the export definition or the contents of the export file in an Export node that is pasted by itself. This restriction does not apply to an Export node that is pasted with upstream nodes.
If the subject of the Export node does not match the subject of the input node, you must change the input subject or remove the existing export content, and then specify new content.
Refine output specifications are retained. If you are pasting the Export node within a segment map, the node reference is retained only if the Export node, refine output references, and all of the intervening nodes necessary to make the refine output reference valid are copied and pasted at the same time. When the Export node is pasted into the same segment map and the node that is the source for refine output is a terminal node and is included in the copy, the refine output reference is to the pasted node. If the terminal refine output node is not part of the copied set of nodes, the reference is to the original refine output node.

Limit node

The Incoming and Actual fields are blank in the pasted node.
You cannot select a data item on the Sort tab if the pasted node is not connected to an input node with a selected subject.

Link node

If a node is assigned to a Link node and the Link node is pasted into the segment map from which the node originates, the Link node is cleared. The Link node is set to an Incomplete state.

Map node

If the Map node is pasted without a connecting node upstream, the From subject is set to Undefined. Only a node with a subject that is compatible with the To subject can be connected to the Map node as an input node.

OR node

If an OR node is copied and the upstream nodes are not included, the subject is undefined and no items appear in the Input Nodes table in the pasted node.

Prioritize node

Generated output nodes are pasted only if the relevant input nodes are included in the copy.
Output nodes cannot be copied by themselves; they must be included in a copy of the node.
Output nodes are pasted in the same relative position as the original output nodes.
If enabled, the Remainder node is pasted with the Prioritize node (if relevant input nodes are included in the copy).

Process node

If a process has been selected, the following considerations apply:

All parameters are copied with their values if the values are set.
Output nodes cannot be copied by themselves; they must be included in a copy of the node.
Output nodes are pasted in the same relative position as the original output nodes.
All of the generated nodes of a Process node are automatically included with the node when the node is pasted into the same diagram.

Split node

All parameters are copied with their values if the values are set.
Output nodes cannot be copied by themselves; they must be included in a copy of the node.
Output nodes are pasted in the same relative position as the original output nodes.
All of the generated nodes of a Split node are automatically included with the node when the node is pasted into the same diagram. The exception is when the split is made using values from a previous node and the previous node was not copied. In this case an empty Split node is pasted.
When a Split node uses values from a previous node and is pasted into the same diagram without pasting the previous node and all of the nodes between the previous node and the Split node, the Split node has a Not ready status. The status is Not ready until you reconnect the previous node to the Split node or you change the Split method selection in the Split node.

Mark Node as a Segment

Marking a Node as a Segment

Note: Nodes that produce output nodes (Split, Prioritize, and Process nodes) cannot be marked as segments.

Select Mark node as segment to save the members of the node in your flow as a segment. Because the segment that is created from a node is associated with the larger segment flow, it inherits the status of that segment map. As a result, when you change the status of the segment map, the node segment status is updated automatically on the Segment Maps and Segments page.

The Code is a unique identifier for the segment.
In the Segment properties field, click the Review and make changes link to edit and view custom segment properties, and to complete any missing fields that are required to mark the segment as Ready in the Manage Segment Properties window.
The Review and make changes link does not appear if custom properties are not available. For more information, see Custom Properties.
Enable Add context to segment to include contextual information about why a subject was selected, for example because the individual was a member of a specific a household. For more information, see Add Context to a Segment.

If a node that has a Ready status is at an incompatible subject level, the parent node or output nodes cannot be marked as a segment.

Note:

By default, there is a 5,000 daily limit on the number of on-premises segments that can be processed. If you need this limit adjusted, contact SAS Technical Support.
The Mark node as segment check box is selectable only for nodes that have a defined subject level.
Custom properties and their values that are in a grid cannot be exported.

To view information about nodes that have been marked as segments, click on the Segment Map tab.

Add Context to a Segment

Add contextual information when you want to associate members of a segment with additional data about their associations. This data could identify individuals as members of a household or associated with a specific bank account. For more information, see Contextual Information for Identities in SAS Customer Intelligence 360: Administration Guide.

IMPORTANT Do not add personally identifiable information (PII) as contextual information, because the context values are stored in the Unified Data Model (UDM) tables.

To add context to a segment:

Click Select a node to choose a context node from another subject level in the segment map. The context node must have a direct relationship with the subject level of the segment node. The subject-level relationships are defined in the information map. The subject level of the segment node and the context node are displayed in the segment information table.
Note: If you change the subject level of the segment node, your selection for the context node is cleared and the count is reset for the segment node.

An available context node must meet the following requirements:
- The context node must be upstream of the segment node or in a disconnected set of nodes.
- The context node must be at a different subject level than the segment node.
Adding a context to a segment could result in multiple subjects in the context matching a single subject in the segment if the relationship between the subject level for the segment node and the subject level for the context node is one-to-many or many-to-many. For example, a customer could hold many accounts at a bank. Adding context to the segment of Customers could result in multiple context subjects (Accounts) matching a single subject (Customer) in the segment.

Segments must be unique collections of subjects. If this type of one-to-many or many-to-many subject-level relationship exists, you must specify a sorting criterion to select one context subject to add to the segment for each subject in the segment. The sort criteria selection is mandatory if the relationship is one-to-many or many-to-many. If the relationship between the subject levels is many-to-one or one-to-one, then this sort criteria is not required.
(Optional) Check Remove segment members that do not have context to remove rows in the segment file that do not contain associated context values. Blank values occur when there is no context information for a specific subject ID in the segment node based on the context node.
Note:
- Selecting this option could potentially reduce the number of subjects in the segment because subject IDs with no context information are removed from the segment content.
- Counts for the segment node are cleared when the selection for this option is changed.
- When this option is enabled in a segment node that contains added context and the criteria for the context node is then changed, the count on the segment node is cleared.

Mark Node as Linkable

Note: Nodes that produce output nodes (Split, Prioritize, and Process nodes) cannot be marked as linkable.

Select Mark node as linkable if you want to use this node as input to Link nodes in other segment maps. The Link nodes in the segment map must be active before the segment map can be published.

You can always mark any node that is in the Not ready status as linkable except the Split and Prioritize nodes. You can also always mark output nodes that are in the Not ready status as linkable.

Note: To ensure that the most recent subject results are used in the consumer segment map, enable the Use the most current data when referenced by a link option by selecting Orchestration

Linking Information in this segment map.

When you reference a linkable node where the Use the most current data when referenced by a link option is disabled, a static linkable population is not available in SAS Customer Intelligence 360 if the segment map that contains the linkable node has never been executed.

If you attempt to execute a segment map that contains a Link node that references a source linkable node with the disabled option, the execution fails because no static population is available. In this same situation, the Update counts and Run export commands succeed because these operations ignore the static nature of the source linkable node and generate a temporary population. However, execution operations do not ignore this setting and result in failures when no static population exists.

To avoid possible execution failures, ensure that the source segment map has been executed and has uploaded a static population before you execute the segment map that contains the Link node.

To unmark a node as linkable, right-click a node, which displays Link Icon , and select Unmark node as linkable.

Note: Unmarking a node as linkable might cause a segment map to be out of sync. The

symbol appears next to the segment map in the list on the Segments page.

Enable Current Data to Be Used by Linked Nodes

On the Linking Information tab for a segment map, click Use the most current data when referenced by a link to display the most recent data. This data applies to segment maps that contain nodes that are marked as linkable. When a segment map contains a Link node whose source is a segment map (which is configured to Use the most current data when referenced by a link), the data for the source node is refreshed. The updated data is sent to the Link node when the segment map that contains the Link node is executed. The counts might vary between the source segment map and the segment map that contains the Link node. The segment map that contains the Link node is updated only when that segment map is opened.

If Use the most current data when referenced by a link is not selected, the dynamic and static executions for link maps occur in the following ways:

Dynamic execution: The source map linkable node is run when the link map is executed in order to obtain the population required by the Link node in the link map.
Static Execution: The specified static source population that was previously generated for the source map linkable node obtains the population required by the Link node in the link map.

The following table lists and describes the link map execution behaviors when Use the most current data when referenced by a link is not selected:

Link Map Execution Behaviors
Source Map State	Execution Behavior
Active not executed	Dynamic
Active executed	Static
Active failed execution	Static - If previously successful, uses the latest source map execution static list population.
Active failed execution	Dynamic - If not previously successful and no static list population is available.

View Segment Map History

To see a list of changes for a segment map, navigate to the Orchestration tab and select the History page.

On the Occurrence page, only information about newer occurrences appears in the Started by and Occurrence Type columns in the Occurrence table. The columns are empty for older occurrences. Information about scheduled occurrences also does not appear in the Started by column.

Using Groups

Use groups to group similar nodes together and simplify a large segment map. For example, you can group nodes that contain repeating logic or group nodes that belong together based on a business requirement.

Select two or more items, such as multiple nodes or a group and a node, to create a group. Double-click the group to add a name and description for the group.

A group contains the following options:

Group: collapses selected nodes into a single group node. This option is available when two or more items are selected.
Ungroup: expands individual nodes that are in a group node. This option is available when a group is selected.
Change icon: Select an icon from the drop-down menu to change the icon for the group.
Change icon color: Select a color from the drop-down menu to change the color of the icon for the group.
Expand: Expand a group and display all the nodes in the group.
Collapse: Shrink a group to a box that contains the group name and icon.

Last updated: August 11, 2026