GMass has updated its Transactional API to let transactional emails follow your configured Message Routes. This means your automated emails will use the same delivery settings as your regular GMass campaigns.
Previously, if you sent transactional emails through the GMass Transactional API, they did not automatically honor your Message Routes. If you routed emails through a mail gateway such as Proofpoint or Mimecast, you may have needed a separate setup or experienced inconsistent delivery methods.
With this update, GMass automatically applies your existing Message Routes to transactional emails. If your route is configured to use OAuth or SMTP, GMass will use the correct delivery method without any extra changes.
For example, if you send transactional emails such as password resets, order confirmations, notifications, or receipts through the GMass Transactional API, those emails will now follow the same routing rules as your marketing campaigns.
This means you can:
- Keep email delivery settings consistent across all GMass emails.
- Reduce manual configuration for transactional email routing.
- Ensure emails sent through gateways like Proofpoint or Mimecast use the correct authentication method.
More about Gmass features and integrations.
