Pimcore
A security-hardening train: nine advisories across six patch releases, no feature work in sight.
A side-by-side editorial comparison of Omnisend and Pushwoosh — release velocity, themes, recent moves, and the top alternatives to consider.
Omnisend is quietly rebuilding itself around the agencies that run its stores.
Omnisend remains an ecommerce email and SMS automation platform, but the visible work has shifted to the Partner Portal: templated accounts, access management, and workflow copying across accounts. Alongside that, segmentation gained Total Spent and AOV filters, and a Blotout EdgeTag integration adds server-side event capture for automations that browser pixels miss. The core campaign builder is stable; the surrounding operator layer is where the changes are landing.
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.
Omnisend remains an ecommerce email and SMS automation platform, but the visible work has shifted to the Partner Portal: templated accounts, access management, and workflow copying across accounts. Alongside that, segmentation gained Total Spent and AOV filters, and a Blotout EdgeTag integration adds server-side event capture for automations that browser pixels miss. The core campaign builder is stable; the surrounding operator layer is where the changes are landing.
The Partner Portal releases stack into a coherent argument: build once, replicate across client stores. Templated accounts, cross-account workflow copying, and per-member access control are the three pieces an agency needs to run dozens of merchants without rebuilding each one. Read together, Omnisend is moving from a single-store SMB tool toward a platform operated on behalf of merchants rather than by them.
Expect the agency layer to keep filling in — cross-client reporting or billing roll-ups are the obvious gaps once templating and access control exist. The segmentation and tracking work suggests a parallel push on data fidelity, but the entries don't yet show which of the two gets priority.
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 Omnisend or Pushwoosh.
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.
AWeber is moving the console out of the browser and into the chat window
Building an agent-drivable outreach stack — MCP, then OpenClaw, now an in-dashboard AI copilot.
See all Omnisend 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 0.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 0.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 Omnisend alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Omnisend alternatives" section above for the current picks, or visit /alternatives/omnisend 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.