From Borrowed Reputation
to Built Infrastructure

How Email Measurement Changed — and What It Revealed

Between 2021 and 2025, the tools that email programs had relied on as primary indicators of audience health shifted significantly across the entire industry. The changes weren’t unique to OBUSA — they affected every nonprofit sender — but understanding them is what made it possible to read our audience clearly and make the right infrastructure decisions in response. That’s where this account starts.

Apple Mail Privacy Protection and the Open Rate Fiction

In September 2021, Apple introduced Mail Privacy Protection (MPP), which pre-loads email content — including tracking pixels — on Apple devices regardless of whether a human actually opened the message. The immediate effect was artificial inflation of open rates across the entire email industry. By 2023, any ESP reporting open rates above roughly 25% was almost certainly capturing a significant share of machine-triggered opens alongside genuine human ones.

OBUSA’s Mailchimp dashboard showed a ~32% average open rate in 2023. On its surface, this looked like a reasonably healthy program. Under the hood, a substantial portion of those opens were Apple Mail proxies, not humans. The 2023 Advancement Communications Report captured this distorted reality: a 32% open rate sitting alongside a 0.35% click rate, against a nonprofit benchmark of 2.79%. Those two numbers cannot coexist in a healthy program. Open rate was a fiction; click rate was the honest signal, and it was pointing at a serious problem.

Bot Traffic: Quantified

Mailchimp’s AI-powered bot/proxy analysis of the last 50 sends (Nov 2025–May 2026) made the scale of the problem concrete. Across the 21 Development-tagged campaigns in that window:

Source: Mailchimp AI bot/proxy export, Nov 2025–May 2026. Mailchimp’s standard dashboard rates already exclude bot traffic before calculating percentages — these figures quantify the noise underneath reported metrics, not an adjustment to them.

Alumni sends were especially saturated — one Alumni Summit Fund Appeal showed 80% bot opens and 82% bot clicks, reflecting a high concentration of corporate email addresses and security-scanning infrastructure in that segment. The contrast with SYBUNT sends (lapsed donors), which were nearly bot-free, is significant and directly informs future segmentation strategy.

What the Data Revealed About Our Audiences

The most useful thing the Mailchimp-era data did for this program was not confirm performance — it revealed audience structure. Looking across the contact universe with better analytical tools, a clearer picture emerged of where genuine engagement was concentrated, which segments were already demonstrating donor-ready behavior, and what kind of communication those segments actually responded to. That understanding directly informed the migration to Braze and continues to shape the audience and content strategy being built today.

The Audience Funnel: 125K to ~13K

Mailchimp engagement export, 2025–26 review. “Truly engaged” = opened any campaign in last 20 sends.

The Donor Picture Was Even Starker

The 2023 Advancement Communications Report captured the donor segment specifically. Of 7,876 subscribed donor contacts in Mailchimp at that time, approximately 98% were classified as rarely engaging — leaving roughly 158 consistently active donor contacts in the entire email program. Mass-blast communications to 80,000+ contacts were reaching a donor audience that was functionally dormant for the overwhelming majority of recipients.

Borrowed Infrastructure, Borrowed Results

OBUSA’s Mailchimp sends ran through a shared IP pool serving millions of other senders. This has a real benefit for new or casual senders: the pool carries established reputation with ISPs, providing inbox placement the sender hasn’t independently earned. OBUSA was borrowing goodwill it had not built — and as noted above, that structural arrangement also limited the ability to improve inbox placement through better sending practices. The simplicity that School-level staff experienced in Mailchimp came at the cost of visibility and ownership. There was nothing to carry that reputation forward when platforms changed.

OBSG: A Parallel Story, Now a Unified Asset

Outward Bound Services Group (OBSG) was, prior to January 2025, a separate OBUSA business unit focused exclusively on selling Open Enrollment (OE) courses. It maintained its own Mailchimp list — the OE List — entirely separate from OBUSA’s Development audience, with no shared visibility into contact overlap, engagement history, or cross-audience relationships.

OBSG’s OE List tells a near-identical engagement story. In 2024, across 64 campaigns and 53,514 total contacts, the list was performing well: 63.4% of contacts were engaged (33,933 contacts), average open rate of 14.2%, with peak open rates of 20–32% in Q2 2024. Then, beginning in Q4 2024, the same decline visible in OBUSA’s data appeared: December 2024 sends dropped to 4.9–5.8% open rates. By January 2025–February 2026 (the last 50 OE List campaigns — every one of them labeled “IP Warming”), 72% of contacts were completely dormant and only 1,113 remained highly engaged — a 78% drop from the 5,239 who were highly engaged just the year before.

The timing is not coincidental. The transition dynamics and shared IP warming challenges affecting OBUSA’s program during 2025 were operating across both programs simultaneously. They were separate accounts, separate lists, separate audiences — but the same underlying deliverability environment. When OBSG was formally integrated into OBUSA in January 2025, the most engaged OE List contacts began migrating to Braze. Today, 9,261 OBSG contacts are reachable in the OBSG Braze team, alongside OBUSA’s 11,700. Accounting for the 3,114 contacts who appear across both audiences, the total combined, deduplicated reachable Braze audience is 17,847 — already exceeding what OBUSA’s Mailchimp-era peak showed when viewed as a single list, and representing something genuinely new: a unified picture of two previously invisible-to-each-other audiences.

The Hitch: Evidence for Segmented Sending

The Hitch — OBUSA’s targeted development newsletter — provides a concrete case study in how a smaller, more curated audience performs against the mass-send baseline. Across 9 targeted sends from April 2025 through March 2026, The Hitch reached an audience that grew from ~4,437 to ~6,297 contacts — a 42% list growth over the period, reflecting genuine interest in this content format.

The reported open rates (5.2–8.4%) reflect the same industry-wide bot inflation. Between 63–75% of total opens across Hitch sends were bot/proxy generated, putting true human open rates at approximately 1.5–2.5% per send. Where The Hitch shows its value more clearly is on clicks. In sends unaffected by anomalous link-triggered bot scanning, human CTR ranged from 0.3% to 0.7% — consistently above the 0.10% baseline for typical mass sends. The two outlier campaigns (“Grateful for You” at 79% bot clicks and “The Hitch (3)” at 81%) likely reflect specific link structures that triggered aggressive security scanning rather than a problem with the audience.

The Hitch isn’t evidence of a problem — it’s early evidence of the model. A small, curated audience receiving content designed for them outperforms mass sends on click efficiency, even at a fraction of the volume. This is the same principle that makes SYBUNT so compelling at scale.

The Deeper Signal: Relevance Outperforms Volume

The most significant performance data point from the entire Mailchimp era is not found in the newsletter or mass-send numbers. Three SYBUNT (Gave Some Year But Unfortunately Not This Year) sends in 2025, reaching 1,167 total contacts, produced a 2.31% donation link CTR — approximately 24x the typical mass-send rate of 0.10%. The SYBUNT audience was small, precisely defined, and nearly bot-free. This is the model: highly segmented, smaller sends to audiences that share meaningful customer attributes — in this case, prior giving history and recency — consistently outperform larger, less tailored communications. The principle holds whether the segment is defined by giving history, course enrollment timing, program type, school affiliation, or geographic connection.

The Case for Braze: What the Migration Unlocked

The migration to Braze was a deliberate infrastructure upgrade, not primarily a response to a deliverability crisis. The deliverability challenges that followed were a known tradeoff of the transition — not evidence the move was wrong.

Why Dedicated IPs Change the Equation

Braze sends through two dedicated IP addresses assigned exclusively to OBUSA (137.22.238.90 and 137.22.248.236, via SparkPost as MTA sub-processor). Every send contributes to — and only to — OBUSA’s own sender reputation. There is no shared pool, no other senders’ behavior to absorb, no borrowed goodwill. The tradeoff is that dedicated IPs begin with zero established reputation: ISPs must observe sending volume, consistency, engagement rates, and complaint rates before assigning inbox placement. This warming period is standard for any move to dedicated infrastructure — not a platform flaw, not a migration error.

Almost No Automation: The Absence That Mattered

One of the starkest findings from the Mailchimp era is not just what the metrics showed, but what was entirely absent: nearly no automated communications, behavioral canvases, or structured stewardship sequences were deployed for donors or other audiences — even though Mailchimp offered this capability at a basic level. The program ran almost entirely on manually-scheduled campaign sends, with no triggered responses to donor behavior, no welcome sequences following a first gift, and no re-engagement automation for lapsed contacts. Every communication required an individual, manual decision to send. This left the entire relationship management burden on human bandwidth rather than on systems designed to carry it.

What Braze + Segment + Snowflake Makes Possible

Performance Evidence, Even Mid-Recovery

Despite sending during an IP warming period — with an intentionally restricted audience, fewer total sends, and active Gmail inbox placement challenges — Braze’s click-through performance is already substantially stronger than Mailchimp’s historical baseline:

12-month Development email lookback, equivalent time period. Note: this CTR advantage is below the nonprofit industry benchmark and should be read as directional progress during a recovery period, not a final performance ceiling.

The Gmail Split Test: Content Works — Reputation Is the Blocker

One of the most important diagnostics from the migration period is the Gmail-vs-non-Gmail split on the Spring Caregiver Appeal 2026. The same creative content, sent to two audience splits one day apart, produced dramatically different results — demonstrating clearly that this is a reputation and inbox placement problem, not a content quality problem. Non-Gmail contacts saw strong engagement; Gmail contacts, whose inbox placement was being filtered by reputation signals at the IP and domain level, received significantly less inbox delivery for that send. As Gmail reputation improves, the performance gap between the two populations will close, recovering reach to a significant portion of the donor audience currently unreachable.

Where We Stand Today (June 2026)

The recovery is measurably progressing. We are in a deliberate, temporary restriction period — limiting sends to engaged contacts only — to protect reputation and rebuild Gmail trust. The audience is temporarily smaller than its Mailchimp peak, but more productive per contact than it has ever been.

Naming the Unusual: An Atypically Long Warming Period

It is worth acknowledging directly that OBUSA’s IP warming process has extended nearly two years — well beyond the 4–12 week timeline typically documented for an organization at this scale. The duration reflects a combination of compounding factors: cold-starting two IPs simultaneously during the transition; a pre-existing list with a high concentration of disengaged contacts that limited positive engagement signals during the critical early warming period; and the Gmail-specific reputation challenges that emerged and required extended remediation. These are recoverable conditions, and the trajectory is clearly improving — c.outwardbound.org reaching High reputation, detailed below, is the proof. But the extended timeline underscores why the infrastructure changes being made now — clean subdomain, clear sender identity, engaged-only sending discipline — are not optional enhancements. They are the foundation that makes sustained improvement possible.

Did Sending Mailchimp and Braze Simultaneously Hurt Deliverability?

This is worth answering directly, since it’s a reasonable question and the honest answer has layers. During the migration window, Mailchimp continued sending to its remaining audience from its shared IP pool while Braze warmed dedicated IPs on c.outwardbound.org, with both programs reaching overlapping segments of OBUSA’s contact base at points in that period. Breaking down where that could and couldn’t have mattered:

• At the IP level: no impact, with confidence. Mailchimp’s shared pool reputation and Braze’s dedicated IP reputation are entirely separate infrastructure, tracked independently by every major inbox provider. Nothing that happened on Mailchimp’s shared IPs could technically transfer a reputation signal to Braze’s dedicated IPs, or vice versa. This part of the concern can be set aside.
• At the domain level: a real but secondary factor. Inbox providers evaluate reputation primarily at the IP level and at the exact signing domain (the domain in the DKIM signature and envelope-from address) — not broadly across an entire root domain. Because Braze sent from the distinct c. subdomain, the two programs were not sharing a reputation identity in the strictest technical sense. That said, both were operating under the same recognizable organizational identity to recipients, during the same window, to overlapping people — and Gmail and Microsoft increasingly weigh organization-level signals alongside strict domain-level ones as part of broader spam and trust modeling. This is very likely a real, if modest, contributing factor to the length of the warming period — not the primary driver.
• At the recipient level: the more plausible mechanism. The likelier source of friction wasn’t infrastructure — it was recipient confusion. A donor receiving similar-looking OBUSA content from two different systems in the same period may not have distinguished between them, engaging inconsistently or occasionally reporting one as spam without recognizing it as legitimate. That kind of noise can quietly dampen the clean, consistent engagement signal a new IP needs during its most sensitive early weeks.

Our stance, in short: running both systems concurrently was very likely a secondary, contributing source of friction — not the primary cause of the extended timeline. The primary drivers remain what they have consistently been in this document: cold-starting dedicated infrastructure from zero, and a legacy list with an unusually high concentration of disengaged contacts providing poor early signal. We don’t have a controlled comparison that isolates this variable precisely, so this is informed technical judgment rather than a proven causal claim — but it is our clear, considered position, and one more reason the completed migration and upcoming subdomain rename represent a cleaner foundation going forward.

IP Reputation Progress: High Achieved on Our Primary Sending Identity

c.outwardbound.org (137.22.238.90) has reached “High” domain and IP reputation with Google as of July 17, 2026 — the top tier of the recovery scale, and a genuine milestone for the program. This is worth sitting with: our primary sending identity has moved through all four stages of the recovery journey — Bad, Low, Medium, and now High — each held consistently for multiple weeks before advancing to the next. Google’s own reporting shows the spam complaint rate holding at 0% across every data point in this window, which is the underlying reason the reputation score was able to climb this cleanly.

Source: Google Postmaster Tools, domain and IP reputation reports for c.outwardbound.org / 137.22.238.90, June 20–July 20, 2026 data window. Google’s Postmaster Tools is being retired for new data after October 31, 2026; historical data will remain viewable until that date. The Bad/Low/Medium/High scale used throughout this document reflects Google’s own current labeling in this reporting view.

Why Some Gmail Contacts Receive Emails While Others Don’t

A common and understandable point of confusion: two contacts in the same “engaged” segment receive the same send, and one gets it in their inbox while the other does not — even though both use Gmail. This is not random, and it is not a system error. Gmail’s filtering algorithm evaluates reputation at the IP and domain level, but it also factors in recipient-specific engagement history. A contact who has previously opened OBUSA emails, moved messages from the spam folder to inbox, or replied within their Gmail account carries a positive individual-level signal that can override broader sender reputation concerns. A contact who has never actively engaged with OBUSA emails at Gmail — even if they qualify as “engaged” based on activity at other mailbox providers or on desktop clients — may consistently land in the spam folder regardless of sender reputation score. Two contacts in the same segment, receiving the same send, can experience materially different inbox placement based entirely on their own Gmail interaction history with OBUSA’s messages. As reputation improves overall, the proportion of Gmail contacts receiving inbox-placed messages grows — but individual-level history remains a factor that no sender can fully control.

Audience Size: Reading the Numbers Correctly

There are two important audience comparisons to hold simultaneously. The first is the Development/donor pipeline comparison: OBUSA’s Braze-engaged audience of ~11,700 (donors, donor prospects, and alumni) versus the Mailchimp “truly engaged” peak of 13,217 from the OBUSA-only list. That 11,700 is 88.5% of the Mailchimp peak — a temporary gap driven primarily by Gmail-blocked contacts excluded during recovery. This is the right comparison for Development’s donor work specifically.

The second is the full organizational picture: combining OBUSA’s 11,700 with OBSG’s 9,261 reachable Braze contacts (and deducting the 3,114 who appear in both), the total deduplicated reachable audience across both Braze teams is 17,847. This already exceeds what any single Mailchimp list ever showed for OBUSA alone — and it represents a unified, cross-organizational view that was structurally impossible when OBUSA and OBSG were on separate Mailchimp accounts. The November 2026 milestone targets OBUSA-specific engaged contacts exceeding 13,217 for EOY Development fundraising, while the combined total positions OBUSA for the largest coordinated reach in the program’s history.

The Volume Drop Was Intentional

Q1 2026 send volume dropped sharply from the November–December pace (Nov: 10 sends, Dec: 17 sends → Jan: 1, Feb: 4, Mar: 2). This is worth surfacing proactively before it appears in revenue or engagement reporting as an unexplained gap. It reflects deliberate deliverability-recovery operations — fewer sends to a deliberately restricted list is the correct behavior during reputation recovery, not a strategy failure or a technology problem. The EOY 2025 Development calendar ran on schedule through Braze. The Q1 pause was a controlled operational choice.

Infrastructure Roadmap: Domain Architecture

The current sending domain configuration is functional but not final. A sequenced series of changes will improve brand trust signals, create clean School-level differentiation, and establish an isolated sending environment for The Reset that protects OBUSA’s core deliverability as both programs scale.

Current State

IP Strategy: Two Dedicated Pools, One Clear Purpose Each

With c.outwardbound.org and IP 137.22.238.90 (“.90”) now at High reputation, the forward IP allocation plan is confirmed. Rather than introducing a third, freshly-provisioned IP for the subdomain rename, the plan reuses the existing secondary IP, 137.22.248.236 (“.236”), for the next stage of warming — and in doing so, sets up the long-term architecture for both the subdomain rename and the School rollout in one sequence:

• Now: .236 begins warming across both newly-renamed subdomains — mail.outwardbound.org and update.outwardbound.org — while .90’s hard-won High status on the current domain is left undisturbed. Decoupling the IP change from the domain rename reduces risk: we’re not asking a single IP to absorb both a new domain identity and new send volume at the same time.
• Then: as mail. and update. establish their own reputation on .236, OBUSA’s ongoing national sends consolidate onto .90 — the IP with the proven track record.
• From there: as School subdomains come online starting with the first migrated cohort, they are assigned to .236 as a dedicated School sending pool — separate from .90 entirely.

The end state: .90 carries all OBUSA national sends; .236 is the dedicated School pool. This is a deliberate structural choice, not just a policy commitment — it means School-level sending practices, whatever they turn out to be as nine independent Schools ramp up, cannot touch the reputation OBUSA has spent nearly two years building on .90. It directly resolves the shared-infrastructure risk raised below in School Subdomain Governance: the “small barrier” between OBUSA and School reputation is now a real IP-level boundary, not just a set of sending guidelines.

Step 1: Subdomain Rename — Trust Signal and Brand Clarity

The current prefixes c. (marketing sending) and t. (transactional sending) are functional but mechanical-looking. Recipients who inspect email headers see these low-legibility strings, which carry no brand meaning and can reduce trust signals — particularly for donor audiences. The planned rename introduces descriptive subdomain names that reflect purpose:

Step 2: Per-School Subdomains

Each regional Outward Bound School will eventually send from its own subdomain, creating clear differentiation between national OBUSA communications and School-specific messages. This serves both deliverability (School sends can warm independently without affecting OBUSA’s national sender identity) and subscriber trust (recipients can identify message origin at a glance).

Step 3: The Reset — Separated Domain Architecture

The Reset has a meaningfully different audience profile, content category, and subscriber relationship than core OBUSA Development communications. Its list is growing, its communications span transactional (confirmed pledge, day-of event reminder) and marketing (re-engagement, digital wellness content, partner co-promotion), and its subscribers may have no prior relationship with Outward Bound as an organization. The sending subdomain is confirmed: reset.outwardbound.org.

It’s worth being precise about what “separated” means here, since reset.outwardbound.org is a subdomain, not an unrelated domain. As established with the School subdomains in Step 2, subdomain reputation is tracked distinctly from the root domain and from sibling subdomains at most inbox providers — that’s the mechanism that makes reputation isolation work at all. What The Reset gains from this subdomain structure is the same kind of isolation Schools get: its own reputation history, its own complaint-rate profile, its own warming curve, independent of mail., update., or any School subdomain. What it does not get is total independence from the organization’s email presence — the shared outwardbound.org root, and increasingly the org-level trust signals some inbox providers weight alongside strict per-domain data (the same dynamic discussed in Section 04 regarding Mailchimp and Braze running concurrently), mean The Reset’s sending behavior isn’t entirely walled off from the rest of OBUSA’s email identity. It’s meaningfully insulated, not hermetically sealed. That distinction is why the goals below still hold, with one important caveat added:

The Rollout Timeline: July Through Year-End

Three tracks are moving at once, on different clocks, for good reason — running them in parallel rather than in sequence is what makes a September campaign launch and a November audience milestone both achievable without re-triggering the reputation risk this whole recovery has been protecting against.

The throughline across all three tracks: September’s fall campaigns and December’s EOY push both launch against a larger, more qualified audience than today’s — not against the full pre-migration list. That distinction matters enough to spell out plainly, and is covered in full in Section 06.

Getting Back to — and Past — 13,217 Engaged

The current engaged audience of ~11,700 is a temporary floor, not a ceiling. Improving Gmail inbox placement, recovering reach to currently-excluded contacts, and active list growth through enrollment, donation, and Reset conversion touchpoints will drive the audience back up — and past the Mailchimp peak by November 2026.

What Growth Means Here — and What It Doesn’t

This is worth stating plainly because the instinct heading into a major fundraising push is often to reach for the biggest possible list. Every figure already in this document points the other way. The effective engagement index in Section 04 shows the current, smaller Braze audience already generating roughly 3× more real donor action per send than the comparable Mailchimp-era cohort. SYBUNT converted at 24× the mass-send rate. The Hitch, at a fraction of the audience, consistently outperformed mass-send click rates. None of that is a coincidence of a smaller list — it’s what happens when a list is curated instead of just large. The inverse is equally true and worth saying directly: the 96,136 Mailchimp contacts with no measurable engagement (Section 02) are not a dormant asset waiting to be reactivated by volume. Mailing them at scale is what degraded deliverability the first time.

So the practical question for September and EOY campaign planning isn’t “how large can the list be” — it’s “which contacts have earned inclusion, and through which channel.” Three tiers cover the audience:

Maximizing reach heading into fall and EOY is exactly the right goal to hold onto here — the question worth sitting with together is what actually maximizes it. Every figure already in this document points to the same answer: a smaller, well-matched audience consistently outperforms a larger, undifferentiated one. SYBUNT converted at 24× the mass-send rate. The Hitch, sent to a fraction of the list, beat typical mass-send click rates. The current Braze audience already generates roughly 3× more real donor action per send than the comparable Mailchimp-era cohort. None of that is an argument for a smaller ambition — it’s the case for measuring success by qualified, engaged reach and revenue per send, rather than by total contacts mailed, as the fastest real path to the largest engaged donor pipeline OBUSA has ever had.

The recommendation for September and EOY planning follows directly: build the fall and EOY sends around the expanding, qualified audience the roadmap above is deliberately growing — recovered Gmail-blocked contacts, Tier 2 re-qualification through small-batch testing, and continued list growth through enrollment and donation touchpoints — rather than reaching for the full historical list as a way to hit a bigger number. The data suggests that path would work against the goal it’s trying to serve.

Why the Gap Will Close

The ~11% gap between today’s 11,700 and the Mailchimp peak of 13,217 is primarily driven by Gmail-blocked contacts who remain excluded from the engagement count while inbox placement continues improving, and by the conservatively-set engagement criteria appropriate for the recovery period. This next part is specific to OBUSA’s primary sending identity: with c.outwardbound.org and its .90 IP now at High reputation (Section 04), previously-excluded contacts reachable through that identity are beginning to re-enter the pool in staged increments and can start accumulating active Braze engagement history. That’s real progress, but it’s progress on one identity out of several. The same climb still has to happen on .236 and the newly-renamed subdomains, and separately, in parallel, on each School subdomain as it onboards (Section 05) — each starting its own reputation history from a colder point. The recovery snowballs forward one identity at a time rather than completing all at once, which is exactly what the roadmap in Section 05 is built to sequence responsibly. The controlled expansion approach — introducing contacts in monitored stages, checked for complaint rates and inbox placement at each threshold before opening further — provides a responsible mechanism for accelerating this without risking a reputation setback.

The Small-Batch Tool: Testing Before Trusting

With c.outwardbound.org now at High reputation (Section 04), the small-batch approach becomes a more useful and lower-risk tool than it was even a few weeks ago. The mechanics: for a specific segment of 200–300 contacts — internally agreed by Development to be likely-engaged donors or prospects, even if they haven’t yet met the formal engagement threshold — split the send into batches of roughly 50, spread across several days, carrying content built specifically for that audience. The Hitch is a natural fit for this: a curated, relevant newsletter to a hand-picked group is exactly the kind of send this tool is built for.

This is the practical mechanism behind Tier 2 above. Rather than a binary choice between “fully excluded” and “added back to the mass list,” the small-batch tool lets Development test a curated slice of the dormant list under controlled, monitored conditions — watching opens, clicks, and complaint behavior closely before deciding whether that segment graduates toward regular inclusion. It’s the same logic that made SYBUNT and The Hitch outperform mass sends, applied deliberately as a re-engagement testing tool rather than left as an occasional exception. Content must be unique and purpose-built for each tested group, not a smaller copy of a general appeal — that specificity is what makes the test meaningful and keeps risk genuinely contained.

Working with Massive Rocket on Segmentation Infrastructure

A parallel workstream with Megan is mapping additional segmentation attributes from Salesforce into Braze — aligned with the specific fields needed to build the audience segments that will power personalized Development communications. This includes both the technical field mapping and a documented SOP defining how new segmentation needs will be evaluated, requested, and implemented going forward. The goal is to ensure the team can build the segments it needs to drive audience relevance and donor trust without technical bottlenecks on each new campaign request.

The Content Consistency Baseline

A structural weakness in the Development email program surfaced clearly by the 12-month lookback data (covering 2024–2025 sends): stewardship-oriented sends represented approximately 4% of total Development email volume (or roughly 18% when the single annual Impact Report is included). The remaining 80%+ of what OBUSA donors received was an appeal, event announcement, or operational notice. This data comes from the 2024–2025 campaign history, not the 2023 audit — so it represents the most current content mix available and shows the pattern has held consistently across multiple years.

This figure reflects mass and lifecycle sends through Mailchimp and Braze specifically — it doesn’t include, and isn’t meant to discount, the one-to-one stewardship and moves-management outreach Development runs directly with individual donors and major gift prospects through Salesforce. That relationship-level work sits outside what either ESP can see, by design. What Braze can do is show whether that outside stewardship shows up in the signals we do track — a donor worked closely by a gift officer engaging more with email, visiting the site, or responding differently to a subsequent appeal. That cross-channel visibility, not a count of direct one-to-one sends, is the useful thing for us to watch here.

This matters for deliverability as well as relationship quality. ISPs reward consistent, expected communication cadences. A subscriber who receives mostly solicitations interspersed with long silences is more likely to stop opening, degrading the engagement signals that inbox algorithms use to route future messages. A regular stewardship cadence — even short, value-first touchpoints between appeals — improves the engagement baseline that makes appeal emails more likely to be delivered and read.

Content Strategy: Value First, Zero-Click Built In

The shift from treating opens and clicks as primary success metrics requires a parallel shift in how we create, deploy, and reuse content. The goal is not fewer sends — it is more relevant sends with more value delivered per message, in formats that generate genuine engagement signals even when no trackable click occurs.

Engagement Signals Beyond Email — Channels Available Now

One of the most important differences between the Mailchimp and Braze eras is not just how email performs, but how many ways engagement can now be tracked, attributed, and acted on. Because all channels flow through the same Braze profile, every interaction — regardless of channel — contributes to our understanding of when and how to reach a contact, and when re-engagement sequences should activate.

Zero-Click Content: What It Means and Why It Matters

Zero-click content delivers meaningful value within the email itself — no link required for the reader to receive what has been offered. Complete impact stories, data snapshots, student quotes, field updates, and program outcome summaries are self-contained. A reader can share, forward, screenshot, or recall the content later without ever clicking a link. The value is delivered on open, not conditional on action.

This matters for two interconnected reasons. First, a growing share of genuine engagement happens without trackable clicks: forwarding to a colleague, saving a screenshot, searching for an organization later after reading about it in an email. Zero-click content reaches people where they actually consume information. Second — and more mechanically important for deliverability — content people genuinely want to read produces lower complaint rates, higher read-time signals, and more consistent engagement, all of which inbox providers use to route future sends favorably. A zero-click email that no one clicks but many people read and keep is building sender reputation. A click-dependent email that generates mediocre engagement is not.

How Zero-Click Engagement Shows Up in Our Data

Setting benchmarks for zero-click content requires different metrics than click-dependent sends. For a purely value-delivery email — an impact story, a field dispatch, a donor thank-you — the appropriate measures are: human open rate (directional signal of subject line and sender trust quality), spam complaint rate (the single most important reputation signal), unsubscribe rate (audience relevance signal), and downstream behavior in the following 7–14 days (did contacts who received a stewardship email convert at higher rates on the next appeal?). A stewardship message generating a 3–4% human open rate, near-zero spam complaints, and measurably improved conversion on a subsequent appeal is performing well — even if its CTR is 0%. Learning to read that story in the data is part of the transition from a click-dependent program to a relationship-driven one.

Content Categories: Expanding the Mix

Zero-click value content for OBUSA’s Development program includes: short participant impact stories complete within the email body; program outcome and data snapshots; seasonal field updates from instructors; staff and crew profiles; partnership profiles and announcements from organizational relationships; CEO and leadership thought leadership pieces; data and impact storytelling delivered as visual graphics within the email; and “what your gift made possible” single-story formats. These send well, generate genuine engagement signal, and prime recipients for appeals — all without asking for anything. The newsletter format remains a valuable flagship vehicle for organizing this content, but it becomes one format among several rather than the sole vehicle carrying all messaging weight. Adding shorter, single-topic sends between newsletter issues flattens the spike-and-silence pattern in send volume that currently characterizes the Development calendar, and gives inbox providers the consistency signal they reward.

Content-Triggered Sending: From the Digest to the Moment

A structural shift worth making deliberately: right now, most standalone content — a new story, a new video, a piece of relevant news — gets saved up and folded into the next scheduled newsletter or digest. That means genuinely timely, donor-worthy content sits unused for days or weeks waiting for a batching cycle, and it means every newsletter has to carry the full weight of everything that happened since the last one. The alternative: treat each piece of qualifying content as its own sending opportunity the moment it’s ready, and separately surface the best of it in aggregate formats afterward. Specifically, any of the following should trigger consideration for an individual, timely send to a relevant donor segment — not just a line in next month’s newsletter:

• A new alumni, donor, or student story published to the website
• A new video published to OBUSA’s channels
• A relevant report or piece of nonprofit-sector news, framed with OBUSA’s specific take or connection to our mission
• Any other timely content that would otherwise be held back and saved for a digest-style email

This isn’t a call to send everything to everyone — it’s a call to treat good content as perishable and match it to a segment likely to care right when it’s fresh, rather than defaulting to a monthly batching cadence. A student story lands as its own short send to donors connected to that program or region. A new video goes to the segment most likely to watch it. The newsletter and other aggregate formats still have an important job afterward: rounding up the highest-performing individual sends from the period into a single, curated recap for people who want the fuller picture. The two formats reinforce each other — individual sends catch the moment; aggregate formats catch the people who missed it.

Segmentation: Moving Past the Blast

The clearest evidence that targeted sends outperform mass blasts is already in OBUSA’s own data. SYBUNT performed 24× better than a typical mass send. The Hitch newsletter, at ~4,300–6,300 contacts, consistently outperformed mass-send click rates. These wins have a common explanation: smaller, more curated audiences receiving content designed specifically for them. First-party attributes available today — School affiliation, giving history, program participation, geographic region, course year — can be used to assemble audiences that are more relevant per send. The discipline required is not technical; it is the willingness to send smaller, better-targeted lists rather than defaulting to the largest available audience.

Frequency and Relevance Scale Together

Industry research and the behavior of OBUSA’s own best-performing segments consistently support the same principle: frequency and relevance are not in tension — they are proportional. Google’s and Yahoo’s bulk sender guidelines make the underlying mechanism explicit: spam complaint rate, not send volume, is the dominant signal inbox providers use to gate placement. A high-frequency program that generates low complaint rates because recipients genuinely want the content will out-deliver a low-frequency program with mediocre engagement at the same volume. The content mix is the variable, not the frequency ceiling. Sending more relevant content more often is the path to better deliverability, not a risk to it.

Sector data reinforces why relevance matters so much: M+R’s 2026 Benchmarks found that advocacy email — typically more targeted and specific than mass fundraising appeals — generated a 2.3% click-through rate against fundraising email’s 0.59%, roughly 4× stronger. The gap isn’t about the ask; it’s about relevance and specificity. Content built for a defined audience consistently outperforms content built for everyone.

A Three-Layer Model for Donor Sending Cadence

Bringing the pieces above together into one coherent structure, rather than three disconnected ideas: a mature donor communication program runs on three layers simultaneously, each doing a different job.

None of the three layers is optional, and none can substitute for the others. Automated lifecycle sequences without fresh triggered content go stale. Triggered content without a newsletter rollup loses the people who prefer a single periodic summary. Appeals without the other two layers arrive as a stranger asking for money, rather than a known relationship asking for continued partnership.

Evergreen Content: Getting More Life from What Already Works

Not every stewardship touchpoint requires original content creation. Program outcome data from previous years, participant testimonials from past courses, handwritten student letters (unfiltered, scanned, delivered directly in the email body), instructor field dispatches from past seasons — all of these are high-value content pieces that can be assembled, refreshed with current context, and sent to audiences who haven’t encountered them before. A donor who first gave in 2022 hasn’t seen course outcome data from 2019; it may be exactly what builds their confidence in giving again now. The planned quote book — an anthology of participant reflections available as a light purchasable ask — adds another evergreen touchpoint: a featured quote can run in email with a gentle link to the book, generating both stewardship value and a low-friction giving opportunity for donors who want to engage without a full donation ask.

Braze’s Canvas architecture is well-suited to evergreen deployment: content pieces can be built into a Canvas library and delivered conditionally based on lifecycle stage. A new donor gets the Donor Welcome canvas with evergreen impact content. A lapsed donor gets a re-engagement canvas with different evergreen content framed around renewal. Create once; deliver contextually over time.

Building the Multi-Channel Foundation

Email is one channel in a broader communication ecosystem. Braze’s platform capabilities — and OBUSA’s growing first-party data infrastructure through Segment and Snowflake — create the conditions for a coordinated multi-channel approach that strengthens email engagement rather than competing with it.

Channels Available in Braze

The current Braze implementation is email-focused, but the platform natively supports SMS, RCS, in-app messaging, web push, and content cards — all within the same contact profile, the same Canvas logic, and the same measurement framework. A donor who doesn’t open an email acknowledgment after a major gift might respond to an SMS thank-you. A first-time applicant on the OBUSA website might engage with a personalized in-app prompt to complete their application. These are not separate platform implementations — they are Canvas steps that incorporate the appropriate channel at the right lifecycle moment, decided by contact behavior and preference data already in the system.

Paid Media as an Engagement Multiplier

First-party donor data — already available in Segment and Snowflake — can be used to build custom audiences for retargeted paid media on Meta and Google. This creates a reinforcing loop: OBUSA delivers messaging to known donors on the platforms where they spend time outside their inbox, increasing brand recall and mental availability. When a subsequent email arrives, the recipient is more likely to recognize, open, and act on it. That engagement signal returns to the Braze profile and strengthens qualification criteria for future sends. Contacts who are currently excluded from email sends due to Gmail reputation challenges can still be reached through paid retargeting — keeping the relationship warm while inbox placement recovers.

On-Site Personalization

Known donors visiting outwardbound.org can eventually be served personalized on-site experiences using Braze’s web channel capabilities combined with Segment’s identity resolution. A donor arriving from an email link sees a landing experience calibrated to their giving history. A lapsed donor arriving organically can be served a re-engagement prompt. This is not an immediate implementation priority — it requires Segment’s web SDK to be the sole tracking layer, not running alongside GTM simultaneously. But the data to power it already exists in the Segment CDP. This is the logical next extension of the infrastructure already in place.

The Data Feedback Loop

The strategic value of multi-channel coordination is not just that it reaches donors in more places. It is that every interaction — email open, website session, form completion, paid ad engagement, SMS reply — comes back into the same Segment profile. Over time, this produces a progressively richer behavioral picture of each contact, enabling more precise segmentation, better timing, and higher-relevance content — which produces stronger engagement signals — which improves deliverability — which increases reach. Each cycle compounds. The infrastructure investment made now is what makes that compounding possible.

Fall 2026 and Into 2027

The next six months are the most consequential in the program’s transition. The work done between now and end-of-year fundraising determines whether OBUSA enters 2027 with mature, automated, high-reach infrastructure — or carries current limitations into another fundraising cycle.

Phase Roadmap: All Priority Journeys Before Year-End

What Success Looks Like by End of 2026

Best Practices to Carry Forward — 2026–2027 Planning

Beyond OBUSA’s own roadmap, it’s worth grounding next steps against where the broader sector sits today. The following is organized into what to track ourselves against, what infrastructure rules are now non-negotiable across the industry, and what donor lifecycle and content practices are worth building toward deliberately over the next 18 months.

Sector Benchmarks Worth Tracking Against

Deliverability Guardrails Now in Force

Google, Yahoo, and Microsoft’s bulk sender requirements — in force since 2024–2025 and fully enforced by 2026 — apply to any domain sending 5,000+ messages per day, a threshold OBUSA crosses regularly. The rules are no longer best practice; they are the price of inbox entry. Two thresholds matter most: keep spam complaint rate under 0.10% for healthy, reliable placement, and never approach 0.30%, which triggers hard rejection (not just spam-foldering) at Gmail and Yahoo. OBUSA’s own Postmaster data has held at 0% spam rate throughout the entire recovery window — comfortably inside the safe zone, and part of why the climb from Bad to High was possible. Compliant senders see roughly 89% inbox placement industry-wide; non-compliant senders see 22–34%, a 3–7× penalty. One-click unsubscribe (RFC 8058) is required, not optional, for all marketing sends going forward.

Lifecycle Automation Practices to Build Toward

• Welcome series, 3 parts over the first 30 days: introduce mission, share a concrete impact story, and offer a clear, low-friction next step — sector-standard structure for turning a new subscriber into a relationship.
• First thank-you within 48 hours of a gift: speed matters more than polish here; a fast, warm acknowledgment outperforms a delayed, elaborate one.
• Repeat-gift cultivation track at 90 days: a donor who gives again within 90 days of their first gift should move out of the generic welcome series and into a track built around sustained engagement, not re-onboarding.
• Lapsed-donor win-back trigger at 9–12 months: an automated re-engagement series highlighting a recent, concrete win, paired with a low-barrier way back in (a short survey, a small ask) — directly aligned with what SYBUNT data already shows works for OBUSA specifically.
• Dedicated mid-level donor cadence: donors between mass-appeal and major-gift territory often fall through the cracks. A quarterly cultivation track — program updates, behind-the-scenes content, early access to impact reporting — keeps this segment from being underserved by both ends of the program.

Content Cadence Practices

• Baseline appeal frequency: 1–2 dedicated fundraising appeals per month outside of major campaign windows; 3–5 per week is appropriate and expected during EOY and Giving Tuesday — provided the stewardship layers underneath are also running.
• Newsletter, monthly at minimum: the sector floor is monthly; several well-regarded nonprofit programs have moved to biweekly or weekly successfully once they had the content pipeline (Layer 02, above) to support it without straining the team.
• Keep individual newsletter stories tight: 100–200 words per story, one primary feature plus one or two secondary items, is the sector norm for a reason — it respects attention and keeps the format skimmable.
• Treat advocacy and thought-leadership content as its own category, not newsletter filler: given its outsized CTR performance sector-wide, CEO thought leadership and cause-advocacy content likely deserves its own individual sends rather than being buried as a newsletter section.

Operational Transparency and Reporting

Three standing initiatives are in place to ensure leadership-level visibility into program health and project progress across the organization:

Weekly Braze Development Performance Reports — filtered to Development-tagged communications and shared with the CDO and development team. These reports provide ongoing data on send volume, deliverable counts, engagement rates, and complaint signals, replacing the need to infer program health from anecdotal reports or one-off requests.

Bi-Weekly Massive Rocket Progress Summaries — synthesized from standing weekly calls and capturing completed activity, active work, upcoming milestones, and any risks or blockers. Shared in written form to support both leadership transparency and project documentation.

Expanded Weekly Meeting Participation — Megan (data and segmentation infrastructure) and Vito (IT and DNS) now participate in the standing weekly meeting, providing real-time access to updates across the data, deliverability, and infrastructure workstreams simultaneously. This eliminates the information latency that has historically required separate follow-up conversations across teams.