{"id":23765,"date":"2019-07-16T00:00:00","date_gmt":"2019-07-16T00:00:00","guid":{"rendered":"https:\/\/www.mailgun.com\/blog\/mailgun-dyspatch-building-a-bridge-between-developers-and-marketers-2\/"},"modified":"2026-09-16T14:42:32","modified_gmt":"2026-09-16T14:42:32","slug":"mailgun-dyspatch-building-a-bridge-between-developers-and-marketers","status":"publish","type":"blog","link":"https:\/\/www.mailgun.com\/fr\/blog\/product\/mailgun-dyspatch-building-a-bridge-between-developers-and-marketers\/","title":{"rendered":"Mailgun + Dyspatch\u00a0: cr\u00e9er un pont entre l’\u00e9quipe de d\u00e9veloppement et l’\u00e9quipe marketing"},"content":{"rendered":"\n

Everyone knows that Mailgun is the email service built by and for developers who need a powerful email infrastructure. If you\u2019re itching to learn more, take a minute to click around the website. We\u2019ll wait.<\/p>\n\n

Developers are able to do what they do best in Mailgun, but marketers can be left shoulder tapping if they have a less-than-technical grasp of email design. And it\u2019s no secret that coding email is not high on most developers\u2019 list of priorities.<\/p>\n\n

Thankfully, your developers and marketers can get the best of both worlds when you pair Mailgun with\u00a0Dyspatch<\/a>\u00a0\u2014 a transactional email production platform that allows you to create and change transactional emails independently of your codebase, customer data, and ESP.<\/p>\n\n

Wait \u2014\u00a0what<\/em>\u00a0kind of email?<\/strong><\/h2>\n\n

So what exactly is transactional email? If you didn\u2019t get a chance to read Mailgun\u2019s recap of\u00a0Transactional and Marketing emails<\/a>, give yourself a few minutes to get acquainted before moving forward. Long story short, they\u2019re those automated emails that are triggered as a result of an action on the customer\u2019s part. Mailgun is great for sending those emails in a way that takes care of your sender reputation and deliverability, and for tracking opens, clicks, unsubscribes, and spam complaints, but those email messages still need to be created and maintained.<\/p>\n\n

\"Interface<\/figure>\n\n

Different folks in different roles will view transactional emails differently. But when it comes to getting them built or edited, everyone involved has a pain point. With developers focused on higher priorities and marketers chasing promotional goals, optimizing transactional emails, to keep content, branding, and compliance up-to-date is often a challenge.\u00a0We\u2019ve all received one of\u00a0those<\/em>\u00a0transactional emails \u2014 you know the type, an email that bears virtually zero resemblance to the app or company website, plain text with no images or CTA, and with virtually no branding whatsoever. \u00a0<\/p>\n

\r\n\r\n

You can solve all those challenges with an email template management process that makes it easy for developers and less-technical users (i.e. marketers) to collaborate on transactional email content.<\/p><\/div>\r\n <\/div>\r\n\n

Dyspatch establishes a template-based workflow that will not only make your developers happy, but your product owners and marketers will be satisfied as well. With templates managed outside of the code base, you can standardize and lock down common elements, such as headers, footers, tables, and CTAs, or the code strings that pull order, account, or offer details, while allowing less-technical stakeholders the flexibility to easily change content, such as copy and graphics.<\/p>\n\n

So how does Dyspatch work with Mailgun?<\/strong><\/h2>\n\n

Dyspatch allows teams to create and change emails faster while ensuring every email is on-brand and fully compliant. Dyspatch adds a layer within which you can create and edit your email templates \u2014 a front-end, user interface where you can organize your templates within workspaces, update content in the easy-to-use visual editor, and test with built-in device testing. The way you and your systems interact with Mailgun remains unchanged. And once the templates and components (headers, footers, CTAs, etc.) are created, developers can focus on other projects, only needing to check in from time to time if the code needs updating.<\/p>\n\n

Here are the nuts and bolts of our integration:<\/strong><\/h3>\n\n
    \n
  1. Create or update your email template in Dyspatch.<\/li>\n\n\n\n
  2. Test your template using sample data with built-in device testing.<\/li>\n\n\n\n
  3. Submit your tested template for approval.<\/li>\n\n\n\n
  4. Once approved, you can retrieve the template with an API call.<\/li>\n<\/ol>\n\n

    When an email needs to be sent:<\/p>\n\n

      \n
    1. The retrieved template is prepared for rendering by inserting the recipient, sender, and localization data.<\/li>\n\n\n\n
    2. The template HTML, text, and metadata are rendered using the Jinja library.<\/li>\n\n\n\n
    3. The rendered email is passed to Mailgun for sending.<\/li>\n<\/ol>\n\n
      \"Flux<\/figure>\n\n

      Can it really be that simple?<\/strong><\/h2>\n\n

      Yes, it can. At the end of the day,\u00a0Dyspatch<\/a>\u00a0and Mailgun want to make things easier for everyone on your team. Developers and marketers get to do what they do best \u2014 create. Developers can focus on building great products and marketers can concentrate on creating great brand experiences. Together, they can collaborate seamlessly on optimized transactional emails that engage customers and drive growth.<\/p>\n\n

      Featured Webinar \u2014\u00a0<\/strong>Mailgun + Dyspatch: Helping Developers and Marketers Find Middle Ground on Transactional Email<\/strong><\/a><\/p>\n\n

      \"Mailgun<\/figure>\n\n

      Finding email workflow solutions that satisfy both marketers and developers can be challenging and frustrating for both parties. By pairing Mailgun and Dyspatch, marketers can own transactional content creation with reduced reliance on developers. In this webinar, we covered the different pain points that come alongside transactional email creation and different ways to solve them.\u00a0Check it out!<\/p>\n\r\n