4 thoughts on “The Complete Marketer’s Guide to Transactional Emails

  1. Hello,

    I want to use SendInBlue to send transactional emails like “abandoned cart”, “product introduction” etc. but there is no option of how to send emails which have differing/generated elements in the content.

    Say for example that my client buys product A, and I want to send them am email which corresponds to product A. and If they buy multiple products (A,B,C) then I want to send them email X.

    I am unable to find anything in your documentation to help me do that.

    Or if a client leaves the store and leaves product A and B in the cart, then I can´t seem to find a way to display the products A and B in the email.

    Please help me

    1. Hi Robin,

      If you are trying to send completely different email templates depending on the products purchased or abandoned, you would need to work with a developer to send these using the API. If you just want to populate the same email template with different product information, you can do this directly in the template. This article talks about how to do it with a WooCommerce framework –> https://www.sendinblue.com/blog/how-to-customize-woocommerce-emails/.

      Generally, transactional emails are sent automatically from your website and they are triggered by specific actions. For this reason, they are usually implemented using the API (using code on the back end of your website). SendinBlue is an SMTP relay, which means you can use our sending framework to route your transactional emails programmatically through our system, but it requires either code that is integrated directly with your website or through the use of certain ecommerce plugins like the SendinBlue plugin for WooCommerce.

  2. Please describe some best practices that’ll help me to create brilliant and lovable transactional emails, that never cease to amaze. Apart from this This is a really good read for me. Thanks for posting this informative blog.

Leave a Reply

Your email address will not be published. Required fields are marked *