Skip to main content

Managing segments

Edit, delete, and understand the cascade behaviour when changing existing segments.

Segments page with a row's overflow menu open showing Edit and Delete actions
Editing and deleting both happen from the row's overflow menu.

Editing

Click Edit on a segment row's action menu. The same modal you used to create it opens, pre-filled.

What you can change:

  • Name — free text. Reports automatically pick up the new name on next load.
  • Code — uppercase identifier. Stays unique within the organization; the form blocks the change if you try to set it to a code already in use.
  • Colour — affects every existing place the segment is shown.
  • Icon — same.

Existing campaign-segment assignments are preserved across edits. Renaming a segment doesn't unlink it from campaigns.

Deleting

Click Delete on the row's action menu. Level prompts for confirmation.

What happens on delete:

  • The segment is removed from the segments list.
  • Campaigns previously tagged with this segment lose the tag. The campaigns themselves are unaffected — they keep all their data and any other segment tags they had.
  • In reports, campaigns left without any segment fall into the Unknown bucket; a Segments report loses the deleted segment's row.

There's no undo. If you delete by mistake, recreate the segment with the same code — campaigns whose names contain that code will be re-tagged automatically on the next sync; anything that was tagged by hand needs to be re-assigned manually.

Cascade reference

ActionAffects
Edit name / colour / iconDisplay only. All campaigns and reports update on next load.
Edit codeWhich campaigns get auto-assigned on future syncs, plus any external code references.
DeleteSegment + tag relations on campaigns; untagged campaigns fall into Unknown in reports.

Permissions

Editing segments requires the Manage Segments permission in the active organization. Deleting has its own permission — Delete Segments, a child of Manage Segments — so an admin can let someone maintain segments without letting them delete any. Without these permissions, the row's action menu is hidden — read-only viewers see the list but can't change anything.