Drip
Two-month digests that keep circling the same theme: get your data out of Drip and into your own stack.
A side-by-side editorial comparison of MailerLite and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
MailerLite put an AI agent in its HTML editor and split abandoned cart from abandoned checkout
Releases land every few weeks with a tight scope: brand styles, templates, and e-commerce automation triggers. May replaced the rich-text editor with a distraction-free Simple editor and rebuilt the Custom HTML editor with live preview, syntax highlighting and an integrated AI agent that edits HTML from plain-English instructions. June split abandoned cart into two triggers, and July added variant-level targeting to the purchase trigger, shipping on Wix first with other platforms rolling out.
Pushwoosh journeys can now read what a webhook says back and act on it mid-run.
The current release batch is broad but coherent. Journeys gained the ability to consume webhook response data and use returned values to personalize later steps in the same run. Messaging coverage evened out across channels, with PW_SMSSent and PW_WhatsAppSent events matching what email already emitted, and one-time WhatsApp sends no longer requiring a journey. On the web side, subscription forms can be dropped into any popup as lead capture, form field labels are editable without code, and the popup editor and targeting both got more room to work.
Releases land every few weeks with a tight scope: brand styles, templates, and e-commerce automation triggers. May replaced the rich-text editor with a distraction-free Simple editor and rebuilt the Custom HTML editor with live preview, syntax highlighting and an integrated AI agent that edits HTML from plain-English instructions. June split abandoned cart into two triggers, and July added variant-level targeting to the purchase trigger, shipping on Wix first with other platforms rolling out.
Two threads. Brand styles are being pulled out of settings and into the places people work — their own section, then a save-as-brand-style button inside the builder, then templates that populate from them automatically. Meanwhile the e-commerce side is getting more precise about shopper intent: cart versus checkout abandonment as separate moments, and product variants rather than products as the trigger unit. Both are depth in an existing product, funded by a clearer picture of what a small store's automations need.
Variant support shipped on one platform with the rest listed as coming, so the near-term work is finishing that rollout across BigCommerce, Shopify, PrestaShop, WooCommerce, Shoper and the e-commerce API.
The current release batch is broad but coherent. Journeys gained the ability to consume webhook response data and use returned values to personalize later steps in the same run. Messaging coverage evened out across channels, with PW_SMSSent and PW_WhatsAppSent events matching what email already emitted, and one-time WhatsApp sends no longer requiring a journey. On the web side, subscription forms can be dropped into any popup as lead capture, form field labels are editable without code, and the popup editor and targeting both got more room to work.
Two things are being closed at once. The channel gap is narrowing — SMS and WhatsApp are being given the same event surface and standalone send path email has had, which makes them first-class for segmentation and triggering rather than journey-only endpoints. The bigger change is that journeys are becoming stateful against the outside world: a webhook step that can return a value into the run turns the journey builder from a sequencer into something closer to orchestration.
Now that webhook responses can feed a running journey, the natural extension is branching on those values and handling failure paths when the external call does not answer as expected. Expect the remaining email-only capabilities to keep arriving for SMS and WhatsApp until channel parity is complete.
Other Mkt Auto products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either MailerLite or Pushwoosh.
Two-month digests that keep circling the same theme: get your data out of Drip and into your own stack.
The forms plugin just opened its data to AI agents through an MCP adapter.
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
Three release lines running in parallel, all of them shipping nothing but fixes this week
OpnForm is turning its V2 platform into an automation surface, one integration at a time.
Zoho Social opens its management surface to AI assistants via MCP.
See all MailerLite alternatives → · See all Pushwoosh alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Pushwoosh is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pushwoosh is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Mkt Auto products to evaluate alongside.
Top MailerLite alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "MailerLite alternatives" section above for the current picks, or visit /alternatives/mailerlite for the full list with editorial commentary on each.
Top Pushwoosh alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pushwoosh alternatives" section above for the current picks, or visit /alternatives/pushwoosh for the full list with editorial commentary on each.