A segmentation fork is a Bloomreach Engagement scenario node that splits customers into separate branches, one for each segment of a saved segmentation. Each group then takes its own path. A scenario can hold up to 5 segmentation forks. A segmentation used this way can have up to 20 segments. Segmentations with parameters are not supported. The common failure is editing the segmentation afterwards. A deleted or renamed segment keeps its branch but passes 0 customers, and a new segment gets no branch. Both stay that way until you open the node, which shows a warning, and click `Update Segmentation`.
Category
Bloomreach Campaigns, Marketing Automation
Also known as
segmentation fork node; segmentation split
In practice
Treat a segmentation that feeds a running fork as a shared dependency and rename segments only with the scenario open. If you need just one group out of a large segmentation, a condition node is cheaper than a fork.
Something out of date?