I've been looking for a non-ruby dependent task to replace Premailer in this grunt workflow. At first glance looks like your email builder could be a good solution. Cheers.
Any quirks to be aware of?
I used them with a few transactional emails.
Marking them up is straight forward:
To test them the sender and recipient should be an @gmail address:
To register with Google, the steps are outlined here:
The issue here is you have to put these into production, then send them to Google, which requires a few more "dev" steps on your part. After I emailed Google it took ~2 weeks for them to approve us and for them to work across the board.
They did stop working at one point. Then you're left wondering if it's a problem with your code or did Google change the whitelisting status.
Would love to see more examples of things that worked, things that didn't work, a/b tests across design, content, timing, triggers. All the data related talks last year were super interesting.
Also more about practical implementation. If talking about segmenting and triggers for example, talk about the tools/resources/people used to do that. I'm always curious what the overall workflow looks like from end-to-end.