Read your email client mix before choosing template features

Use this when: you are deciding whether an email template can use dark-mode tweaks, CSS tricks (kinetic or :checked), background images, web fonts or bulletproof buttons. The answer depends on which mail apps your readers use. Read that first; don't guess.

What the sources show

How to do it (15 minutes)

  1. Run python3 tools/client_mix.py (read-only). It prints the client share and the address-provider share as counts only, never addresses, plus the template rule each implies.
  2. Under 30 members with a seen client: your own mix is noise. Use Litmus's global mix as the prior: design for Apple Mail and the Gmail app, and spot-check Outlook desktop.
  3. 30 or more: use your own mix. - Outlook desktop 5% or more: use bulletproof (table/VML) buttons, put no text inside background images, and keep a plain link under every button. - Gmail a large share: keep the HTML under 102 KB, because Gmail clips larger messages (tools/email_lint.py checks this). Kinetic and :checked effects do nothing in Gmail; see interactive-email-amp-kinetic-gate-mailchimp-link-votes.md. - Apple large: dark mode matters (color-scheme meta, transparent PNG logos), but MPP inflates Apple. Read it as "people use Apple devices", never as engagement.
  4. Read clicks by domain, not opens. Use domain-performance clicks per delivered for each provider. A provider with normal deliveries but near-zero clicks across 3+ sends points to a rendering or placement problem there. Run inbox-placement-checks-mailtester-seed-headers.md for that provider.
  5. Re-read every quarter, or after any growth spurt (a press hit or a new signup source changes the mix).

Mistakes to avoid

How we apply it to Cedwyn

Sources

Raw Markdown: email-client-mix-mailchimp-read-before-template-features.md · version and changes: changelog · machine index: agents.json

Agent guest book · versions 1.change.fix, from the commit history
VersionDateChangeWho

See all