Updated · 8 min read
Subject line anatomy: the four parts every line that performs shares
Subject-line advice usually fixates on details: emoji or not, length, numbers vs words. The details matter less than the structure. The lines that consistently out-open the inbox share a four-part anatomy that keeps them scannable, specific, credible, and low-stakes to read. Here's the anatomy, the three ways programs distort it, and how to test without fooling yourself.
By 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 scannable, 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" — the actual thing. "Your March invoice". "3 new templates". "The IP warm-up plan". Specific nouns create an information scent readers scan for. Abstract nouns read as generic, because they are.
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. No reason, no open.
3. Credibility.Implicit or explicit. "Your March invoice" is credible because it's transactional and timely. "New features you'll love" reads as sales because the claim is unsupported. "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 to parse. Urgency ("Don't miss out!") is emotional cost. Curiosity loops ("You'll never guess…") are emotional cost. Specificity plus credibility beats urgency plus 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. Scannable 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 sits in the middle of the line, it never gets read.
Design for the first 40 characters. Everything past that is bonus text for desktop preview, not where the decision happens. Preheader text (covered in the preheader guide) is where the secondary scan earns its keep — and preheader should complement the subject, not duplicate it. Repeating the subject wastes the exact real estate where a second argument could live.
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 some mobile clients, break subject-line truncation in unhelpful places. 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 most users filter it unconsciously. The open-rate lift has decayed year-on-year since about 2015. If you're going to personalise, personalise something that matters — a specific account detail, a specific outcome, a specific next step — not the name field.
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-converting tier. Urgency lands when the timing is genuinely scarce ("Ends 5pm Friday"). It doesn't land when the caps key is trying to manufacture it.
How to test subject lines without fooling yourself
Subject-line A/B tests are low-effort to run and high-noise on small audiences. Four rules keep them honest.
1. Test hypotheses, not variants."Specific noun vs generic noun" is a hypothesis — it produces a finding you can reuse. "Blue vs green button" is a colour test that happens to use subject lines as the randomiser. The second teaches you nothing generalisable.
2. Measure click, not open. Apple MPP inflates opens for Apple Mail users. Clicks still reflect humans doing things. The MPP guide has the mechanism 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 around 50,000 conversions to detect reliably. Most teams don't have that volume, which means most subject-line tests are answering a question they can't actually answer — and then someone puts the result in a deck.
4. Kill the novelty effect. New variants can outperform for three to seven days on novelty alone. Run the test for at least two full cycles of your natural sending rhythm before reading results. Anything shorter is a vibe, not a finding.
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 makes a good email subject line?
- Four ingredients. Specific (names a thing the reader can visualise, not abstract), short enough to not truncate on mobile (~35-55 chars is safe), carries a concrete hook rather than generic curiosity ("Your Tuesday delivery is out" beats "Update for you"), and flows into the preheader rather than duplicating it. Bad subject lines fail one or more: too long, too vague, no hook, or the preheader restates the subject.
- How long should an email subject line be?
- 35-55 characters is the safe zone for mobile visibility. Gmail desktop shows ~70 characters; iOS Mail cuts around 35-40 depending on portrait/landscape; Apple Watch truncates aggressively at ~20. If the subject line makes sense truncated at 35, it'll work everywhere. Longer subject lines can work on desktop but consistently underperform on mobile, where the majority of opens now happen.
- Do emojis in subject lines help open rate?
- Sometimes. The honest answer: emojis produce ±5-10% open-rate variance depending on audience and context. B2C audiences often respond well to one well-chosen emoji. B2B audiences often react against them — seen as unprofessional. More than two emojis almost always hurts — reads as marketing-template. Test per audience rather than applying a universal rule.
- Should subject lines ask questions?
- Occasionally, not as a default. Questions work as a hook when the question is genuinely interesting and the email answers it ("Why did Gmail clip your last send?"). Questions fail when they're rhetorical or formulaic ("Ready for the weekend?"). The pattern that consistently underperforms: generic question subject lines on promotional sends. The pattern that works: specific, answer-promising questions on curiosity-driven content.
- How do I A/B test subject lines?
- Send each variant to a random 10-20% of the audience, measure open rate on the primary metric, declare the winner, then send the winner to the remaining 60-80%. Most ESPs automate this as a "winner send" feature. Caveats: open rate is contaminated by Apple MPP, so results on audiences with significant Apple share are noisy. Where possible, use click-through rate or downstream conversion as the winner metric rather than opens.
This guide is backed by an Orbit skill
Related guides
Browse allPersonalisation that doesn't feel creepy
There's a line between personalisation that earns trust and personalisation that breaks it. It's not where most people think it is — it's about how you signal what you know, not what you know. Here's the line, how programs cross it without noticing, and the patterns that keep you on the right side.
Push notification copy that actually gets tapped
Push is the highest-interrupt channel in the stack. A bad push burns goodwill in under a second; a good one feels like a useful nudge from a friend. This is the copy discipline — specific words, specific structures, specific anti-patterns that reliably get a user to turn your notifications off for good.
The SMS playbook from the operator's seat
SMS is the highest-engagement and highest-risk channel in the lifecycle stack. Here's the compliance architecture, the copy discipline, and the frequency rules that keep SMS from destroying the goodwill it's uniquely positioned to create.
Preheader text: the second subject line most programs ignore
The preheader is the snippet shown next to the subject line in the inbox preview. Treat it like a second subject line and you double your hook. Treat it like an afterthought and it says 'View this email in your browser'. Here's how to write preheaders that actually earn the open.
Transactional emails: the highest-engagement messages you ignore
Order confirmations, password resets, receipts, shipping updates. Transactional emails post open rates two to three times higher than marketing sends — and most lifecycle teams have never touched them. Effort is going to the wrong place.
Liquid for lifecycle marketers — the complete Braze reference
Every personalised field in every Braze message runs through Liquid. Get it right and personalisation quietly improves every send. Get it wrong and 50,000 people see 'Hi {{${first_name}}}'. This reference covers the syntax and the production habits that stop that happening.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 54 lifecycle methodologies, 55 MCP tools, native Braze integration. Pay what it's worth.