These cookies are essential for the website to function properly. They enable core functionality such as security, shopping cart, and account access. You cannot disable these cookies.
These cookies enable enhanced functionality and personalization, such as remembering your language preference or region. If you do not allow these cookies, some features may not work properly.
These cookies help us understand how visitors interact with the website by collecting and reporting information anonymously. This helps us improve our website.
These cookies are used to deliver advertisements that are relevant to you based on your interests. They also help measure the effectiveness of advertising campaigns.
Omnisend Integration sends PrestaShop visits, viewed products, cart changes and orders to your Omnisend account. Installation, one Brand ID from your account and an enable switch complete setup.
Omnisend handles email, text message and web push marketing, including welcome, abandoned-cart and post-purchase flows. A free plan covers the start; paid plans begin around sixteen dollars monthly and grow with your contact list. The module works with every plan.
You control the connection through the identifier and switch; nothing is sent while either is missing or disabled. Signed-in customers are recognised by account email, and the connection loads after the shop page without theme edits.
Your marketing segments use the products customers actually viewed and bought, with browsing linked to the recognised customer's profile.
Omnisend Integration feeds your Omnisend account with what really happens in the shop. Six features connect shop activity with your marketing:
Every page visit is reported, and the report carries substance: which product was viewed, what entered or left the cart, and which orders were placed. Omnisend receives the events its automations and segments are built on, straight from the storefront.
Identity travels with the events. A signed-in customer is recognised by the account email on every page, so the browsing session attaches to the contact Omnisend already knows instead of remaining an anonymous visit.
Omnisend is a marketing platform made for online stores: email campaigns in a drag-and-drop editor, text messages, web push notifications, signup forms and popups, audience segments and clear reports. Its ready-made automations cover the classics, welcome series, abandoned cart recovery, order confirmations and win-back messages.
A free plan covers the start, and paid plans begin around sixteen dollars a month, growing with the contact list. The module works with every plan, the free one included.
Abandoned cart recovery fires because Omnisend sees the cart being filled and then left. Post-purchase flows fire because the order arrived with its contents. Win-back campaigns find the customers who stopped coming, and segments are drawn from what people genuinely viewed and bought.
A recovery message can bring an abandoned cart back as an order, and campaigns can target audiences defined by real behaviour.
The Omnisend connection loads after the rest of the page, so product photos, prices and the buy button never wait for it. Customers on slow connections see your shop first.
The module is silent until it is complete. With no identifier, or with the switch off, the storefront carries nothing of Omnisend at all: a half-finished setup never leaks a broken tracker into the shop.
Installation, then one field: the Brand ID copied from your Omnisend profile under organization settings, then the switch. From that moment the storefront reports to Omnisend on every page.
Until then, a readiness notice in the back office names exactly which setting is missing, so there is never a doubt about why tracking has not started, and never a theme edit or template change on the way there.
Be the first to share your experience with this product.
Connect your PrestaShop store to Omnisend by adding Omnisend's onsite tracking snippet without editing your theme. Once enabled, the module sends page-view tracking and identifies logged-in customers by email, so your Omnisend campaigns can use real storefront activity.
The module declares ps_versions_compliancy from 1.6.0.0 up to the running PrestaShop version, and its header documents PS 1.6 through 9.x. composer.json requires PHP 7.2 or newer. It only registers the displayHeader hook, so it does not rely on front-controller APIs that changed between major versions.
The module remains installed, but hookDisplayHeader() returns nothing because isActive() requires the Brand ID. The required-configuration notice also tells staff that tracking is inactive until the Brand ID is added.
The configuration class stores only two functional settings: Enable Omnisend and Brand ID. The module's active check requires both the enable flag and a non-empty Brand ID.
No. In the files read for this rollout, the module's storefront template sends page view and optional email identification only. It does not contain PrestaShop hooks or JavaScript for add-to-cart, checkout, or purchase events.
On every storefront page the header pushes a $pageViewed event to the omnisend queue and loads Omnisend's external launcher-v2.js from omnisnippet1.com. When a customer is logged in, hookDisplayHeader() additionally passes that customer's email in an identify call; guests send no email. No cart, order, or payment data is sent by the module. Because a logged-in email leaves your store for a third party, you remain responsible for the appropriate consent and privacy disclosure.
Yes. The module registers displayHeader and renders its own Smarty template, while the admin controller saves the enable switch and Brand ID through the shared configuration table.
When enabled with a Brand ID, it renders a header script that sets the Omnisend account ID, tracks $pageViewed, identifies the logged-in customer's email when available, and loads https://omnisnippet1.com/inshop/launcher-v2.js asynchronously.
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
A store using Omnisend Integration tracks page views and identifies logged-in shoppers so Omnisend workflows have clearer storefront behaviour to work with. That handles the messaging layer, but those workflows are most effective when there is real on-site content worth bringing shoppers back to.
Blog Revolution covers that with a native place for buying guides, announcements and advice, keeping articles, categories, tags, authors, comments, ratings, RSS and clean blog pages inside the shop. It produces on-site content, entirely separate from the Omnisend integration.
Running both, your store builds durable articles that attract and inform visitors while Omnisend associates known browsing with profiles independently. The blog gives your workflows substantial on-site material to point readers toward, and the two operate as separate tools, one creating content and the other connecting storefront behaviour to Omnisend.
A store running Omnisend Integration relies on clean storefront behaviour, since identifying logged-in shoppers and tracking page views is only as useful as the activity behind it. Omnisend connects the behaviour, but it does not reduce bot submissions and spam in the forms that feed it.
reCAPTCHA & hCaptcha Protection covers that by reducing spam messages and bot submissions on contact, registration, login and newsletter forms, supporting reCAPTCHA v2, v3 and hCaptcha. It filters bot noise at submission, a separate concern from the Omnisend connection.
Running both, your storefront forms see fewer bot submissions while Omnisend works from cleaner activity. The protection module reduces spam and automated submissions on the forms, so the profiles and behaviour you act on through Omnisend carry less bot noise than unprotected forms would produce.
With Omnisend Integration, a store identifies logged-in shoppers and tracks page views so workflows reflect real browsing. That supports off-site re-engagement, but it does not provide the on-page trust signal that helps a hesitant shopper decide to buy: how reviewers rated the product.
Reviews & Ratings covers that with native ratings, written feedback, optional photo reviews and review criteria for products, categories, CMS pages and the store itself, all moderated inside PrestaShop. It owns moderated customer feedback, a separate concern from the Omnisend connection.
Running both, reviews help convert shoppers on-site while Omnisend re-engages those who leave through profile-based workflows. The two operate independently, one building trust at the decision point and the other handling follow-up afterwards, so your store strengthens both conversion and retention without either tool relying on the other.
30 days return right
Plug & Play Modules
Dedicated Support First
Built and maintained by David Miller and mypresta.rocks. David Miller has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.
