Skip to content

MailerLite Overview

IxDF's email marketing platform for newsletters and campaigns. This doc is a bridge between the dev team and the campaigns team — it explains what data is available, how segments work, and what changes automatically.

For code details, see mailerlite-technical.mdFor v5 list separation spec, see docs/specs/2026-02-mailerlite.md

In a Nutshell

Early 2026 data (pre-v5):

v5 changes (Feb 2026): IxDF now uses two separate MailerLite accounts to give subscribers granular unsubscribe control:

  • IxDF News & Legacy — "Important News" (campaign emails)
  • IxDF Power — "1 Powerful Email Each Week" (automated weekly chain)

Subscribing on ixdf.org auto-subscribes to both lists. Each list can be unsubscribed independently.

Purpose

MailerLite handles newsletter marketing:

  • Automated weekly email chains for new subscribers
  • Targeted campaigns based on membership status
  • Masterclass, course, and promotion announcements

What MailerLite does NOT handle:

  • Transactional emails (password resets, receipts) → Mailgun
  • In-app notifications → Internal notification system

MailerLite Concepts

Groups vs Segments

ConceptWhat it isHow it works
GroupStatic subscriber listSubscribers are explicitly added/removed
SegmentDynamic filtered viewAuto-updates based on custom field values

Account Structure (v5)

IxDF uses two MailerLite accounts with separate sender domains.

Accounts and Groups

AccountGroupSender Domain
IxDF Power1 Powerful Email Each Weekpower.ixdf.org / power-for-members.ixdf.org
IxDF NewsImportant Updatesnews.ixdf.org / news-for-members.ixdf.org
IxDF NewsNewsletter (Legacy)interaction-design.org

IxDF Power Segments (2)

SegmentSender Domain
Active Memberspower-for-members.ixdf.org
Non-Memberspower.ixdf.org

IxDF News Segments (5)

SegmentSender Domain
Active Members (Legacy)interaction-design.org
Non-Members (Legacy)interaction-design.org
Active Membersnews-for-members.ixdf.org
Non-Membersnews.ixdf.org
Cancelled Membersinteraction-design.org

Legacy segments receive the same campaigns as non-legacy, but from the old sender domain (during the warm-up period for new domains).

Automated Email Chains (v5)

Each account uses two separate workflows — one for Members, one for Non-members. The content is completely different with zero overlap, so a subscriber who becomes a member starts the member chain from email #1 without seeing duplicate content.

The legacy Newsletter chain has been stopped. Legacy subscribers only receive campaign ("Important News") emails. Almanac newsletters have been discontinued.

Subscriber Journey

Key behavior: When a member cancels, they move to the Cancelled Members segment — they are NOT re-added to non-members.

Subscribing and Unsubscribing

Subscribing

Subscription forms on ixdf.org auto-subscribe to both lists (Power + Updates). Non-members receive an email confirmation; members do not need one.

Unsubscribing

Every email contains 3 unsubscribe links:

  1. List-Unsubscribe header — controlled by MailerLite (the Gmail/Outlook top link)
  2. IxDF link in the email footer — links to ixdf.org where subscribers manage preferences per list
  3. Built-in MailerLite footer link — visually hidden

Members can also manage subscriptions from the Notification Settings panel.

Custom Fields (what the IxDF app syncs to MailerLite)

These custom fields are automatically kept in sync. Use them when building segments or personalizing campaigns.

Fields Available for Segments and Personalization

FieldExample ValuesUse For
nameJohn DoePersonalization
countryDenmark, United StatesGeo-targeting
membership_lifecycle_stateactive / expired / canceled / emptySegment assignment
token(unique per subscriber)Unsubscribe link variable

membership_lifecycle_state — the main segmentation field

This field reflects the subscriber's current membership status on IxDF. It updates automatically when their membership changes.

ValueWho is in this stateWhat happens next
activePaying member with a valid subscriptionStays active, or expires/cancels
expiredMembership ran out, in a grace period (14–50 days), may still renewRenews → active, or times out → canceled
canceledMembership ended (didn't renew or manually canceled)Can reactivate → active
(empty)Never been a member — free subscriberPurchases membership → active

Typical lifecycle:

Free subscriber → active (purchases) → expired (runs out) → canceled (doesn't renew)

Or: activecanceled (manual cancel)

Reactivation is always possible: canceledactive

Deprecated Fields (still present, avoid using for new segments)

These older fields are still synced but have been replaced by membership_lifecycle_state:

FieldPossible ValuesWhy Deprecated
member_statusnon-member / canceled / active-or-expiredLumps active and expired together — use membership_lifecycle_state instead
membership_expire_atDate like 2025-03-15Expiry date; replaced by lifecycle state which is more actionable
membership_plan_categorynon-member / individual / teamNo longer needed for segmentation
Deprecated field values reference

membership_plan_category (deprecated):

ValueMeaning
individualSubscriber has an individual membership plan
teamSubscriber is on a company/team plan
non-memberSubscriber has never been a member

member_status (deprecated):

ValueMeaning
non-memberNever been a member
canceledMembership canceled
active-or-expiredActive or expired (no way to distinguish)

When Do Fields Update?

The IxDF app updates MailerLite custom fields when:

  • Someone subscribes to the newsletter
  • A membership is purchased, renewed, or canceled
  • A membership expires
  • A subscriber changes their email preferences on ixdf.org

Two-Way Sync Between IxDF and MailerLite

DirectionWhat triggers it
IxDF → MailerLiteNew subscriber, membership change, preference change on ixdf.org
MailerLite → IxDFSubscriber unsubscribes, bounces, or reports spam in MailerLite

Important: Never delete subscribers directly in MailerLite — the IxDF app does not detect deletions, only unsubscribes/bounces/spam reports.

Known Trade-offs

  1. No cross-account spam protection — MailerLite's "don't email twice in a week" does not work across the two accounts. A subscriber could receive emails from both accounts on the same day.
  2. Loss of historical statistics — Engagement data from the legacy account does not carry over to new accounts.
  3. Loss of chain progress — Legacy chain progress is not transferable; new chains start from email #1.
  4. Hardcoded subscriber counter — The displayed count on ixdf.org adds 300,000 to prevent drops after cleanup.

Open Questions

  1. Move existing members from Legacy to new lists? Requires warming up power-for-members.ixdf.org and news-for-members.ixdf.org first.
  2. Legacy list end-of-life — When and how does the Legacy Newsletter list get decommissioned?
  3. Reply-to address — What should reply-to be for campaign emails from the new domains?

Access