Key takeaways
- Set pre-header text explicitly to avoid truncated fragments or default messages.
- Complement subject line with new value, not repetition, in preview text.
- Front-load urgency in first 40 characters for mobile visibility guarantee.
- Test cross-client rendering before deployment to catch truncation points.
Your email pre-header is the 40-to-90 character string that appears beside or below the subject line in most inbox views. Get it right and you have two headlines working in concert. Get it wrong, and most subscribers see either a truncated fragment or the words "view this email in your browser" before they have even decided whether to open.
That gap between what you intended to show and what actually renders is where open rates are lost. This guide covers how to close it.
Why pre-headers fail so often
The most common failure mode is not a bad copywriting decision. It is a technical one. When no explicit pre-header is set in the HTML, the email client pulls the first readable text it finds in the message body. For transactional templates that means an accessibility skip-link, a tracking pixel alt tag, or the literal string "If you cannot see this email." None of those convert.
Rendering is the second problem. Preview length is set by the email client, the device and the orientation, and none of the major clients publishes a fixed limit. Illustrative order-of-magnitude estimate, not a substitute for your own calculation: Gmail on Android in portrait mode shows around 100 characters. Apple Mail on iOS shows up to about 140. Some desktop Outlook versions clip after as few as 35. Because your subscribers read across all of these environments, test the pre-header in each one rather than writing it for a single client.
A reliable way to check is to push every campaign through a cross-client rendering tool such as Email on Acid or Litmus before deployment. These tools simulate dozens of client-and-device combinations in minutes and flag truncation points precisely. Pair that audit habit with your customer journey optimisation work and you will catch errors that analytics alone never surfaces.
Writing preview text as a continuation
The relationship between subject line and pre-header should be additive. The subject line opens a thought; the pre-header completes it, adds evidence, or introduces a second reason to open. Repetition is the biggest waste of the space.
Consider a subject line built around subject line personalisation: "Maria, your basket is still waiting." The pre-header should not echo that. It should carry the message forward: "Your items are reserved until midnight. Free shipping on orders over £75." That single sentence adds urgency messaging, states the free shipping threshold, and gives a second, distinct reason to act.
A few principles hold across categories:
- Write the pair together. Subject line and pre-header are one unit of attention, so draft them side by side rather than treating the pre-header as an afterthought once the subject line is approved.
- Front-load the value. Mobile-first design conventions mean the first 40 characters of the pre-header are the only ones guaranteed to show. Place the incentive or the social proof signal there, not at the end.
- Avoid mirroring urgency phrases already in the subject line. If "last chance" appears in the subject, the pre-header should provide context ("Only 3 units left in your size") rather than repeat the emotion.
- Test sender name optimisation separately. The sender name occupies visual real estate adjacent to the subject line, so changes there interact with how the pre-header reads as a whole. Treat the three elements as a triad: sender, subject, preview text.
Technical implementation without rendering bugs
The standard method is a hidden span placed at the very top of the email body, before any visible content. The span contains your pre-header text followed by a run of zero-width non-breaking spaces and regular spaces. The spaces push any subsequent body text beyond the character limit that email clients pull for the preview, so only your intended copy appears.
Here is the structure in brief. The span carries a style of display:none; max-height:0; overflow:hidden; and a mso-hide:all attribute for Outlook compatibility. The filler characters sit immediately after the pre-header copy inside the same span. That construction works across Gmail, Apple Mail, Yahoo Mail and most Outlook versions.
Where it breaks down is in plain-text fallback versions. If a subscriber's client is set to receive plain text only, the hidden span is irrelevant and the first visible text wins again. Always confirm that your plain-text version leads with a substantive sentence rather than a navigation label or unsubscribe link.
Dynamic content compounds the risk. If you inject dynamic product recommendations or a countdown timer into the pre-header via merge tags, confirm that the fallback value is set. An empty merge tag renders as a blank or, worse, as the literal tag string, both of which damage credibility with the segment you most want to convert.
Matching pre-header to campaign type
The right approach varies by email type, and applying a single formula across your programme will leave value on the table.
For abandoned cart recovery emails, the subject line typically names the behaviour ("You left something behind"). The pre-header is where you address the hesitation: a trust signal, a returns policy reminder, or a social proof line such as the number of other shoppers viewing the same item. Incentive placement works here when the discount or free shipping offer appears in the pre-header rather than buried below the fold of the email body.
Browse abandonment emails call for a different angle. The subject line may reference a product category; the pre-header can introduce a dynamic product recommendation pulled from the session data, giving the subscriber a specific reason to return.
Promotional campaigns around seasonal peaks benefit from countdown timer copy in the pre-header ("Sale ends Sunday at midnight") that reinforces urgency messaging without crowding the subject line. Post-purchase sequences, by contrast, should use the pre-header for reassurance: a delivery update, a one-click return to basket for a related purchase, or a reference to product imagery in the email body to set expectations before the subscriber opens.
| Campaign type | Subject line role | Pre-header role |
|---|---|---|
| Basket abandonment | Name the behaviour or item | Address hesitation with a trust signal or incentive |
| Browse abandonment | Reference the category browsed | Surface a dynamic product recommendation |
| Promotional | Announce the offer or event | Add urgency with a deadline or threshold |
| Post-purchase | Confirm or celebrate the order | Reassure with delivery detail or related product |
Send-time cadence also affects how the pre-header reads. A pre-header written at 9 am that references "today only" can become misleading if your sending infrastructure delays delivery by several hours. Either use relative language ("ends tonight") or connect the pre-header copy to a live data feed where your setup supports it.
Measuring the impact of pre-header changes
Open rate is the obvious metric, but it is now complicated by Apple's Mail Privacy Protection, which pre-fetches open pixels regardless of whether a human opened the message (Apple, 2021). Lean on click-to-open rate instead: if more of the people who did open went on to click, the pre-header and subject line combination is working as a pair.
A clean A/B test isolates the pre-header as the single variable. Hold subject line, sender name, send time and segment constant. Run the test on a statistically meaningful portion of your list before full deployment. For most mid-market programmes, that means a minimum of several thousand addresses per variant before the result is actionable.
The experience optimisation mindset applies here as much as it does on-site: every element of the inbox experience is a hypothesis, not a finished decision. Iterating on pre-header copy quarter by quarter, against a consistent measurement framework, compounds into a measurable lift in revenue per email sent.
Segmentation sharpens the picture further. A pre-header that converts well for a high-frequency buyer may underperform for a lapsed segment, because the two groups carry different levels of brand familiarity and purchase intent. Behaviour-based targeting gives you the granularity to test different pre-header angles against different segments in the same campaign, rather than averaging across your whole list and missing the signal.
SaleCycle: Intelligence Centre and Activation Suite
The Activation Suite's Multi-channel Remarketing capability handles the end-to-end email workflow, from dynamic content injection through to send-time logic, so the pre-header, subject line and body content all draw from the same real-time data layer. Rendering audits, variant testing and segment-level performance reporting sit within the same environment, which removes the manual reconciliation step that most teams lose time to every campaign cycle.
If you want to see how pre-header copy interacts with your segment behaviour and campaign performance on your own data, Book a demo.
