GetResponse With Causality Engine: Is the Last Click Enough?

The short answer: GetResponse's Attributed revenue column, GA4's Email row and your paid orders are three counts of different things, so expect them to disagree. GetResponse, the email, automation and webinar platform (entry), assigns an order to the last message whose link the buyer clicked, for 5 days after the click by default, per its revenue attribution article. An open alone earns nothing. It is still last click among emails only, blind to the ad the same buyer clicked a day later. If your store syncs orders to GetResponse and records purchases in GA4, run a Splitter holdout first. Then take the GA4 Attribution paths export to the start page of Causality Engine (entry), which reads that file for what each channel caused. The first finding is free.

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

Check these before the monthly report goes out:

1. Count what is switched off. For example, 22 messages went out last month and 9 had Revenue attribution enabled. The column covers 9 / 22 = 41% of your sends, so email is under-reported before it is over-reported.
2. Know your plan. Revenue tracking is listed as not available on Starter and included from Marketer (plans article).
3. Open one sent newsletter's links. If the address bar shows no utm_medium=email after a click, GA4 never filed that send under Email.

Who records what, in order

Last Click, as GetResponse defines it

The revenue attribution article names the model itself: Newsletter Revenue Statistics uses Last Click. Four mechanics follow from it.

The window opens on a click, not on the send. A click two weeks after delivery starts a fresh window that day.

One window per store and recipient. A newer message with a newer click can overwrite the open one, and the order then belongs to that message.

Only paid orders count. The ecommerce reports article points to the order-status mapping under Tools, Ecommerce tools, Store settings.

And the feature is opt-in per message. You move the Revenue attribution slider and pick the store for a newsletter, an autoresponder or an automation message. The window length is a store setting: Tools, Ecommerce tools, Settings, Attribution window.

One thing deserves credit. Its Ecommerce report draws total revenue and attributed revenue as separate lines and states the attributed share. The vendor's own screen says email did not make every sale.

The Google Analytics switch

Tagging is a second switch. The integration article places it in the first stage of creating a message: an ON/OFF button. With it on, Source is set to getresponse and Medium to email on every link. List names show up as the campaign, and subject lines as the content. For other values, the Integrations tab has a Google Analytics form with Source, Medium, Term, Content and Campaign fields.

Leave Medium alone. Google's channel rules file a visit under Email when source or medium matches email, and under Unassigned when nothing matches.

Ecommerce campaigns such as abandoned cart and price drop emails have their own Google Analytics toggle under General settings (ecommerce campaigns article).

The mistakes the integration article warns about:

• With click tracking and Google Analytics both on, use the original link, without analytics parameters of your own, and keep it under 255 characters.
• If your server cannot process the parameters, the link ends in a 404.
• No spaces in the link, and no non-standard characters such as ą or ć in the subject.

GetResponse rules one thing out in writing: its revenue attribution cannot be connected to Google Analytics.

A worked example with the leftovers counted

For example, as an illustration with made-up numbers, not any store's results: 1,460 paid orders in a month. GetResponse attributes 212 to its messages. Meta claims 498 and Google Ads 571. GA4's last click gives Email 158, Organic Search 322 and Direct 289.

The three self-reported claims total 212 + 498 + 571 = 1,281. If all three were true and none overlapped, 1,460 - 1,281 = 179 orders would remain for everything else. GA4's last click puts 322 + 289 = 611 on organic search and direct alone. So at least 611 - 179 = 432 orders have two owners.

Email's own gap is small: 212 - 158 = 54 orders, where the buyer clicked an email and returned within 5 days by another route that GA4 credited. A click-only rule keeps that number down.

Small is not the same as settled. Both email figures are last-click rules, one inside GetResponse and one inside GA4, and neither estimates what the emails caused. Causality Engine's how-it-works page describes what its read sets beside them: each channel's caused share with Direct split back, a last-click rebuild from the same file, a data-health score from 0 to 100 and a next step. If that share and the 212 are far apart, test on a held-out group before the send calendar changes.

The Splitter as a free control group

GetResponse's Splitter filter divides contacts in an automation workflow at random between path A and path B, by percentages you set, and can include contacts already on the list. The article uses it to compare two journeys. Attach Send message actions to path A only and path B is a holdout: a by-hand use of a documented element. Under 100 contacts the split can be off by a couple of percent, the article says.

For example, 4,000 contacts on a 90/10 split: 3,600 receive a three-email promotion and 400 receive nothing. After 14 days the store shows 252 paid orders from the first group and 24 from the second, which is 70 per 1,000 against 60 per 1,000. The promotion caused about 3,600 x 10 / 1,000 = 36 orders. For one sequence that answer is enough.

What stays outside the read

Causality Engine does not integrate with GetResponse. Its integrations page describes reading the channels a GA4 export records, with no connector.

So it cannot rank your newsletters; it knows email as a channel. A webinar or funnel shows up only if it ends in a purchase GA4 recorded. GA4 logs purchase events while GetResponse counts orders with paid status, so their totals need not match. The read asks for a purchase key event and 12 months or more of history (start page), and the homepage says it declines when spend is too small for a signal.

Revenue tracking begins on Marketer, one plan above Starter (plans article), and the figure is computed where Google Analytics cannot reach it. The number that shows what email earned is part of what the higher plan sells, and the only place to read it is the tool being judged.

Then the export

If the Splitter result is clear, stop there. For the wider question of how email sits beside paid and organic, Causality Engine, which I founded, gives a free first finding in the browser on the start page. One full read costs €99 and is refundable within 30 days (pricing, checked on 11 November 2026).

See also

• GetResponse: plans, webinars and October 2026 prices
• How to use GetResponse: host a webinar, email the no-shows
• GetResponse on the marketplace: GetResponse's affiliate program terms
• Causality Engine: what it reads, costs and declines
• How to use Causality Engine: six steps from export to test
• Causality Engine on the marketplace: affiliate terms for the owner's product
• GetResponse vs Mailchimp: webinars and funnels in the plan
• How to export GA4 data for attribution: twelve months of attribution paths

FAQ

Does GetResponse count a sale after an open?

No. The Attribution window opens when the recipient clicks a link, and revenue goes to the last clicked message, per the revenue attribution article.

Can GetResponse send its attributed revenue to Causality Engine?

There is no route for it, and none is needed. GetResponse says its revenue attribution cannot be connected to Google Analytics, and Causality Engine takes only the CSV you export from GA4 (how it works).

Why is a message showing no attributed revenue at all?

Check its Tracking settings first. Revenue attribution is enabled per message with a slider, and a message sent with it off reports nothing, whatever it sold (automation revenue article).