Birthday Email for Nonprofit Brands That Leads With Impact

The nonprofit birthday has two flavors and they are not the same job. The donor birthday thanks the person who gives and protects renewal. The beneficiary birthday thanks the giver by showing them the specific person their money supports. The second one converts better, because the donor already has a relationship with one named beneficiary.

Most sponsorship and cause nonprofits keep a beneficiary birthday on the constituent record. Child sponsorship, animal rescue, scholarship funds, mentorship programs all fit. If your client has that field, this is the email to automate. If they do not, start with the donor birthday and use the year-in-review angle instead.

Trigger. Fire on the beneficiary's birthday date property, day-of, at 6am local. Klaviyo stores this as a date property on the sponsor's profile, for example child_birthday. Mailchimp stores it on a birthday merge field in the sponsored-member audience. Day-of beats the day before, because a "tomorrow is her birthday" message reads like marketing and a "today is her birthday" message reads like news.

Offer and CTA. Lead with a low-friction action, then make the donate ask optional. The strongest call to action on a beneficiary birthday is not "Donate." It is "Send Amara a birthday note." That note form captures engagement, and the donate option sits beside it as a $15 birthday gift tied to a concrete unit: a book for her classroom, a bag of feed, one vet visit. Concrete units beat dollar amounts in fundraising copy every time I have tested them.

Copy angle. Name the beneficiary by first name. Give the age. State one specific detail from the year, what she wants to be, her favorite subject, the name of the dog she walks. Then deliver this year's impact in real units, not adjectives. "22 books, three health checkups, a seat in the reading club" outperforms "your generosity made a lasting difference." Close with the optional ask and get out.

Numbers to expect. Triggered birthday emails to warm constituents open in the high 40s to low 50s percent, and donation conversion on the soft gift commonly runs 2 to 4 percent. The bigger win is retention. A constituent who gives a second time within 90 days of their first gift retains at roughly 60 percent over the next year, against roughly 20 percent for one-time donors who never get that second touch. This email is one of the cheapest second touches you can automate.

The HTML under this email is table-based, not flex-based, because Gmail, Outlook, and Yahoo all still strip flexbox and float tables happily. Every layout container is a nested table, every cell is a td, and the width lives on the table, not in a style block. That is the only layout method that survives every inbox unchanged.

Every element carries inline CSS. Webmail clients like Gmail, Yahoo, and Outlook on the web keep inline styles and drop style blocks partially or fully, so anything that must render, renders inline. The head styles exist for the one or two clients that still read them.

The button is a bulletproof VML button, not an image. Outlook on Windows renders mail through Word's engine, which ignores border-radius, drops CSS backgrounds, and turns a styled link into a flat gray rectangle. The VML roundrect fallback draws a real rounded button with the correct background color in Outlook 2016 through 365, and the standard anchor tag shows through in every other client. No image means no broken-image icon when the donor is offline.

Impact numbers and the beneficiary's name are live text. Baking "Amara turns 9" into a hero image is the most common mistake I see in nonprofit creative. Apple Mail dark mode and Gmail image caching recolor or dim it, and screen readers skip it entirely. Live text scales, inverts cleanly in dark mode, and is readable to a donor using VoiceOver.

Dark mode is handled with a color-scheme meta tag in the head, plus a supported background style on the cream section. Apple Mail and Outlook dark mode respect the color-scheme hint and stop inverting the warm background to pure black, so the design holds its tone instead of going harsh.

There is one mobile media query, scoped to max-width 600px. It collapses the single column, grows the button tap target to a real thumb size, and sets body text to 16px so iOS Mail does not trigger its small-text auto-zoom. One query is enough. Two dozen is where bugs enter.

Web fonts declare a fallback stack. The headline loads a web font if the client allows it, then falls back to Georgia and the system serif. Gmail strips link tags entirely and Apple Mail blocks remote fonts until the recipient loads them, so the fallback has to be a font you have already designed around, not an afterthought.

Copy the HTML from the export. In Klaviyo, open a new email and choose the HTML email type, or drag a raw HTML block into a drag-and-drop email where you need it. Paste the code into the source view. In Mailchimp, start a campaign, pick Email, choose Code your own, then Paste in code, and drop the full document in.

Swap four things before you send. The nonprofit name in the header and footer. The logo URL and the donation landing-page link. The three hex values that drive the design, the deep rust header, the burnt orange button, the cream body. And the beneficiary details in the body copy.

Wire the merge tags. These tokens turn a static template into a personal email.

In Klaviyo, the donor greeting is {{ first_name|default:'Friend' }}. The beneficiary name and age come off custom profile properties you sync from the CRM, for example {{ person|lookup:'child_name' }} and {{ person|lookup:'child_age' }}. Pass this year's impact as its own fields so the copy stays clean: {{ person|lookup:'impact_books' }} books, {{ person|lookup:'impact_checkups' }} health checkups. The donation link should carry the donor ID so the gift attributes correctly: https://give.example.org/birthday?donor_id={{ person|lookup:'donor_id' }}.

In Mailchimp, the same fields are merge tags: *|FNAME|* for the donor, *|CHILD_NAME|* for the beneficiary, *|CHILD_AGE|*, and *|IMPACT_BOOKS|*. The donation link uses *|DONOR_ID|*. If a record is missing the beneficiary field, set a default inside the tag, *|CHILD_NAME:Friend|*, so the email never reads "Today is 's birthday."

Set the trigger. In Klaviyo, build a Flow triggered by the date property child_birthday equals today, scheduled for 6am in the constituent's timezone. In Mailchimp, start a date-based automation on the birthday merge field with the same send-time rule.

Test before it goes live. Send a preview to Gmail on web and iOS, to Apple Mail on desktop, and to Outlook on Windows. Then toggle dark mode on an iPhone and confirm the cream background holds and the live text inverts cleanly. Fix any of those four before you schedule, not after.