Integration / Mailchimp

Sembr & Mailchimp.

Your member list stays in sync with your Mailchimp audience. Consent flags travel with each contact so CASL and PIPEDA-aware sends stay clean.

What this does

One source of truth, two surfaces.

Push on status change

Sembr is the source of truth. Active members appear in Mailchimp; lapsed/deceased/opted-out auto-remove within minutes.

Consent-aware

CASL and PIPEDA consent flags travel with each contact. You don't accidentally email someone who opted out.

Field mapping

Sembr tier, status, and tags map to Mailchimp tags. Custom Sembr fields map to Mailchimp merge fields.

Status: Phase 2.

Sembr ships with native email tools (renewal reminders, member announcements, event invites) so most orgs do not need Mailchimp for core operations. The integration is for orgs that have an established Mailchimp setup and want to keep it.

# Sembr native email (built-in)
> renewal reminders
> member announcements
> event invites
> automated lapse outreach
> via Resend (DKIM-signed, SPF-aligned)
FAQ

Common questions.

What about Mailchimp tags vs Sembr fields?
Sembr tier, status, and tags map to Mailchimp tags (configurable in setup). Custom Sembr fields can map to Mailchimp merge fields. Field mapping is set once at integration time and editable afterward.
Will my Mailchimp automations still trigger?
Yes. Sembr's push respects Mailchimp's subscription/unsubscription status, so automations triggered by "subscribed to audience" or "added to segment" fire normally.
What if we use Mailchimp's e-commerce features?
Out of scope at launch. The integration syncs member contact data only, not transactional history. For revenue attribution, use the Sembr / QuickBooks/Xero sync instead.
Is the sync two-way?
One-way push only at launch (Sembr to Mailchimp). Reverse sync (Mailchimp subscribes new contacts back into Sembr) is Phase 3.

One source of truth, two surfaces.

Sembr for member operations. Mailchimp for campaigns. No double entry.