Something to keep in mind is how it will be used. As you mentioned, Segmentations are resource intensive. So if you need to immediately use a Segment after a corresponding data value has changed, that may be problematic.
For example: Let's say you have a form that is enriched by a data vendor setting Industry. When someone submits the form, there is a choice step in the Flow to add them to a specific list based on Segmentation. It's very possible that the Flow will run before the Segmentation is set.
CDVs get committed to the DB immediately without any delay (i.e., you don't need to add a wait step after a CDV to use the new value), but post a CDV, the segmentation update might take a while, unlike a smart list that directly reads data on the fly from the DB when queried.
PS: for anyone wondering, CDV = Change Data Value.
Something to keep in mind is how it will be used. As you mentioned, Segmentations are resource intensive. So if you need to immediately use a Segment after a corresponding data value has changed, that may be problematic.
For example: Let's say you have a form that is enriched by a data vendor setting Industry. When someone submits the form, there is a choice step in the Flow to add them to a specific list based on Segmentation. It's very possible that the Flow will run before the Segmentation is set.
In this case, a Smart List is preferred.
Agreed! Great point, Xander.
CDVs get committed to the DB immediately without any delay (i.e., you don't need to add a wait step after a CDV to use the new value), but post a CDV, the segmentation update might take a while, unlike a smart list that directly reads data on the fly from the DB when queried.
PS: for anyone wondering, CDV = Change Data Value.