Skip to main content
Solved

Using Other Segments in a Segment Definition

  • January 5, 2026
  • 2 replies
  • 33 views

jjensen_ksp
Problem Solver I
Forum|alt.badge.img+5

Hello,

 

I would like to define a segment and use “Is not in segment xyz” or “is in segment xyz”.

I have multiple use cases.

One example is that I have a segment called VIP. And there’s some definition that make a profile a VIP.

 

I might want to look at a segment of profiles that are VIP but have also performed an action in the last 30 days.

 

Today, I’m duplicating the VIP definition and adding the new condition to the definition. But when the definition of VIP changes, someone needs to know they also have to update the definition of the other segments to match.

If we could use segment data within segments, a lot of problems get solved.

 

Does this feature exist and I can’t see it? Or is there another way I can manage the layered definitions in a way that is organized?

Best answer by Mike-H

This is interesting for sure, but no, I don’t think you can use “is in segment x” as a condition inside the definition of “segment y”.

Segments are calculated in real-time so if you have nested segments, or a segment that relies on an update from another segment, that can create complex processing loops to say the least.

Questions…

Do you plan to send one-off newsletters to this group, or is this for an automated flow?

Is your VIP definition based on 'lifetime spend' (permanent) or a 'rolling window' (like, ordered in the last 90 days)?

2 replies

Mike-H
Problem Solver II
Forum|alt.badge.img+11
  • Problem Solver II
  • Answer
  • January 5, 2026

This is interesting for sure, but no, I don’t think you can use “is in segment x” as a condition inside the definition of “segment y”.

Segments are calculated in real-time so if you have nested segments, or a segment that relies on an update from another segment, that can create complex processing loops to say the least.

Questions…

Do you plan to send one-off newsletters to this group, or is this for an automated flow?

Is your VIP definition based on 'lifetime spend' (permanent) or a 'rolling window' (like, ordered in the last 90 days)?


jjensen_ksp
Problem Solver I
Forum|alt.badge.img+5
  • Author
  • Problem Solver I
  • January 6, 2026

Hi Mike,

Loops would be the issue wouldn’t it. If the loops could be avoided, the calculation should be no different than if I were to copy all the conditions into one segment. (Although complexities might be hidden, wrapped in a segment)

In my example the VIP definition would be controlled by a marketing team that decides what a “VIP” is. And an ecommerce team would decide to give a filtered selection of the VIPs a juicy deal.

I’ve wanted the ability for flows and one offs. I’ve found that I can sort of add extra conditions to flows to use a segment + extra filters, but it isn’t as reusable as I’d like. The real pain is for the one off, it looks like I need to select only a selection of segments & lists. My clones will become messing and misleading. (Certainly not anything we can’t handle, but nested segments seem like a simple and powerful way to manage things)

Our vip definition is rolling. But there are other examples like:

  • A segment of people that are part of the “Valentines Day Shopper” (rolling) segment, AND are part of the “In-Store Shopper” (permanent) segment.
  • We might have a definition for a collection of products, but that product changes their brand and product names. From an email marketing perspective, they are the same. I now need to change each flow/segment to include both old and new collection definitions. If I had defined the collection in a reusable segment, I would only need to update it once.