Gravity Forms notifications that actually arrive.

Comparison reflects each vendor’s default behaviour as of 2026-06. Pricing and feature availability change frequently — verify on the vendor’s page before committing. WP Mail SMTP is an independent product. Gravity SMTP is made by Rocketgenius, the company behind Gravity Forms; its details here come from gravityforms.com and docs.gravitysmtp.com (checked 2026-10-29). In the Gravity SMTP column, a dash means we did not find the feature in its documentation.

• Does Gravity Forms's User Registration add-on email work?

  Yes. The User Registration add-on uses wp_mail() to send activation links, password setup emails, and notifications when a user submits a registration form. All of those route through SecureSMTP automatically — no extra configuration in the add-on settings.
• What about partial entry notifications?

  Yes — Gravity's partial-entry save-and-resume emails route through SecureSMTP. The resume URL (whether encrypted-token or standard-link variant) is preserved in the email body exactly as Gravity generates it. We hook at pre_wp_mail, which fires after Gravity has assembled the message.
• Will Stripe / PayPal / Square payment forms work?

  Yes. Gravity's payment add-ons trigger order-confirmation and admin-notification emails through wp_mail() after a successful transaction. Those route through SecureSMTP like any other notification. Stripe/PayPal webhooks themselves are HTTP calls — orthogonal to email.
• Does GravityFlow workflow email work?

  Yes — GravityFlow's "User Input", "Approval", and "Notification" workflow steps all use wp_mail() to send their assignee/approver/notification emails. Routes through SecureSMTP unchanged. The workflow audit trail in Gravity is preserved separately on Gravity's side, so you keep both logs.
• GravityView / GravityCharts — anything to know?

  GravityView's entry-update notifications and GravityCharts' scheduled-report emails both use wp_mail(). They route through SecureSMTP without special configuration. If you've wired up custom hooks via gform_after_submission or gform_entry_post_save to send your own email, those custom hooks also go through SecureSMTP.
• Multi-site (network) installs — does SecureSMTP work network-wide?

  Yes, but each site needs its own SecureSMTP API key. In a WordPress multisite network, you network-activate SecureSMTP and then each subsite's admin pastes their own SecureSMTP API key under the network site's settings. Each subsite's email count is tracked separately against its own quota.
• Do my Gravity merge tags still work?

  Yes, completely. Gravity does its merge-tag resolution ({Name:1}, {Entry ID}, {date:format=...}, etc.) inside the gform_notification filter chain, which fires BEFORE wp_mail() is called. By the time SecureSMTP sees the message, the merge tags are already replaced with the actual values from the entry.
• Will this change the notes Gravity Forms adds to each entry?

  No. Gravity Forms adds an entry note (Forms → Entries → open an entry → Notes) saying WordPress passed the notification to the sending server. It adds that note when wp_mail() succeeds, and wp_mail() succeeds when SecureSMTP accepts the message for routing (within a few milliseconds). The note keeps working. SecureSMTP adds a separate, more detailed log (delivery status, bounces, complaints) on top.