Recorded events, not guarantees
Delivery, opens, and clicks reflect the latest recorded provider events. We never promise inbox placement, guaranteed delivery, or exact open counts.
Header fields
Subject
Our spring plan for the river
Preheader
Three ways to get involved this month
From
Meadowlark Alliance
Reply-to
Content blocks
Preview
Our spring plan for the river
Hi {first_name}, here is how Meadowlark Alliance is protecting the watershed this season — and three ways you can help.
Get involvedYou are receiving this from Meadowlark Alliance · Unsubscribe
Choose an audience from your CRM, compose from blocks with personalization, test before you send, and measure recorded delivery, opens, and clicks — all on the record that already knows your supporters.
The operating loop
Pull recipients from CRM lists and saved cohorts, then see exactly how many are email-ready before you commit. A suppression drawer explains every held address — unsubscribed, bounced, category opt-out, or duplicate — so your send list is honest.
Total selected
12,662
across 3 lists
Email-ready
11,607
deliverable
Suppressed
1,055
see reasons
Selected lists & cohorts
Monthly newsletter
List
Ward 3 signers
Cohort
Lapsed donors
Cohort
Why suppressed
Global and category suppression applied before send · demo data
Split a test percentage across variants, hold out the rest, and pick a winner by recorded open or click rate. The winning subject releases to the remaining list — while charts stay clear that they reflect recorded provider events, not guaranteed opens.
Our spring plan for the river
Test share 20%
Three ways to protect the watershed
Test share 20%
Test share
40%
20% each
Holdout
10%
winner release
Criterion
Open rate
then click
Winner to
50%
remaining list
Recorded opens by variant
Based on recorded provider open events · not a delivery guarantee
Send now or schedule in a chosen timezone, with optional modeled optimal timing offered — never promised as lift. Verify your sending identity and custom-domain status through a DNS workflow, and run a real test send before launch.
Delivery
DateSat, May 10 · 9:00a
TimezoneAmerica/New_York
Optimal timingModeled · optional
Sender identity
Custom-domain verification is a DNS workflow — never automatic.
Test send
Test recipient
Track delivered, opens, clicks, bounces, and unsubscribes against a recorded-event time series and a recipient-status breakdown. Every number is framed as the latest provider event, never inbox placement or exact opens.
Delivered
11,412
recorded
Opens
3,864
recorded
Clicks
1,092
recorded
Bounces
195
Unsub
73
Recorded events · first 12 hours
Latest provider events · opens are recorded, not exact
Recipient status
Delivered
11,412 recorded
Opened
3,864 recorded opens
Clicked
1,092 recorded clicks
Bounced
195 hard bounces
Unsubscribed
73 opt-outs
Delivery, opens, and clicks reflect the latest recorded provider events. We never promise inbox placement, guaranteed delivery, or exact open counts.
Unsubscribes, hard bounces, and category opt-outs are held automatically, with the reason shown for every suppressed address.
Custom-domain sending uses a DNS verification workflow with clear status — it is never automatic, and SES failover applies only when enabled.
Templates and personalization are yours to write; optimal timing is modeled and optional. No AI copy generation and no promised lift.
Audience, composer, A/B testing, and recorded-event reporting in one connected workspace.