Moosend With Causality Engine: What Campaign Revenue Means

The short answer: if Moosend's revenue widgets and the shop's order total tell different stories, begin with the rule, because Moosend publishes less of it than most. Its revenue tracking article says the Track your campaign revenue option appends a campaign ID, cmid, to every tracked link. Neither that article nor the dashboard pages state how long that click keeps earning. The same send can carry 3 UTM parameters, so GA4 keeps a second count of its own. Set both beside the order total, hold a fifth of one segment back, then take the GA4 export to Causality Engine, where a first finding is free at app.causalityengine.ai/start.

Disclosure: I founded Causality Engine and own it, and this page recommends it. Every claim about it links to Causality Engine's own pages.

Moosend is an email marketing and automation platform with website tracking built in. Causality Engine is a product that reads a GA4 export and works out what each marketing channel caused. There is no integration between them. Causality Engine's integrations page gives pages to eight platforms, Moosend not among them, and adds that the product works with every channel visible in the GA4 data, email included. For Moosend, that visibility depends on one switch per campaign.

Rule of thumb before a revenue widget is quoted:

• Count the campaigns that were switched on. Revenue tracking is set campaign by campaign. For example, if 6 of last month's 9 campaigns had it set to Yes, the widget covers 6 ÷ 9 = 67% of sends, and the other 3 earned nothing on Moosend's books however they sold.
• Start from the tracking you installed. Per Moosend's main dashboard article, website revenue appears only with website tracking in place, and campaign revenue only with the option enabled.
• Look for newsletter / email in GA4. That pair is what Moosend's UTMs write, and it is the row to compare.

Moosend's side and GA4's side

What Moosend's campaign revenue is made of

Two things have to be true before Moosend shows campaign revenue. The site must run Moosend's website tracking, which the website tracking article describes as cookie-based and able to record page visits, product views, carts and purchases with quantity and price. And the campaign must have Track your campaign revenue enabled on its Set basic settings page, where the campaign guide describes it as tracking the campaign's views and orders.

With both in place, every tracked link gains the campaign's ID, and orders that follow are reported against it. They surface in the main dashboard's Revenue area, in widgets such as Revenue by Campaign Type, and in custom report widgets such as Campaign Revenue by Date, listed in the widget reference.

What these pages leave out matters as much. They give no number of days between click and order, and do not say which campaign keeps an order when a subscriber clicked two. So the rule in practice is: a click carrying a cmid, then an order the tracker saw, with the time limit unknown.

One caution is documented. The installation guide says an order completed event is tracked accurately only if an added-to-order event for the same product was recorded first.

Putting Moosend traffic in GA4's Email row

The neighbouring option on the same settings page is Track your campaign with Google Analytics. Set to Yes, it adds utm_source=newsletter, utm_medium=email and utm_campaign with the campaign's name, per the Google Analytics article. Transactional campaigns get utm_source=transactional. For a campaign already built, the toggle is under Set basic settings.

Google's default channel group needs nothing more: a medium of email is enough for the Email channel. The source, though, says newsletter, not Moosend, so any other tool that tags its links the same way lands in the same GA4 row.

The revenue article carries a warning: if the destination site cannot handle URL parameters, the added cmid can break the redirect. Click a test email through to the shop before a full send.

A holdout Moosend does not offer, built by hand

Moosend's A/B campaign sends the winning version to everyone outside the test groups, so nobody is left unmailed. Its segments can fetch a Max % of matching recipients, but the segments article does not call that pick random. So do the random part yourself. Add a custom field named Holdout, fill it for one subscriber in five from a shuffled spreadsheet, and send the campaign to a segment built on that field that leaves them out.

For example, 10,500 subscribers split into 2,100 held back and 8,400 mailed, four to one. Two weeks later the order export shows 372 orders from mailed addresses and 81 from held-back ones. With no campaign the mailed group would have ordered about 81 x 4 = 324 times. The campaign caused 372 - 324 = 48 orders, and no tool is needed for that answer.

A worked example: the same fortnight in three systems

For example, using made-up numbers with the working shown:

• Order export: 642 orders averaging $54, 642 x 54 = $34,668.
• Moosend, orders tied to a cmid: 219, worth 219 x 54 = $11,826.
• GA4, newsletter / email, Paid and organic last click: 126 orders, 126 x 54 = $6,804.
• TikTok Ads Manager claims 148 purchases and Google Ads 301.

The claims sum to 219 + 148 + 301 = 668, so 668 - 642 = 26 orders have more than one owner. Email's two readings differ by 219 - 126 = 93 orders, 93 x 54 = $5,022. GA4 gave those 93 to whichever tagged channel the buyer clicked last. Moosend kept them because an earlier click carried its ID.

Which is nearer the truth is a causal question, and this page invents no answer to it. A Causality Engine read, per its how-it-works page, lays out each channel's share of credit after Direct is split back, the last-click share from the same file, a data-health score from 0 to 100, and a next step to raise, cut or hold. If that read and Moosend's widget point in opposite directions, rerun the holdout above on the segment in question before the budget follows either.

Where Causality Engine adds nothing, and where it does

It adds nothing without history: the start page calls for 12 months or more, built on your purchase key event. It adds nothing below a threshold, since how it works labels a channel under 1% of credit on both methods too small to act on. And it cannot tell one campaign from another. Moosend's campaign widgets do that; the read treats Email as a single channel.

Remember who built the first screen. Moosend sells plans by number of contacts, per its pricing page, and its main dashboard sets purchases from the whole website beside purchases from campaigns, with no published window between them. A dashboard like that keeps a contact-based bill looking small.

Where the read does help is the budget split across channels. Causality Engine, which I founded, shows the channels behind Direct for free on the start page, and the full read is a single €99 payment that can be refunded for 30 days (pricing, checked on 11 November 2026).

See also

• Moosend: pricing by subscribers and who it suits
• How to use Moosend: winning back or dropping inactive subscribers
• Moosend's affiliate program terms
• Causality Engine: method, price and where it declines
• How to use Causality Engine: reading each channel's four fields
• Causality Engine's affiliate program terms
• How to measure email incrementality: the holdout method in more depth

FAQ

Does Moosend send its revenue data to Causality Engine?

No. Nothing passes between the two products. Causality Engine works from a CSV exported out of GA4, in which Moosend's sends are visible only as tagged Email traffic.

How many days after a click does Moosend credit an order?

The user guide pages on revenue tracking and Google Analytics give no figure. Ask Moosend's support, and write the answer down next to your reports.

Why is my Moosend traffic called newsletter in GA4?

Because that is the utm_source Moosend adds, with email as the medium, per its Google Analytics article.