Back to the Knowledge Base

Knowledge Base Article

What happens if a merge tag cannot find data for a recipient?

If a merge tag cannot find the corresponding data for a particular recipient, the tag is replaced with an empty string (blank). No brackets, placeholder text, or error messages will appear in the sent email. To use words of your own instead, add a bar and fallback text inside the tag: [MailingCity|your area] reads your area for anyone with no city on file.

[FirstName] works a little differently. Argenta uses the recipient's nickname when there is no first name. With neither, a greeting that opens a line, such as Hi [FirstName],, is left out of that recipient's email, so it never reads Hi ,. Anywhere else in a sentence [FirstName] comes out blank like any other tag. To greet them with a word of your own, write [FirstName|Friend], which reads Hi Friend,.

Common scenarios where a tag resolves to blank:

  • [TotalDonated] - The recipient has never made a donation
  • [MembershipLevel] - The recipient is not a member
  • [RenewalDate] - The recipient has no active membership
  • [Nickname] - No nickname has been entered on their constituent record
  • [MailingAddress] - No mailing address on file
  • [Phone] - No phone number on file

The Insert Merge Tag picker showing available tags

Every tag in the picker resolves to a blank when the recipient has no data for it. [FirstName] tries the nickname first.

Best practices for handling missing data:

  • Write your email so it still reads naturally if a tag is blank. "Dear [FirstName]," at the start of a line already handles this for you: with no name, the greeting is left out. It is the other tags that need the care.
  • Avoid sentences that depend entirely on a tag being present, such as "Your total giving of [TotalDonated] has made a difference" unless you know the recipients are donors.
  • For donation or membership tags, only use those tags in emails being sent to lists that you know contain donors or members.
  • Use the [OrganizationName] tag freely since it always has a value from your account settings.
Reconnecting…

Whoops!

You've Encountered An Error

Something went wrong on our end. Don't worry, our development team has already been notified, and we'll get it fixed as soon as we can.

Please avoid repeating the same action for now. A quick reload usually gets you going again.