A subject line should identify a relevant reason to open without misrepresenting the email. Preview text should add context, specificity, or a useful second idea rather than repeat the subject. Draft both after the email has one clear job, then test them against downstream behavior and complaints, not open rate alone.
Who this is for: Lifecycle and content marketers writing promotional, educational, onboarding, or transactional email for permission-based lists.
- Make the subject-preview pair an accurate promise about the message a subscriber will receive.
- Use concrete nouns, timing, and value where relevant while avoiding fabricated urgency or curiosity.
- Judge performance with clicks, completions, replies, unsubscribes, and complaints alongside opens.
Clarify the email's job
Before writing the inbox copy, state the audience segment, trigger, desired reader outcome, primary action, and evidence. A welcome lesson, abandoned setup reminder, product announcement, and receipt should not share the same persuasion pattern. If the email contains three unrelated announcements, resolve that scope problem before polishing a subject line.
Identify what the recipient already expects based on signup source, relationship, and timing. A person who requested a checklist should recognize that delivery immediately. A customer receiving a policy change needs the change and effective date, not playful suspense. Relevance comes from context and permission, not inserting a first name into generic copy.
Draft the subject promise
Write several angles based on the actual content: direct description, useful outcome, specific question, timely reminder, or concrete update. Use familiar words and place distinctive information early because inboxes truncate text differently. Keep the sender identity and subject working together; do not spend the subject repeating a brand name already visible beside it.
Check every implied claim. 'Last chance' requires a real deadline. 'Your account needs attention' requires an actual account issue. Questions should not imply that the sender knows something it does not. Avoid tricks such as fake reply prefixes, fake order notices, or manufactured personal concern. They may attract an open while damaging consent and trust.
Use preview text as a second line
Preview text can explain the action, name the artifact, supply a date, or resolve ambiguity. For 'Your July reporting checklist,' the preview might say, 'Five checks to run before sharing channel totals.' That adds a concrete reason to open. Repeating the subject wastes scarce inbox space.
Control unintended previews by setting deliberate preheader text and testing major clients where feasible. Otherwise the inbox may pull navigation, an image label, or an unsubscribe sentence. Keep essential meaning in the subject because previews can be hidden or truncated. Do not place a required legal disclosure only in preview text.
Test the whole promise
Compare subject-preview pairs on a defined segment with a large enough sample for the decision. Keep sender, timing, and email body stable when testing inbox copy. Open measurement is imperfect because privacy features and automated activity can affect it. Use the test to learn about qualified engagement rather than declaring one phrase universally superior.
Review clicks, completed actions, replies, unsubscribes, spam complaints, and downstream quality. A sensational subject can raise opens while lowering meaningful action. Save tested pairs with audience, trigger, body, date, and outcome. Learn patterns, but do not convert one winner into a formula applied to unrelated emails.
Write the inbox copy for a report
Subscribers asked for a monthly analytics worksheet, and the first email delivers the completed July template.
- Define the job as delivering the requested worksheet and helping the subscriber perform the first review.
- Draft direct subjects that name the July marketing report worksheet rather than promising vague growth.
- Use preview text to add the specific first task: reconcile spend and tracked conversions before calculating return.
- Check that the email contains the promised file, instructions, and support path with no hidden sales condition.
- Measure worksheet access and replies beside opens, unsubscribes, and delivery problems.
Inbox copy review card
Review each subject-preview pair against the actual message and recipient context.
- Email job: segment, trigger, existing expectation, useful outcome, and primary action.
- Subject: angle, distinctive words, concrete detail, implied claim, urgency basis, and truncation check.
- Preview: added context, non-repetition, essential-detail check, and fallback content.
- Trust: sender clarity, permission, accurate personalization, no deceptive convention, and body match.
- Evaluation: test cell, clicks, completion, replies, unsubscribes, complaints, and downstream quality.
Common mistakes
- Optimizing open rate with a subject that the email body cannot honestly fulfill.
- Repeating the exact subject in the preview instead of using the second line for added meaning.
- Declaring a winner from opens alone without checking action quality, opt-outs, or complaint signals.
Try one
An email announcing a routine feature update uses 'URGENT: Your account is at risk.' Evaluate it and propose a better pair.
The original falsely implies an account threat and should be rejected. A good replacement names the updated feature in the subject and uses preview text to explain what changed, who is affected, and whether action is required. Evaluation should prioritize accurate expectations and downstream engagement over curiosity-driven opens.
Sources
- Google Analytics event definitionOfficial GA4 definition of event-based measurement.
- Google Analytics key events guideOfficial GA4 guidance for measuring and reporting business-important actions as key events.