esc
Get started

Hyvä + Pulse support

Hyvä stores get the full feature set with no compatibility module, because Pulse, the extension's customer-journey engine, lives inside Magento rather than in the storefront theme.

Hyvä logo Pulse mark

Most Magento extensions meet Hyvä through a compatibility module. This one does not need one, and Pulse is the reason: the customer-journey work happens inside Magento, and the little JavaScript that does reach the storefront carries no dependencies. There is nothing for a new frontend to break, so a Hyvä store runs the same build as everyone else.

Hyvä: supported natively

The extension supports Hyvä natively. No compatibility module, no Luma fallback, no extra setup. The storefront pieces (the Mailchimp Pixel and guest email capture) are dependency-free JavaScript, so they run as-is on Luma, on Hyvä themes and on Hyvä Checkout, including its dynamic checkout steps.

Admin pages are independent of your storefront theme; the admin always runs Magento’s standard theme.

Pulse: the customer-journey engine

Pulse is ebizmarts’ customer-journey engine for Magento, a separate install that pairs with the extension. Lean by design, it records what happens in your store, in your own database, and prepares that activity for the Mailchimp sync to send on.

The clever part is identity resolution: the moment a shopper types an email at checkout or in a newsletter form, or logs in, Pulse connects their cart and their browsing to that email, including what they did before identifying themselves. That is how a guest’s abandoned cart reaches Mailchimp ready to recover, with no account and no completed checkout needed.

Pulse makes no external calls of its own; data only leaves your store when the Mailchimp sync sends it. Email us for the install directions. Install order does not matter; add Pulse whenever you like.

What works without Pulse

Pulse is optional. Catalog, customer, subscriber, cart and order sync all work without it. What stops is the shopper-journey layer: behavioral events feeding Customer Journeys, guest email capture, landing-page attribution and journey narration. Campaign attribution stays: the extension reads Mailchimp’s own attribution verdict from the order sync response, so attributed orders, the Recovered flag, the dashboard revenue and the campaign report all keep working, and only the campaign’s arrival on the shopper’s timeline stops.

Questions along the way? Troubleshooting has the answers, and ebizmarts support is one email away.

Next: Composer installation directionsThe Composer package, the authentication token and the step-by-step directions to install the extension.