· 8 min read
Subject line anatomy: the four parts of every line that performs
Subject line advice usually fixates on details: emoji or not, length, numbers vs words. The details matter less than the structure. Subject lines that consistently out-open the competition share a four-part anatomy that keeps the line scan-able, specific, and credible. Here's the pattern.
Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
The four parts in order
Subject lines don't need to be clever. They need to be scan-able, specific, credible, and low-stakes. Clever is a bonus, not a requirement.
Every subject line that consistently performs has four components, usually in this order:
1. A specific noun.Not "news" or "update" but the actual thing: "your March invoice", "3 new templates", "the IP warm-up plan". Specific nouns create an information scent that readers scan for; abstract nouns read as generic.
2. A reason.Why should the recipient care specifically? "Your March invoice is ready" has a reason (it's ready, implying action). "3 new templates we built this week" has a reason (they're new, they're by you).
3. Credibility.Implicit or explicit. "Your March invoice" is credible because it's transactional and timely. Marketing subject lines lose credibility when claims are unsupported: "New features you'll love" reads as sales; "New features that ship this week" is credible because it's dated and specific.
4. Low emotional cost.The line shouldn't demand emotional labour. Urgency ("Don't miss out!") is emotional cost. Curiosity loops ("You'll never guess…") are emotional cost. Specificity + credibility beats urgency + curiosity at almost every tier of engagement.
Where the line should land visually
30–50chars
Visible subject line width on most mobile clients. Anything longer truncates.
~6words
Sweet spot for mobile-first audiences. Scan-able at a glance.
~60chars
Desktop Gmail visible width. Keep the critical words up front.
Most subject line drop-off is length-related, not content-related. A 90-character line is truncated in the inbox; the reader sees the first 40–50 characters and decides. If your specific noun is in the middle of the line, it never gets read.
Design for the first 40 characters. Everything after that is bonus text for desktop preview, not where the decision happens. The preheader text (covered in the preheader guide) is where you earn the secondary scan.
The three distortions that ruin a clean line
Emoji as emphasis.One emoji that visually represents the noun is fine. Two or more read as spammy and, on many mobile clients, break subject line truncation in unhelpful ways. Use emoji when the noun itself is ambiguous and the emoji disambiguates it ("🎉 Your 100th send"), not as decoration.
Personalisation as gimmick."Justin, check this out" reads as manipulation. The first-name-in-subject pattern is decades old and modern users filter it unconsciously. If you're going to personalise, personalise something that actually matters: a specific account detail, a specific outcome, a specific next step — not just their name.
All-caps urgency."LAST CHANCE" and "DON'T MISS" are conversion-negative in every test I've watched. They trip spam filters, they read as low-quality sender, and the users who open anyway are the lowest-conversion tier. Urgency lands when the timing is genuinely scarce ("Ends 5pm Friday"), not when the caps key tries to manufacture it.
How to test subject lines without fooling yourself
Subject line A/B tests are low-effort to run and high-noise in small audiences. The four rules that keep them honest:
1. Test hypotheses, not variants."Specific noun vs generic noun" is a hypothesis. "Blue vs green button" is a colour test that happens to use subject lines as the randomiser. The second tells you nothing generalisable.
2. Measure click, not open. Apple MPP inflates opens for Apple Mail users. Clicks still reflect human behaviour. The MPP guide covers why this changed and what to use instead.
3. Power the test for the effect you care about.A 3% relative lift on a 5,000-recipient variant needs ~50,000 conversions to detect reliably. Most teams don't have that volume, which means most subject line tests answer a question they can't actually answer.
4. Kill the novelty effect. New subject line variants can outperform for 3–7 days on novelty alone. Run the test for at least two full cycles of your natural sending rhythm before reading results.
The Orbit Lifecycle Copy Framework skill covers the four-part anatomy in more depth, including the tone-of-voice mapping for each part by channel.
Frequently asked questions
- What's the ideal subject line length?
- 30–50 characters covers what's visible on mobile inboxes where most opens happen. Desktop Gmail shows ~60. Write the line so the specific noun and the reason are both inside the first 40 characters; anything after is bonus preview.
- Should I use emoji in subject lines?
- One emoji that visually represents the subject noun is fine. Two or more read as spammy and can trip filters. Use emoji to disambiguate, not decorate.
- Does personalisation (first name) actually lift open rates?
- Marginally, sometimes. The effect has decayed over the last decade as users learned to filter it. Personalisation that matters (specific account detail, specific outcome) still works. First-name-in-subject as a gimmick is weak.
- Is urgency effective in subject lines?
- Only when genuine. 'Ends 5pm Friday' lands. 'LAST CHANCE' doesn't — it reads as manipulation and trips spam filters. The open-rate lift from manufactured urgency is usually offset by higher unsubscribes and lower downstream engagement.
- How do I test subject lines without fooling myself?
- Test hypotheses (specificity vs abstraction, question vs statement), not variants. Measure click not open (Apple MPP inflates opens). Power the test for the effect size you'd act on. Run at least two sending cycles to kill novelty.
- Should subject lines match preheader text?
- They should complement, not duplicate. Subject line earns the scan; preheader earns the open. If the preheader repeats the subject line, you've wasted the real estate where the secondary argument lives.
This guide is backed by an Orbit skill
Related guides
Personalisation that doesn't feel creepy
There's a line between personalisation that earns a user's trust and personalisation that breaks it. This guide is about where the line actually is, how lifecycle programs cross it without noticing, and the specific patterns that keep you on the right side.
A/B testing in email: sample size, novelty, and what to report
Most email A/B tests produce winners that don't reproduce. This guide covers the three reasons — under-powered samples, the novelty effect, and weak readout discipline — and how to design tests that actually drive decisions.
Price-testing through email: what's testable, what isn't
Email is often the first place teams try to price-test, and it's often where the wrong lesson gets learned. This guide covers what can genuinely be tested in email, what can't, and the measurement traps that make most email price tests unreliable.