Allow multi-selecting segments in Matrix editor interface | Squiz DXP

Allow multi-selecting segments in Matrix editor interface

Alexander Heyes

We have implemented multiple segments, and we want components to show if users are in multiple segments at once. Currently, the editor interface only allows selecting a single segment at a time, which means we can't preview components that require multiple segments.

February 13, 2026

Cam Ross

Hi Alexander,
I think I better understand your request now - you have different components personalised based on different segments, and just want to have a way to see them all on one page, is that right? 
If that is indeed the case, then we actually do already have this feature. When you're in page builder, switch the toggle in the top left from "build mode" to "preview mode" - on that version of page builder, you can select multiple segments to apply at once and see all personalised content on the one page.
Does that help?
Thanks
Cam

Alexander Heyes

Cam Ross That is exactly what we were looking for, thank you! We'll definitely use that going forwards.

Sorry we didn't find it ourselves, we tend to use the visual page builder preview and preview in a new window, but not the preview in Matrix. Would you consider adding the segment multi-select to those two previews as well?

Cam Ross

Hi Alexander,
Our personalisation system is designed to apply only one personalised version of a block at a time, and we support some complex rules to enable you to prioritise which segments take precedence over others. 
If you have a use case that requires you to have a default version of a component, and a version for segment A, and a 3rd version for segment B, and a 4th version for segments A & B combined, then our recommended approach would be to add a single segment that represents the intersection between A & B.  
Thanks!
Cam

Alexander Heyes

Kia ora Cam Ross , the way we are using segments doesn't match what you have described. We have one segment for all logged in users, and then additional segments for specific attributes like campus and academic division. If we have to create segments and components for every combination, it will quickly become exponential and unmanageable.

For example, we have a page with a logged in dashboard view, and then specific components for each campus on that logged in view. We don't want to create a segment for 'logged in + Wellington capmus', we'd rather have students in both the logged in segment and the Wellington segment.