Postmark

Postmark's 'Broadcast' Message Streams technically permit bulk/newsletter-type sends (each must include an unsubscribe link) and separate them from transactional traffic for deliverability, but there is no campaign builder, audience/list management UI, or contact segmentation tool — the sending application must build the email and manage recipients itself. This is sending infrastructure, not a marketing-email product, so marketing_email is recorded as false; see the transactional_email/note and automation/segmentation fields for the same distinction.

This is Postmark's core, entire product.

SMTP is offered as a first-class alternative to the REST API, described as 'a fast, reliable, care-free replacement for SMTP.'

Covers delivery, bounce, open, click, spam complaint, subscription-change, and inbound events; up to 10 webhook URLs per stream.

No visual workflow/automation builder of any kind; sends are triggered entirely by the customer's own application code.

No contact database or audience segmentation tooling — Postmark has no concept of a stored contact list.

No native A/B/split-testing feature; a 2016-era third-party integration (Sendwithus) offered this but Postmark itself does not.

No SMS product found anywhere on postmarkapp.com.

No landing-page builder; the footer directs marketing-site needs to sibling product ActiveCampaign.

No native signup/subscribe form builder.

Automatic bounce and spam-complaint handling, DKIM/SPF/DMARC setup guidance, a dedicated DMARC monitoring tool (paid add-on, from $14/mo per domain on postmarkapp.com/pricing), Message Streams to isolate sending reputation by traffic type, and optional dedicated IPs.

Starts at $50/month per IP; only available to customers sending 300,000+ emails/month.

No native Shopify app on postmarkapp.com; connected via Zapier or custom API/webhook integration built by the merchant.

No first-party WooCommerce plugin from Postmark; routed via WordPress SMTP plugins (e.g. WP Mail SMTP, ShopMagic) or Zapier that connect to Postmark's SMTP/API.

No first-party Magento extension from Postmark; third-party Magento 2 SMTP extensions (e.g. Plumrocket, Mageplaza) or Zapier connect to Postmark's SMTP/API.

Not a marketing/ecommerce product; no such feature exists.

No native ecommerce event tracking or cart-abandonment triggers; would have to be built by the customer's application and sent as a transactional message.

No revenue/purchase-attribution reporting found; Postmark's analytics cover delivery/open/click/bounce events only, not ecommerce revenue.

Live chat Monday-Friday 9am-6pm EST via Help > Ask > Chat; email support otherwise (average response under 3 hours). No phone support found; not available 24/7.

No first-party page found that explicitly states whether free-plan accounts receive the same support access as paid accounts. Support pages describe channels without mentioning plan-based gating, but that is not a positive confirmation. See reports/needs-verification.md.

Signable DPA incorporating Standard Contractual Clauses, offered to all customers.

First-party FAQ states: 'Postmark is a US-based company and we also store our data in the US, including personal data of our customers.' No EU hosting option is offered.

First-party support article states: 'Even though Postmark itself has not undergone a SOC audit, our data center has.' Postmark's data center (Deft) holds SOC 1/SOC 2 accreditation, but Postmark as a company has not obtained its own SOC 2 report — recorded as false to reflect Postmark's own status, not its data center's.