Unified Email Manager / Providers & Compatibility
Work with the systems your site already uses.
UEM manages supported email interfaces and adds its own workflows while WordPress, WooCommerce and your configured transport keep their responsibilities.
Explore Unified Email Manager
Open the interactive workspace and try the controls.
Keep the working mail connection.
Sending continues through the host, SMTP plugin or API connection configured for the site. Configure its sending credentials and domain restrictions in that owning system. UEM’s provider screen configures supported feedback and correlation—not a replacement SMTP service.
| Provider feedback | Configuration |
|---|---|
| Mailgun | Enable feedback, use the webhook signing key and configure the provider callback. |
| Twilio SendGrid | Enable feedback with the public webhook verification key and a signed event webhook. |
| Brevo | Enable feedback with a matching secret bearer token and transactional callback. |
Google Workspace/Gmail, Microsoft 365/Outlook and Amazon SES transport configurations can be recognized where supported. Recognition alone is not a delivery-feedback connection.
Connect local activity to provider outcomes.
UEM inspects supported information from WP Mail SMTP, FluentSMTP and Easy WP SMTP. Built-in bridges add correlation information on relevant WP Mail SMTP and Easy WP SMTP API paths where supported. A recognized transport does not establish support for every private API route.
Provider callbacks authenticate their configured proof and normalized duplicate events are not inserted as identical new records. A genuine callback can still be unmatched when the transport drops the correlation metadata; it is not arbitrarily assigned by subject wording.
External provider plans, tracking settings, quotas and plugin compatibility determine the available feedback. UEM preserves the distinction between a recognized connection and a measured provider result.
WordPress first. WooCommerce where the workflow needs it.
Core requirements
Unified Email Manager requires WordPress 6.5 or later and PHP 7.4 or later. The supported deployment scope is a single WordPress site.
Without WooCommerce
Use core source management and applicable WordPress and newsletter-subscriber workflows.
With WooCommerce
Use supported order/customer audiences, order follow-ups, checkout consent and native simple-product/variation cart recovery.
A compatible AffStackDev Suite provides shared product navigation and a dashboard summary. Without it, UEM has a standalone menu. Standard PHP remains available; the Suite’s global enhancement disable takes priority over UEM’s local enhanced preference.
Match specialized workflows before deployment.
Use the current Customer Reference and Master Technical Reference for supported transports, provider feedback, imports and recovery requirements. Specialized checkout payloads, external services and custom subscription workflows require their own supported connections.
Provider recognition, supported source controls and native cart support are specific interfaces, not a promise to control every installed plugin or external service. Multisite certification is not included in this edition.
Background execution depends on the site scheduler, traffic, worker availability, provider limits and the workflow’s own controls. A due time is not a guarantee of execution at that exact second.