Yes, I understand how the functionality currently works; that was the reason for submitting the feature request. ... View more

We would like to create a segment of contacts that do not have the first or last name fields populated. The segments have a lot of filtering options, but for some odd reason the name fields aren't accessible.   Some use cases for this: 1) Send an email to contacts without name fields with an option to update their profile. 2) Separate a campaign to send a different greeting to those without a first name field. I realize we can add some text to use if a merge field is blank, but we can't fall back to another field or change it completely. If the first name field is blank we may want to use a preferred name field or customize the greeting and email 3) Data management. Since our contacts often exist in other systems, a segment of those with blank name fields can be used to pull in information from outside sources. ... View more

As we approach the 4 year anniversary of this feature request, would you please explain the justification for ignoring it? You can view/edit a contact from everywhere except the segments, so what is technically different about a segment that makes this implementation difficult? It seems like a very simple fix to add the view & edit options to the ... menu that's already there, and the functionality to view & edit is already there as well, so what's the issue? The dynamic nature of segments makes them a great tool for data validation, but that means editing them as they show up is important. For example, since we send campaigns based on a combination of tags and lists, we have a segment to check for contacts without the correct tags so we can update them. Your solution to this suggests that I create a new "Contacts to Edit" list, add them to that, export the list, edit it in Excel, import the changes, and then remove them from the list. That's hardly a reasonable solution, is it?  ... View more

We have a similar need, but focused on the preferred greeting of an individual. Some of our user base from non-US cultures have names that are either tough to pronounce or long, and some of these people have chosen simplified versions. Plus those with names like Jennifer who commonly go by Jenn. This means that we need the Greeting to allow the use of the preferred greeting field, but also use the standard contact fields as the first level fallback.   So if a Preferred Greeting exist, use that. If that field is blank then use the First Name (for example), and if that is also blank use the generic fallback text. This is the only way that we can make our communication feel personal to all of our user base without impacting the data integrity. ... View more