An event invitation goes out to 4,000 members with “Dear ,” in the greeting and a link pointing to last year’s gala. Nobody caught it because the only way anyone saw the email before it went out was a quick look at the template in the editor, and the editor doesn’t show what a real constituent’s merge fields will produce.
Previewing an Altru email properly means answering three different questions, and each one needs its own check: Does the content look right? Does it merge correctly for real people? Does it render properly in the inboxes your audience actually uses? Below is how to cover all three with what Altru gives you, plus a few habits that make the check fast enough that people actually do it.
Know what your version of Altru shows you
Altru’s email tools let you build templates with merge fields and send them to a selection of constituents pulled from a query. What the on-screen preview shows, and whether it can render a specific constituent’s merged values, may depend on your release and on which email feature you’re using (a marketing email versus an automated acknowledgment or eTicket, for example). Rather than relying on memory or a forum post, open the template you plan to send and check for yourself:
- Does the preview show merge fields as placeholders, or as real values from a record?
- Can you choose which record the preview uses?
- Can you send a test to an address without sending to the whole selection?
If you can’t tell, ask Blackbaud support what your current release supports. The rest of this guide works whatever the answer turns out to be.
Build a seed list once, use it for every send
The most dependable way to preview a real merged email is to send it to people who aren’t your audience. Set up a small group of test constituent records that belong to staff, each with a staff inbox as the primary email:
- A current individual member with a full name and salutation filled in
- A household membership, so you can see how household names merge
- A lapsed member
- A record with a blank first name or salutation, which is the one that catches “Dear ,” before your audience does
- A record with a long name, an apostrophe, or an accented character
- A donor-only record with no membership, if the email references membership details
Next, make a query that returns only these records, and give it an obvious name like “SEED – email tests.” Before any real send, point the same email at this query first. Because the test runs through the same merge process as the live send, what lands in those inboxes is what members will see.
Keep the seed records clearly labeled (a constituent attribute or a note works) and leave them out of reporting, counts, and appeal results. Make sure they can’t end up in a real mailing by accident, either by excluding them in your standard queries or by checking that they’re filtered out.
Check that the real selection merges cleanly
The seed list proves the template works. It doesn’t prove your actual audience’s data is clean. Before sending, run the real selection query and look for the fields your email depends on:
- Add the merge-field columns (first name, salutation, membership level, expiration date, event name) to the query output.
- Sort each column so blanks rise to the top.
- Decide what happens to those records: fix the data, add a fallback in the template if your version supports one, or exclude them and contact them separately.
While you’re in there, check for duplicate email addresses. Duplicate constituents sharing one inbox can mean the same person receives an invitation two or three times, which is more noticeable to recipients than a typo.
Look at it where people will read it
Even a good on-screen preview only shows you one rendering. Your members are reading on phones, in Gmail, in Outlook, and sometimes with images turned off. When a seed email arrives:
- Open it on a phone and on a desktop client. Outlook on Windows is often the least forgiving.
- Turn off images once. If the event date or the call to action only appears inside an image, it disappears.
- Click every link, especially registration, ticket, and calendar links. Copied templates are a common way old URLs sneak through.
- Read the subject line and preview text the way they appear in the inbox list, not just in the editor.
Make one person the second set of eyes
A simple rule works well: whoever builds the email doesn’t approve it. The approver gets the seed send, replies “approved” (or doesn’t), and only then does the live send go out. For invitations and appeals, add a final glance at the selection count. If you expected around 4,000 recipients and the query returns 11,000, stop and work out why before you send.
Quick answers
Can I just send the email to myself?
You can, but if your own record has a clean name and an active membership, you’ll only see the best case. A seed list with deliberately messy records shows you the failures.
Do I need a sandbox for this?
Not for previews. Seed records in production are fine as long as they’re labeled and kept out of reporting. A sandbox is more useful when you’re testing a new template structure or merge logic you haven’t used before.
Where Social Good fits
Everything above can be done with Altru, a handful of test records, and some discipline. For recurring messages like eTickets, acknowledgments, renewal reminders, and post-visit emails, Email Designer sends automated, branded emails from Altru queries without manual exports. The seed-query habit still applies: run any new automated email against your staff test records first.
