Use merge tokens and personalized content safely

Tags: product:outreach intent:merge-token intent:personalization intent:fallback

Insert personalization from the editor's merge-tag menu rather than typing token syntax from memory. Available tokens depend on the outreach type and data available to the institution. Use a fallback for optional values such as preferred name, class year, or other constituent attributes so missing data does not produce a broken salutation or blank sentence.

Before sending, use the draft preview and Send Test Email. A test sent to an administrator may not contain the same constituent data as production, so also review merge-token substitution status or recipient preview when that feature is displayed. Confirm that personalized links use the intended constituent/appeal workflow and do not expose sensitive fields in visible URLs.

If a token is not in the editor's menu, do not invent it. Add or import the required data first, use a supported custom field/segment attribute, or rewrite the message without the token.