MessageGears features: what you get on each plan

Every line below was read on 14 September 2026 against two publisher surfaces that agree: the product pages on messagegears.com and the Accelerator documentation on docs.messagegears.com.

The From plan column cannot do its usual job here. messagegears.com/pricing/ returned 404 on that date, and no plan name appears anywhere on the site. MessageGears is sold as one quoted contract, so the question this table normally answers, which tier unlocks a feature, has no answer.

Feature matrix

How to read this table

The prerequisite is the gate. The whole table is available to every customer, and the barrier sits one step earlier: MessageGears queries your warehouse rather than copying your data into its own, so a team without Snowflake, BigQuery or Databricks cannot buy the product at all. Read this as a list of what a warehouse buys you, not as a ladder.

The A/B testing line is the one to read twice. The documentation describes a Split node that randomly divides an audience into branches, and an older help centre article covers multivariate and A/B testing on marketing campaigns, so splitting traffic is real. What is documented nowhere is the part most marketers mean: a campaign-level test that measures both arms and promotes the winner by itself. You split, you send, you compare afterwards in the analytics. That gap is why buyer reviews call this platform an ESP with no A/B testing while the product pages advertise it, and why both are defensible.

Pre-send checking beats its reputation. The template docs list personalisation preview against real recipient data, SpamAssassin scoring, Litmus evaluation across more than 14 spam filters, rendering in over 30 email clients and a subject line preview. Buyers who complain about the missing staging environment mean something else, a place to rehearse a whole campaign, and that really is absent. The per-message checks are not.

Suppression is documented as a policy, not a product. The bounce guidance hands you thresholds to implement: one invalid recipient, no more than three consecutive DNS failures, five spam blocks in thirty days, ten attempts in six months with nothing delivered. Those are rules you build against your own data, which fits the architecture and adds one more line item for the data team.

Continue reading

• MessageGears review, rated 5.8 out of 10, including the sending policy last revised in 2012
• MessageGears overview