Article

9min read

52 Email Subject Lines That Work From Fashion and Beauty Brands

You’ve all heard the saying before: You should never judge a book by its cover. Sounds ridiculous, right? Well, whether you like it or not, that’s exactly how people tend to determine an email’s worth by its subject line. 

To give you some perspective, 35% of email recipients open emails based on subject lines alone according to HubSpot, and 21% of subscribers mark boring ones as spam, even if they know they aren’t. 

In other words, customers are tough to impress. 

If you really want to get noticed and prove you are deserving of their time and attention, supercharge your email subject lines with emotion. Because in the end, no matter how much we rationalize, our buying decisions spring from our emotions

Read more: Creating Emotional Connections with Customers Using Data

Think of what a customer fears, dreams of, desires and wants in a product or solution. Use that as a premise of your subject lines to trigger an emotional response

Some fashion and beauty brands have already been doing consistently well in this area. It’s time you learn the ropes from them.

Fair warning: It’s not a good idea to rely on emotions alone. The purpose of retail brands, like yours, is to sell. So hit a variety of customer touchpoints, including sending personalized emails, because they are 26% more likely to be opened than those without. Even better, they deliver 6X higher transaction rates.

Anyway, let’s dive in…

Email subject lines that induce FOMO

What does FOMO mean? Fear of missing out.

No one likes missing out on time-sensitive deals, including you. Just think of the last time you jumped on an offer because you didn’t want to regret losing out on a good bargain. 

In another case, imagine a time when you felt some stress for not having bought something when there was still time, stock, and a good deal. 

The same emotional reaction happens to your customers. Whether it’s creating a top-notch holiday campaign, announcing a limited time or a limited stock sale, pick the right set of words like ‘last chance, ‘don’t miss…’, to create urgency. Seeing such offers immediately activates this fear of missing out and drives them to act right away. 

It’s exactly why this email from The North Face displays. The simple nudge is enough to get their recipient to grab this one– the last chance to save some money.

The North Face - using FOMO in email subject line

Examples of FOMO-provoking email subject lines:

Limited time offer:

  • Alice & Olivia: LAST.DAY.DROP.EVERYTHING.
  • Dropps: Get 15% off, but move quick.
  • UNIQLO: TICK TOCK! Free shipping ends tonight
  • Mango: LAST FEW HOURS to enjoy 30% off the entire collection!

Show it’s in demand: 

  • Nykaa: These will sell out in 3…2..⏳
  • Sorel: These stunners are selling out fast
  • Olay: Get it before it’s gone!🎁
  • Marc Jacobs: New to sale and going fast

Imply negative outcomes: 

  • Nykaa: You snooze, you lose.
  • Revolve: Say goodbye to 65% off 👋
  • UNIQLO: Get it before it’s gone
  • Nike: Good stuff in your cart…checking out > missing out

More ideas:

  • You’ve still got time
  • Offer expires tonight
  • The stock’s running out
  • UH-oh. Your fav styles are (almost) gone
  • ATTN: This pack will DEFINITELY sell out
  • Saying goodbye is the toughest
  • Our top 10 at 10% off for the next 24 hours
  • LAST chance to save up to $55
  • <New product> is selling like hot cakes
  • You’ve ONE day left: FREE shipping +20% off
  • Tonight only: Your wish list items on sale
  • LIMITED-time offer on items on your wishlist

Email subject lines that drive curiosity

Can you guess what makes crime drama series binge-worthy? Why we click intriguing Upworthy and BuzzFeed posts? Or why we can’t stop reading novels? Blame our inherent need to close the loop between what we know and what we want to know. Otherwise known as – our curiosity!

This is also exactly why when people receive emails with partial information in the subject lines, they feel the urgent need to click ‘open.’ 

A perfect example is this email from Nykaa. This cliffhanger technique adds a touch of drama and mystery that is enough to tempt people to see what’s on the other side.

Nykaa - using curiosity in email subject line

Examples of using curiosity in subject lines: 

  • Huckberry: “Want” — everyone
  • Michael Kors: Give us an inch…
  • J.Crew: The shorts circuit
  • TwoThirds: Meet our unique pieces!
  • Revolve Tomorrow’s outfit forecast
  • Kate Spade: You’re getting sleepy…
  • Steve Madden: TORNADO warning
  • Anthropologie: Let us per-SUEDE you.
  • Birchbox: We’ve got some ideas for you.
  • Sephora: Because you need these.
  • Estée Lauder Online: Why’s everyone obsessed with retinol?
  • Jimmy Choo: Dreams are made up of these + complimentary global shipping

More ideas:

  • Not even in your wildest dreams would…
  • Got a sec? Open this email right away, or…
  • FIRST time ever on sale
  • New launches inside
  • Is THIS what you’ve been waiting for?
  • You DESERVE this
  • Don’t buy from us…
  • Before you regret not buying your favs
  • Saying goodbye is the toughest
  • Did we tell you that…
  • This is personal…

How to personalize and test subject lines to maximize your open rate

By crafting a personalized email with your customer’s name or a point of interest in the subject line, you’re ensuring a connection with your customer.

According to Forbes, 72% of customers ONLY interact with personalized messaging.

Personalization is an important way to build trust with your customer and maintain your relationship with them before, during, and after their purchases. If you’re not using personalization in your email campaigns, you’re likely missing out on a huge opportunity. 

Whether you’re looking to personalize your email content to capture customer attention or A/B test your subject lines to determine the best-performing phrase, choosing the right software will help you transform your ideas into reality.

AB Tasty is the complete experience optimization platform to help you create a richer digital experience for your customers — fast. From recommendations to smart search, this solution can help you achieve personalization with ease, experiment with a low-code implementation and revolutionize your brand and product experiences.

Email subject lines that spark happiness

Since you already occupy a sacred space in your customers’ inboxes, why not become a reason for their happiness?

A lot of things make people happy. So right from using humor, wordplay, solving people’s problems, appealing to their vanity, surprising them with freebies and special offers to reminding them there’s good in them. For example, if you can relate their shopping efforts to contributing to a social cause, that’s one idea of reminding them there’s good inside.  There are plenty of ideas that you can use to really catch their eyes and make them feel unique.

This email from Fortress of Inca, for example, plays the vanity card. Honest confession: I was at the receiving end and I had to open the email because my fabulous choice in shoes was being appreciated!

Fortress of Inca_ triggering happiness through email subject line

Examples of subject lines focusing on happiness:

  • Pura Vida: Save the Amazon Rainforest!
  • Michael Kors: FOOD IS LOVE: Help Us Watch Hunger Stop
  • Sephora: Your beauty issues solved
  • Nicole Miller: Button me up, Button me down.
  • Alice & Olivia: Hot date? We’ve got you.
  • J.Crew: We don’t do this (MAJOR) sale too often…
  • JustFab: Your FREE money is waiting. We put $30 in your account.
  • Pura Vida: Happy birthday to us (gifts for you!)
  • DSW: Find out how you can make a difference.
  • Patagonia: School lunch made easy
  • The North Face: 5 jackets that will have everyone saying…where’d you get them from!

More ideas: 

  • Our birthday treat = gifts for you!
  • Giving > Getting
  • It’s true…these will look dapper on you
  • What to wear for the New Year’s bash
  • Style secrets you can master in under 10 minutes
  • Your winter break packing list is HERE!
  • You’re one click away from shopping complete spring look
  • Impressed by items in your card: Buy ‘em before they’re gone
  • You earned what’s INSIDE this email

Email subject lines that create excitement

So far we’ve already established that humans are emotional creatures. Let’s now use excitement to get your sales meter ticking, because chances are that it results in impulse shopping.

Selling to customers is much easier when they’re excited and in touch with their emotions. In a state of excitement, your level of enthusiasm brings you to think and behave differently.

There are a number of ways to get the excitement level up. You can start by highlighting the exclusiveness of your offer, adding social proof (drop names and numbers), capitalizing action verbs to motivate action completion and even using emojis and exclamation marks.

In the email subject line below, team Pura Vida does two things — attract attention and excite the subscriber with the clever use of an emoji, the word ‘holy smokes,’ and a few ‘!

Pura Vida - triggering excitement in email subject line

Examples of Building Excitement in Subject Lines:

  • J.Crew: What Adam Scott thinks of our suits
  • Anthropologie: Just for you: the inside scoop
  • Pura Vida: Special offer (but only for our BFFs)
  • Olay: Over 50 million sold ❤️
  • Sorel: Meet our exclusive Frozen 2 boots✨
  • DSW: Reviewers have spoken: “BEST BOOTIE EVER!”
  • Steve Madden: Take our shoe stylists’ word for it
  • Meundies: Well, this is exciting!
  • Adidas: You’re in. Welcome to Adidas
  • Revolve: This collab was made for you
  • theBalm Cosmetics: Welcome to #THEBALMERS community!
  • Victoria’s Secret: 60% off bras & apparels, in stores only! GO, GO, GO!

More ideas: 

  • Beyonce-approved autumn wear you can’t say no to
  • Sweet launch discount (for members only!)
  • Howdie! Your faves are back in stock
  • Sshh…you’re the FIRST ONE to be seeing this
  • It’s between you and us ONLY
  • For your eyes only, because you wanted it
  • Baby, it’s baccccck!
  • It’s your birthday! Get 30% off, a FREE gift and free shipping.

Ready to Craft Email Subject Lines That Deliver?

Full disclaimer: It takes a lot of A/B testing and patience to come up with subject lines that stay within the 40-50 characters limit and stir the right emotions. Thankfully,  now you’re aware of which emotions to go after and how to invoke emotional decision-making.

So it’s time to get to work! But before you go, and for maximum impact, keep these equally important things in mind:

  • Match your brand personality with the tone of voice of your subject lines.
  • Segment your audience to send targeted/personalized emails.
  • A/B test your email send times.

Subscribe to
our Newsletter

bloc Newsletter EN

We will process and store your personal data to respond to send you communications as described in our  Privacy Policy.

Article

9min read

Chaos Engineering 101: How Chaos Brings Order

As we go deeper into digital transformation and as companies move towards large-scale globally distributed systems, the complexity that comes with them increases. This means that failures in these intricate systems become much harder to predict, as opposed to traditional, monolithic systems. 

Yet, these failures could result in high costs for teams to repair them; not to mention the painstaking probability of the potential loss of new and existing customers.

The question then is how can we build confidence in the systems that we put into production? How can teams make sure that they’re releasing stable and resilient software that can handle any unpredictable conditions that they’re put into?

This is when teams turn to what is aptly referred to as “chaos engineering”.

What is chaos engineering?

According to the Principles of Chaos, chaos engineering is “the discipline of experimenting on a system in order to build confidence in the system’s capability to withstand turbulent conditions in production.”

In other words, chaos engineering is the process of testing distributed systems to ensure that it can withstand turbulent conditions and unexpected disturbances. Strictly speaking, this is the “chaos” of production.

Chaos engineering is particularly applicable to large-scale, distributed systems. Since such systems are now hosted on globally distributed infrastructures, there are many complex dependencies and moving parts with several points of failure. This makes it harder to predict when an unexpected error will occur.

Due to the unpredictability of these failures of the components of the system, it becomes harder to test for them in a typical software development life cycle.

This is when the concept of chaos engineering came about as a way to predict and test for such failures and uncover hidden flaws within these systems. 

In other words, this concept determines the resilience of these systems by identifying their vulnerabilities by carrying out controlled experiments to test for any unpredictable and unstable behavior.

This is done by breaking things on purpose by injecting failure and various types of faults into the system to see how it responds. This will help determine any potential outages and weaknesses in the system.

The ultimate goal of this is a lesson in how to build more resilient systems.

Where does the term come from?

Before we delve any deeper into chaos engineering, it would be helpful to understand where this concept originated.

Chaos engineering started in 2010 when the engineering team at Netflix decided to develop “Chaos Monkey”, which was later made open source, as the team at Netflix migrated from a monolithic architecture to the cloud, deployed on AWS.

For Netflix, this migration to hundreds of microservices brought on a high amount of complexity; therefore, engineers at Netflix were seeking a better approach to prevent sudden outages in the system. 

These engineers were mainly looking for a way to disable instances and services within their architecture to ensure that their system can handle such failures with minimal impact on the user experience, allowing them to build a more resilient and reliable architecture.

The idea behind the Chaos Monkey tool was that they would unleash a “wild monkey” to break down individual components in a carefully monitored environment to make sure that a breakdown in this single component wouldn’t affect the entire system. 

This, in turn, helped them locate the weaknesses in the system and build automatic recovery plans to address them and alter the system if necessary so that it could easily tolerate unplanned failures in the future.

Afterwards, Chaos Monkey improved and evolved to allow Netflix engineers to more precisely determine failures by testing against more failure states, enhancing the resilience of their system.

From then on, the chaos journey began for Netflix and later on for many organizations dealing with similar distributed systems.

Principles of chaos engineering

We can deduce that chaos engineering involves running experiments to understand how a distributed system behaves when faced with failure.

Unlike other forms of testing, chaos engineering involves experimentation and learning new things about a system by creating a hypothesis and attempting to prove that hypothesis. If it’s not true, this is a chance to learn something new about the system.

Testing, on the other hand, involves making an assumption about a system based on existing knowledge and determining whether it’s true or not by running tests; in other words, the test is conducted based on knowledge of specific properties about the system. The results, therefore, don’t provide new insights or information.

Chaos engineering, for its part, involves exploring scenarios that don’t usually occur during testing designed to gain new knowledge about the system by considering factors that often go beyond the obvious issues that are normally tested for.

The following principles provide a basis on which to run such experiments on your system:

  1. Plan an experiment

The first step involves planning an experiment, where you will need to pinpoint things that could go wrong. This will require gaining an understanding of your system’s normal behavior and determining what constitutes a normal state. Afterwards, you start off by forming a hypothesis of how you think the components of your system will behave in case something goes wrong and then create your control and experimental groups accordingly. 

Defining a metric to measure at this stage is useful to gauge the level of normalcy within your system. These could include metrics such as error rates or latency. 

  1. Design real-world events

At this stage, you will outline and introduce real-world events that could potentially cause disruptions to your system such as those that occur within hardware or server or any other external event that could lead to outages in your system such as a sudden spike in traffic, hardware failures, network latency or any event that could potentially disrupt the steady state of the system.

  1. Run the experiment

After defining your system’s normal behavior and the events that could disrupt it, experiments can then be run on your system preferably in a production environment to measure the impact of the failure to gain a better understanding of your system’s real-world behavior.

This will also allow you to prove or disprove your hypothesis. The harder it is to cause an outage in the system, the more confident you can be in your system’s resilience

However, keep in mind that since your experiments are run in production, it’s important to minimize the blast radius in case something goes wrong. This will ensure that any adverse effects are kept at a minimum and if things go smoothly, you can then gradually increase this radius till it reaches full scale. It’s also wise to have a roll back plan if something does go wrong.

  1. Monitor results

The experiment should give you a clear idea of what’s working and of what needs to be improved by looking for a difference between the control and experimental group. Teams can then make the necessary changes as they’re able to identify what led to the outage or disruption to the service, if relevant. 

Why we should break things on purpose: Benefits of chaos engineering

We can look at chaos engineering as a sort of safeguard that helps prevent worst case scenarios from happening and impacting the user experience before they actually happen.

Consequently, chaos engineering has a number of benefits.

Increased reliability and resilience

As we’ve already mentioned, running such controlled chaos experiments will help determine your system’s capabilities, thereby preparing the system against unexpected failures. 

Information gathered from these experiments can be used to strengthen your system and increase its resilience by locating potential weaknesses and finding ways to resolve them.

In other words, by learning what failure scenarios to prepare for, teams can improve and speed up their response to troubleshooting incidents. 

Enhanced user experience

By strengthening your system, it is less likely that it will experience major outages and downtime that could negatively affect the user experience. It allows you to pinpoint issues and problems before they actually become customer pain points.

This will, in turn, result in improved user experience and increased customer satisfaction as you are now releasing high performing, more resilient software.

Reduced revenue loss

By running chaos experiments, companies can prevent lengthy disruptions and outages to the system, which otherwise could lead to losses in revenue as well as high maintenance costs.

Improved confidence in the system

The insights gathered from these experiments can help teams build more resilient and robust systems.

This means that teams, by predicting the unexpected, are prepared for worst-case scenarios, which helps to increase confidence in their systems by having a recovery plan set up for such scenarios.

Nonetheless, organizations should still carefully consider the challenges of chaos engineering before implementing it as, despite its benefits, it can also be costly and time-consuming.

Unleashing chaos for better digital experiences

As we’ve seen, chaos engineering is an essential practice when it comes to creating uninterrupted, seamless digital experiences for your customers.

It’s not just breaking things for the sake of breaking things; it’s a way to gain insight on how a system behaves and to gauge its resilience. In other words, chaos engineering is not only breaking things, but it’s also about fixing weaknesses in a system to build its resilience by exposing hidden threats thereby minimizing risk.

It’s important to note that chaos engineering isn’t meant to replace the other types of testing that are carried out throughout the software development life cycle but instead to complement these tests to provide a high performing system.

Finally, chaos engineering has an important role in DevOps. At the heart of DevOps is the idea of continuous improvement, which is why integrating chaos engineering into a DevOps methodology is essential to mitigate security risks. It’s also a way for DevOps teams to deal with the rising complexity of applications nowadays.

Consequently, introducing chaos experiments into your DevOps CI/CD pipeline will help teams detect hidden issues more quickly, which grows confidence in the system enabling them to deploy faster to end-users.