A wrong name in a Gmail mail-merge message usually requires checking the recipient source and field mapping, not simply rewriting the greeting. Stop the campaign while investigating so that a data problem does not reach more people.
Identify where the field comes from
For recipients added directly to the To line, inspect Google Contacts and the name entered with the address. Gmail can use that information to populate name tags. A short display name may not provide an unambiguous first and last name.
For a linked Google Sheet, confirm that recipient information is on the first tab and that the selected email and name columns are the intended ones. Compare one entire row, not just a name column viewed separately from its address.
Check headers, missing values, and shifted rows
Inspect column headers and the tags actually offered in the compose window. Special characters in a header can affect how Gmail names its tag. Correct a misleading header in a controlled copy rather than assuming a similarly named tag refers to the right field.
Review blank cells and any sorting or pasting that may have separated names from addresses. When a required merge field is missing, use an appropriate default only if a generic greeting is acceptable. Do not invent a person’s name to suppress an error.
Verify the correction with different test rows
Use controlled recipients representing a normal complete row, a missing optional field, and any unusual data format. Inspect received copies to confirm the name and associated details stay together. A preview of one row cannot establish that all mappings are correct.
If hidden spreadsheet formatting causes a read error, Google’s guide suggests a new Sheet containing values-only copies. Preserve the original and recheck every mapped column afterward. If incorrect messages were already sent, reconcile the actual sent recipients before deciding on a narrowly targeted correction; resending the whole list can create another error.
Browse Gmail & Google Account help
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.