In email campaigns that are using personalization merge tags (such as first name, last name, company etc…), blanks will populate if the data is missing. You can use fallback text for personalized merge tags so that the merge tag still populates some text even when the guest personal information is missing.
Understanding the health of your database allows better segmentation and more effective email campaigns, but if you don’t have the data in your database as a result of incomplete front desk data collection or minimal contact list fields. You can use fallback text for personalized merge tags, so your merge tags generate some content even if the guest profile doesn’t have the data.
This is available for:
- GUEST FIRST NAME
- GUEST LAST NAME
- GUEST FULL NAME
- GUEST TITLE
You will see that merge tags to be added will populate as [GUEST FIRST NAME, fallback=] for example. After the = sign, you can write in what you would like to appear as an alternative to the guest personal information.
Dear [GUEST FIRST NAME, fallback=Valued Guest]!
If the guest profile has a first name, then their first name will populate. If the guest name is ‘John’ it will say “Dear John” in the email to the guest. If the profile does not have a first name, it will say “Dear Valued Guest”.