Shared email addresses and personalized greetings

For school administrators using GiveCampus Outreach. Controls can differ between the classic email editor and the newer Composer editor.

The audience builder groups results by normalized email address. Several qualifying constituent records can therefore become one email recipient with several associated records. This does not prove that a source segment contains only one constituent or that the intended household member will supply every merge field.

Merge fields use their own record priorities and choose the first generated value. For the Preferred First Name token, CRM preferred/first-name data takes priority over direct recipient-upload and segment-member names. Within a record priority, linked constituent records are ordered deterministically, but not by constituent creation date; changing the backing records can change the selected person, and a blank value can fall through to another record.

Review the affected recipient's merged values and intended greeting before sending to shared addresses. You should not expect that the first row in an uploaded file, the person matching one particular segment clause, or the oldest spouse always wins. Confirm the exact token: Informal Name and Preferred First Name need not be the same field.