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

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.
The code drives automatic assignment: during each sync, campaigns whose names contain the code get the segment automatically. Change the code and campaigns matching the old token stop being picked up — only names containing the new code will be tagged going forward (already-assigned campaigns keep their tags). If anything outside Level references the code too, that breaks as well. Decide on the code at creation time and avoid changing it.
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
| Action | Affects |
|---|---|
| Edit name / colour / icon | Display only. All campaigns and reports update on next load. |
| Edit code | Which campaigns get auto-assigned on future syncs, plus any external code references. |
| Delete | Segment + 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.