Current segment selector

Created on 13 August 2025, 2 months ago

Overview

Current segment selector.

We need a current segment selector, by default will be the "Default" segment.

Proposed resolution

  • We need a current segment selector (visible only based on feature flag)
  • This segment selector should show existing segments sorted by weight.
  • This segment selector should set the "active segment" on the redux store, so we can e.g. flag when the "personalize" button will show/which personalization case needs to be render on the preview + layer panel.

User interface changes

A beautiful selector is on the top for selecting the active segment in the editor.

📌 Task
Status

Active

Version

1.0

Component

Personalization

Created by

🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @penyaskito
  • 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
  • First commit to issue fork.
  • Merge request !1479Migrate SegmentSelector from POC → (Open) created by Unnamed author
  • 🇨🇦Canada mred9

    The SegmentSelector component has been introduced into the TopBar. Unlike the SegmentList on the dashboard, which lists segments by weight, the SegmentSelector places the default first and then sorts alphabetically for easy discovery. It intentionally includes disabled segments, allowing you to modify and preview before turning them on.

  • Pipeline finished with Failed
    about 2 months ago
    Total: 625s
    #583112
  • 🇨🇦Canada mred9

    Notice the requirements explicitly asked to sort segments by weight, so that has been updated. The Default segment now appears last.

  • Pipeline finished with Failed
    about 2 months ago
    Total: 886s
    #583123
  • 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

    Notice the requirements explicitly asked to sort segments by weight, so that has been updated.

    I don't think I verified this with the designs when I wrote that. Having Default followed by alphabetic/weight sorting makes sense to me for that selector.

    I just checked Figma and it shows Default first. It's not explicit how the others are sorted, but I'm wondering we should show Default first, and then sorted by weight.

Production build 0.71.5 2024