Make it personal

Show each subscriber the content that matters to them, and greet them by name. Your team sets simple rules and mailCMS writes the code in your ESP’s own language, so personalisation no longer needs a developer.

Speak to everyone at once

One email can speak to every part of your audience. Your team decides who sees each module using the data you already hold in your ESP, like where subscribers live or anything else you track, and combines as many conditions as they need.

  • Rules for any module
  • Match any or all of your conditions
  • One email for every audience

Fluent in your ESP

Rules come out as the code your ESP expects, whether that’s HubL, Liquid or Handlebars, so they work the moment your email arrives in your platform. We set it up for you, and your team never has to look at the code unless they want to.

  • HubL, Liquid, Handlebars and more
  • Set up for your platform
  • Show or hide the code as you build

On first-name terms

Add a subscriber’s name, city or anything else you hold, right in the text. Test emails show realistic preview values, so everyone can see how it reads, and your export carries your ESP’s own tags, ready for the real send.

  • Tags set up for your data
  • Preview values in test emails
  • Your ESP’s own tags on export

Room for your developers

For anything the rules don’t cover, anyone comfortable with code can write their own logic around a module. Developers and marketers work in the same email, and nobody has to hand anything over.

  • Your own logic around any module
  • Edit or remove it at any time
  • Visible in the editor as you build

FAQs

Do we need to know HubL, Liquid or other code?

Not at all. Your team builds rules by choosing a field, a condition and a value, and mailCMS writes the code. Anyone who does know code can write their own too.

Which ESPs does it work with?

We set mailCMS up to write the language your platform uses, such as HubL for HubSpot, Liquid for Braze or Handlebars for Iterable. Our team will confirm the details for your platform when we scope your project together.

Where does the subscriber data come from?

Your ESP. mailCMS never sees your subscriber data. Rules and tags go into your email as code, and your ESP fills them in when it sends.

How can we check a personalised email before it goes out?

Test emails use each tag’s preview value, so you can see how the email reads. In the editor, you can show or hide the personalisation code around each module as you build.

Can we send emails in more than one language?

Yes. You can set up a master email with merge tags for the translated content, then upload a CSV file with the text for each language. mailCMS uses it to build a separate version of the email for each language.

See how mailCMS could work for your brand

Book a friendly, no-pressure 30-minute walkthrough. We’ll look at how you build emails today and share practical ideas you can use straight away, whether or not you choose mailCMS.