There are no standards in email HTML. It means that you won't be able to use the techniques you got used to on the web.
Some of the email clients don't support div tags, only tables, some of them don't support media queries or even classes.
Our service generates the most robust email HTML code, so you don't need to know email HTML.
We support the biggest number of email clients on the market. (Link to compatibility.)
Always generate nice looking transactional emails, marketing emails, newsletters or digest emails.
Example
- generating digest emails programmatically --- build up a json -> generate
Automated Email HTML Maintainance
Description
- we take care about the changes in email clients, karbantarthatóság! --- mini releasek száma from Pati's cikk!!!
- leírni, hogy milyen költségei vannak az email html karbantartásának
- https://litmus.com/blog/how-often-do-email-apps-change-more-often-than-you-might-think
- don't waste your time and energy, don't let your employees go nuts when they need to fix bugs in your emails
Example
- you figure out that your abandon cart (or any other) email breaks on some of the email clients.
- Git clone, modify the HTML, test it on Litmus or Email on Acid, test it on a real device, commit the changes. After that here comes the release process, and someone else will do the same.
Instead of that, you can store your emails in our JSON or XML format and generate it whenever you send out an email.
You can make sure this way that you will send our most up-to-date email code and you don't need to worry about email HTML maintainance again!
You know your audience better than anyone else. If you don't need some email client related feature, you can switch it of to make your email code shorter.
You can also select different generation strategies that fits your audience and your ESP.
Also, you can set different properties like line-length.
For example, if you don't need to support Outlook, you can switch of VML backgrounds. That can save lots of lines of code.
Read more
Whenever we release something, we introduce it behind a feature toggle.
Its default value is false, you need to manually set it to true in order to try out the new feature or bugfix.
By doing it this way, we can make it sure that nothing breaks on your backend.
In many cases you might need to modify the code that was generated by our generator.
For example, you need to put some kind of tracking code on buttons.
If we change something in the button code, we do it behind a feature toggle, so you will have the chance to prepare for those changes.
Read more