Introduction
In some courses, it might be interesting to want to separate the population according to a combination of criteria. In order to identify this population, it is possible to use the node "Decision according to email reaction".
Decision according to segment membership
This node is located in the "Decision" section. It separates the population from the previous node into two based on segment membership.
Segment separation: Any lines entering the node and belonging to the selected segment will go to the top branch. The rest will go to the bottom branch.
Depending on the deduplication of the separation segment defined in Queryly, the key used to identify segment membership in the incoming population will be different:
- If no particular deduplication has been set, the population will be separated according to customer ID.
- If the separation segment has one line per contract, (deduplication to contract has been disabled on queryly), then the population entering the node will be separated according to contract ID. This field must therefore be present in the incoming population. This field must be named
contract_numberly_contract_id.
Conclusion
The population of a journey can be split in two based on segment membership.