How the connection works
Moosend's help articles present WooCommerce as one of several website tracking plugins, next to Magento, OpenCart, ZenCart and CS-Cart. The plugin sends visitor behaviour to Moosend, and that behaviour powers segments, automations and product blocks. [1] [2]
On WordPress.org the plugin is called Moosend Website Connector. Its description covers page view tracking, add-to-cart and purchase tracking, custom events, cart abandonment segmentation and automated retargeting emails. It also says customers who purchase are synced with name, email address and details into a new list. As accessed on 2026-10-30, the page listed version 1.0.190, more than 1,000 active installations, and a warning that it had not been tested with the latest three major WordPress releases. [7]
That warning matters for a live shop. Test on a staging copy first and keep a rollback path.
Installation steps
Moosend's install steps start from a website already added to your Moosend account: [2]
- In Moosend, go to More, then Websites, and click your site's URL. The Connect your website page shows your domain and website ID. [2]
- Click Install connection script and pick the plugin that matches your platform. [2]
- In WordPress, go to Plugins, Add New, search for "Moosend website tracking" and click Install Now. Alternatively, download Moosend Website Connector and copy its folder to wp-content/plugins/mootracker/. [1]
- Click Activate, then Settings. Enter your Moosend website ID and click Save Changes. [1]
- If you use Google Tag Manager instead, Moosend documents pasting its JS tracking snippets into a Custom HTML tag that fires on All Pages. [1]
What the tracking records, and when it knows who someone is
Moosend says its website tracking uses proprietary, cookie-based technology to record page visits, product views, cart contents and purchase information such as quantity and price. The cookies store a browser-session ID, a browser ID, a website ID and feature flags. Moosend says it cannot uniquely identify a device. [3]
Tying those events to a person is a separate step that Moosend calls Identify, and it must happen before other events count toward automations. With the plugin, Moosend lists four ways a visitor becomes identified. [4]
- They reach your site through a link in your newsletter. [4]
- They submit a subscription form on your site. [4]
- They register an account. [4]
- They log in. [4]
| Tracked data | Where Moosend documents it | Gotcha |
|---|---|---|
| Page views | Plugin page and tracking overview [3] [7] | Anonymous until Identify fires [4] |
| Product views | Tracking overview [3] | Product data includes name, code, image, URL, price and category; only one category is kept per product [1] |
| Add to cart | Plugin page [7] | Moosend's tracking library needs an add-to-order event before a completed order is recorded for that product [2] |
| Purchases | Plugin page [7] | Product identifier is the WordPress post ID, not SKU [1] |
| Custom events | Plugin page and trigger list [5] [7] | Requires a small JavaScript snippet [7] |
The automation triggers WooCommerce tracking unlocks
Moosend groups these under website engagement triggers. Each one lets you choose whether it fires on every occurrence or only the first, and which connected website it watches. [5]
| Trigger | Typical use |
|---|---|
| When someone views any product / specific products | Browse abandonment and category interest tags [5] |
| When someone adds any product / specific products to their cart | Abandoned cart recipe [5] [6] |
| When someone purchases any product / specific products | Post-purchase thank-you, cross-sell or review request [5] |
| When someone browses any page / a specific page | Pricing-page or shipping-page follow-ups [5] |
| When someone exits any page / a specific page | Exit follow-ups [5] |
| When custom event is recorded | Anything your developer tracks with a snippet [5] |
Building the abandoned cart flow
Moosend ships an Abandoned cart recipe. Its walkthrough sets the trigger "When someone adds any product to their cart" to fire every time, waits 45 minutes, checks whether the person has not purchased a product in that window, and only then sends the email. Moosend says 45 to 60 minutes is probably the best wait, and advises allowing an extra 5 minutes beyond any timed IF/THEN step. [6]
Inside the email, a cart abandonment block fills itself with the product image, title, price, code, manufacturer, category and URL from the connected website. Moosend notes that 3 x 1/3 and 4 x 1/4 layouts cannot be used for these repeatable blocks. [8]
Worked example (hypothetical): a shopper clicks your Tuesday newsletter, which identifies them, adds a kettle to the cart and leaves. At about 50 minutes the filter finds no purchase and the reminder goes out with the kettle in the cart block. A different visitor who never clicked an email or logged in triggers nothing, because they were never identified. [4] [6]
Consent checklist before switching tracking on
Moosend's docs state that tracking is cookie-based and that Identify links browsing to an email address across sessions and devices. They also say both data collection and Identify can be switched on or off by the client. How you get consent is your responsibility, so settle it before launch. [3]
- List the Moosend cookies in your cookie policy, and describe the browser, session and website IDs Moosend says it stores. [3]
- If your consent banner blocks non-essential cookies until a visitor accepts, check that the Moosend script respects that choice. With Google Tag Manager, Moosend points to the tag's consent settings under Advanced Settings. [1]
- Tell subscribers in your privacy notice that clicking newsletter links links their browsing to their email address. [3] [4]
- Only email people who agreed to marketing. Moosend's acceptable use policy says registering for an event or completing a survey is not enough consent to receive email. [9]
- Make sure the checkout opt-in is not pre-ticked if you rely on it for consent.
Questions before you decide
Does the Moosend plugin import my WooCommerce customer list?
The plugin's WordPress.org page says that after a customer purchases, Moosend automatically syncs their name, email address and details into a new list. Moosend's docs describe the plugin mainly as website tracking, and they do not describe a bulk import of past customers.
Why does my Moosend abandoned cart automation not fire for some shoppers?
Moosend says a visitor must be identified before other events count toward automations. With the plugin, that happens when the person arrives from a newsletter link, submits a subscription form, registers an account or logs in.
Should I use SKUs in Moosend product triggers for WooCommerce?
No. Moosend's plugin documentation says the WooCommerce plugin uses the WordPress product post ID, not the SKU, as the product identifier, so purchase segments and automations must use those IDs.
How long should the abandoned cart wait be in Moosend?
Moosend's abandoned cart recipe starts with a 45-minute wait and its walkthrough calls 45 to 60 minutes probably the optimum. It also advises allowing an extra 5 minutes for timed IF/THEN steps to fire.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Moosend Docs: Install website tracking using a plugin Accessed 30 Oct 2026
- Moosend Docs: Install website tracking Accessed 30 Oct 2026
- Moosend Docs: Website tracking Accessed 30 Oct 2026
- Moosend Docs: Tracking the actions of a website visitor Accessed 30 Oct 2026
- Moosend Docs: Different types of triggers Accessed 30 Oct 2026
- Moosend Docs: Create an abandoned cart automation Accessed 30 Oct 2026
- WordPress.org: Moosend Website Connector plugin Accessed 30 Oct 2026
- Moosend Docs: Create dynamic content blocks Accessed 30 Oct 2026
- Moosend: Acceptable Use Policy (June 2025, PDF) Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.