EmailOctopus With Causality Engine: From Clicks to Orders

The short answer: Tuesday's issue shows hundreds of clicks in EmailOctopus and GA4 shows almost no Email revenue for the week. Before the newsletter takes the blame, look at one toggle. EmailOctopus, an email-only newsletter platform, reports opens and clicks and stops there: its report article lists no orders and no revenue. It also tags links for GA4 only when Google Analytics link tracking is switched on, and its pricing page keeps free-plan reports for 30 days. So this tool never overclaims a sale. The risk runs the other way: untagged clicks get filed under Direct and email looks smaller than it is. Switch the tagging on, hold one tagged group out, and let Causality Engine, a causal attribution tool that reads a GA4 export, show what Direct is hiding. The 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.

Line these up before you judge an issue:

1. Turn clicks into a rate you can check. For example, an issue with 420 unique clicks, followed by 21 purchases in GA4's Email row, gives 21 ÷ 420 = 5 orders per 100 clicks. EmailOctopus supplies the 420. Only GA4 can supply the 21.
2. Collect what exists already. The campaign report with clicks per link, GA4's purchase event, and the shop's order export with email addresses.
3. Decide what proves it. Orders per 1,000 subscribers among people who got the issues against people who did not.

What EmailOctopus counts, and what it leaves alone

Tracking is on by default for every campaign and automated email, and it follows two things, opens and clicks, per the campaign tracking article. The report built from it lists who opened, who clicked, who clicked which link, unsubscribes, bounces, complaints, and the people who did neither. For each link you get unique and total clicks, with an export (link report article).

Two cautions come from EmailOctopus itself. Apple Mail pre-fetches the tracking pixel, so the open rate is, in the tracking article's words, not the most reliable metric. And links that carry merge tags or custom fields in the URL are not click-tracked at all.

What is absent matters as much. There is no attribution window, no credited order, no revenue per campaign. The help centre says there is no native Shopify integration; a third-party app, Zapier or Make can sync customers in (Shopify article). That moves contact data into the list. It does not put sales into the report.

EmailOctopus and the GA4 read at a glance

Switching on Google Analytics link tracking

The setting sits in the campaign's Advanced settings panel. Toggle it on and EmailOctopus adds three parameters to each link: utm_source emailoctopus, utm_medium email, and utm_campaign set to the campaign's name (tracking article). Parameters you typed on a link yourself are left alone and take precedence. Google's channel definitions file a session under Email when the medium or the source is email, so the automatic medium is the part that counts.

Mistakes the vendor's own pages point at:

• Leaving it off. EmailOctopus's UTM guide says that without UTMs Google Analytics classes most email traffic as direct.
• Careless campaign names. The name becomes utm_campaign. The same guide notes values are case-sensitive and advises lowercase with underscores or hyphens instead of spaces.
• Expecting to edit the defaults. The automatic values cannot be customised; you override them link by link.

The help article does not say whether the toggle carries over to the next campaign or to automated emails. Click a link in a test send and read the address bar.

A worked example: 1,680 clicks and nobody claiming them

For example, as an illustration with made-up figures and no real shop behind it. In a month of four issues to 6,000 subscribers, EmailOctopus reports 1,680 unique clicks. The shop books 310 orders. Meta claims 150 of them and Google Ads 190. GA4's last-click view gives Email 9 and Direct 96. Link tracking was off for the first two issues.

• Claims by tools that credit sales: 0 + 150 + 190 = 340, which is 340 ÷ 310 = 1.10 per booked order.
• EmailOctopus's claim: 0 orders, by design.
• Email in GA4: 9 ÷ 310 = 2.9% of orders. Direct: 96 ÷ 310 = 31.0%.

Here the claim gap is inverted. Two ad platforms claim more than the shop sold, the newsletter claims nothing, and GA4's Email row is a floor, since two issues' worth of clicks went in untagged. How many of Direct's 96 began with an issue? No report above can say.

That is the first thing the read addresses. Causality Engine's start page describes the free finding as the channels that sent the buyers last click files under Direct. The full read then shows Email's caused share next to a last-click rebuild from the same file, a data-health score from 0 to 100, and a next step (how it works). If it puts Email far above 2.9%, do not double the sending frequency on that alone. Run the holdout below first.

Limits on both sides

The read needs a purchase key event in GA4 and 12 months or more of paths. Its one-off read page says not to buy when analytics history is thin or broken, and that a channel under 1% of credit on both methods is called too small to act on. A young newsletter can land there, and that is an answer too. The read also works per channel. Who clicked which link in which issue is EmailOctopus's ground, and nothing in GA4 replaces it.

One fact about defaults. EmailOctopus bills by subscriber count (pricing page) and tracks opens and clicks in every campaign from the first send, while the tag that lets GA4 judge those clicks waits behind a toggle in Advanced settings. The default report grows with the list you pay for. The figure that could show an issue sold nothing appears only when you ask for it.

A holdout by tag, then the read

EmailOctopus's segmentation article lists no random-sample condition, so this one is by hand, built from two documented pieces. In a spreadsheet, mark a random tenth of the list with a tag such as holdout; the import article lets a column carry tags. When you send, open the campaign's Advanced tab and add a Tags condition for contacts without that tag, as the segmentation article describes.

After four issues, match both groups to the order export. For example, 5,400 mailed subscribers place 81 orders and 600 held-out subscribers place 6: 81 ÷ 5.4 = 15.0 per 1,000 against 6 ÷ 0.6 = 10.0. The issues added 5.0 orders per 1,000 mailed, 5.0 × 5.4 = 27 orders, three times the 9 in GA4's Email row. That result stands without any purchase.

For email next to the paid channels, take the next step: drop the paths export on the start page and take the free finding. If Direct turns out to be sitting on newsletter sales, Causality Engine, which I founded, does the full read for €99, paid once, VAT not included, and refunds it on request for 30 days (pricing, checked on 11 November 2026).

See also

• EmailOctopus: the entry, with plans and per-list billing
• How to use EmailOctopus: a double opt-in newsletter launch
• EmailOctopus in the marketplace: EmailOctopus's affiliate program terms
• Causality Engine: what the read is and costs
• How to use Causality Engine: six steps from export to test
• Causality Engine in the marketplace: terms for its affiliates
• How to find what Direct traffic is hiding: the GA4 side of this check
• EmailOctopus vs Mailchimp: store-connected flows against a low price

FAQ

Does EmailOctopus report revenue or orders?

No. Its report article lists opens, clicks, link clicks, unsubscribes, bounces and complaints. Order data lives in the shop and in GA4.

Do EmailOctopus and Causality Engine talk to each other?

They do not, and nothing needs installing on either side. Causality Engine's integrations page says it measures every channel visible in GA4 data, email included. The newsletter gets there as tagged sessions.

Is Google Analytics link tracking on by default?

The help article tells you to toggle it on in Advanced settings, so treat it as off until you have seen a tagged link.