docs: Document Preference Center Segment ordering by Public name#851
Open
promptless-for-oss wants to merge 2 commits into
Open
Conversation
Segments in the Preference Center are now ordered alphabetically by Public name (with a stable secondary sort by ID), per mautic/mautic PR #15850. Document the ordering so admins know Public name controls how Segments appear to Contacts.
|
|
||
| Use the Segments tab to add or remove a Contact from a Segment. Segments are a source for both starting Campaigns and sending Emails. Any Contact in a particular Segment is automatically part of a Campaign that has that Segment as the source. You can also use a standalone Email to manually send an Email to a Segment. If a User has opted out of a Segment they no longer receive Campaign actions or messages sent to that Segment. | ||
|
|
||
| Segments appear in the Preference Center in alphabetical order by Public name. If two Segments share the same Public name, Mautic orders them by their internal ID. Since Contacts see this order, set a clear Public name on each Segment to control how it appears. |
Contributor
Author
There was a problem hiding this comment.
Documents the ordering introduced by this PR: LeadListRepository::getPreferenceCenterList() changed its query from orderBy('l.name') to orderBy('l.publicName') plus addOrderBy('l.id', 'ASC'), so Preference Center Segments now sort alphabetically by Public name with a stable secondary sort by internal ID.
Source: mautic/mautic#15850
adiati98
reviewed
Jul 21, 2026
|
|
||
| Use the Segments tab to add or remove a Contact from a Segment. Segments are a source for both starting Campaigns and sending Emails. Any Contact in a particular Segment is automatically part of a Campaign that has that Segment as the source. You can also use a standalone Email to manually send an Email to a Segment. If a User has opted out of a Segment they no longer receive Campaign actions or messages sent to that Segment. | ||
|
|
||
| Segments appear in the Preference Center in alphabetical order by Public name. If two Segments share the same Public name, Mautic orders them by their internal ID. Since Contacts see this order, set a clear Public name on each Segment to control how it appears. |
Contributor
There was a problem hiding this comment.
@promptless-for-oss please address the suggestions.
Suggested change
| Segments appear in the Preference Center in alphabetical order by Public name. If two Segments share the same Public name, Mautic orders them by their internal ID. Since Contacts see this order, set a clear Public name on each Segment to control how it appears. | |
| Segments appear in the Preference Center in alphabetical order by **Public name**. If two Segments share the same **Public name**, Mautic orders them by their internal ID. Since Contacts see this order, set a clear **Public name** on each Segment to control how it appears. |
Applies maintainer @adiati98's review suggestion to emphasize the 'Public name' field references in the Preference Center Segment ordering note.
Contributor
Author
|
Thanks @adiati98 — done. We've applied your suggested edit: the three Public name references in the Segment-ordering note are now bolded, with the wording otherwise unchanged. Committed and pushed to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Open this suggestion in Promptless to view citations and reasoning process
Adds a note to the Contact Segments section of the Preference Center docs explaining that Segments appear alphabetically by Public name, with a stable secondary sort by internal ID, per mautic/mautic PR #15850. Clarifies that setting a clear Public name controls how Segments appear to Contacts.
Trigger Events
Tip: Tag @Promptless in GitHub PR comments to guide documentation changes during code review 🐙