AWeber With Causality Engine: What Sales Tracking Counts

The short answer: when AWeber's Sales tab and the shop's order list disagree, look at what AWeber counts before doubting either. Its sales tracking guide logs one sale for every hit on your order confirmation page from a browser carrying AWeber's cookie, prices each at the amount you typed in, and states no time limit. One click through an email sets the cookie; after that the visit counts wherever the buyer came from. AWeber's product update of 7 July 2026 also puts 3 UTM parameters on every email link by default, so GA4 holds a second opinion already. Causality Engine reads that GA4 data, and its 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.

AWeber is an email platform for creators and small businesses: lists, automations, landing pages. Causality Engine is a tool that takes a GA4 export and estimates which channels caused a shop's sales. Neither plugs into the other. Causality Engine's integrations page describes a product with no platform pixel and no connector, which measures whatever channels the GA4 data shows. AWeber enters that data through its link tags alone.

Three sums before the Sales tab is believed:

1. Multiply the typed value out. For example, with Monetary Value set to $45 and 141 hits on the order page, AWeber shows 141 x 45 = $6,345, whatever the baskets held. At a real average of $62 those orders were worth 141 x 62 = $8,742.
2. Check the page you already nominated. The guide wants a URL people reach only straight after ordering, because every hit is tracked as a sale.
3. Look for aweber / email in GA4. AWeber's product update points to Acquisition, Traffic acquisition, filtered by source and medium.

AWeber and Causality Engine in one table

AWeber tags every link for GA4 unless you switch it off

The July product update is specific. At send time AWeber adds utm_source=aweber, utm_medium=email and a utm_campaign equal to the email's subject line. It is on for every account. The switch is a UTM Tracking toggle on the List Settings page, per list, and it takes effect on the next send. Links that already carry UTM parameters are left alone.

That medium satisfies Google's default channel group, which files a session under Email when source or medium reads email. The subject line becomes the campaign name, so every send is its own campaign row.

One wrinkle. AWeber's older Google Analytics article still says there are no direct integrations, and teaches tagging by hand with a Campaign Source of "AWeber", capital A and W. Google's URL builder page says parameter values are case sensitive. Hand-tagged links left in an old automation sit under a second source beside the automatic lowercase one.

How AWeber decides a sale happened

Sales tracking has two steps. Install Email Web Analytics by pasting AWeber's code above the closing body tag of each page, from Reports, Tracking. Then, in the Sales Tracking section of that screen, enter a Goal Web Page URL, a description, the Event Type "Sale" and a Monetary Value in dollars.

From there the rule is the cookie. A subscriber receives it by first reaching the site through an email link. The guide is plain about what follows: once the cookie is there, a page visit is tracked regardless of where the subscriber came from. A buyer who clicked a newsletter and later returns from a search ad still reaches the goal page with the cookie, for as long as it lasts.

The broadcast stats guide describes the Sales tab as subscribers who made a purchase after clicking through that message. What neither page gives is a number of days, or which message keeps the sale when a subscriber clicked several. Treat both as undocumented. Unless someone sets the value dynamically, revenue is hits times a constant.

Worked example: a launch month in four counts

For example, with invented figures and every sum shown:

• Shop's order list: 318 orders, 318 x 62 = $19,716.
• AWeber's Sales tab: 141 goal-page hits, 141 x 45 = $6,345.
• GA4, source aweber, Paid and organic last click: 58 purchases, 58 x 62 = $3,596.
• Meta's ads report claims 97 purchases and Google Ads 104.

Stack the claims: 141 + 97 + 104 = 342, which is 342 - 318 = 24 more orders than the shop took. Inside email the spread is 141 - 58 = 83. Those 83 buyers held the cookie and bought from somewhere GA4 did not call email. AWeber's count runs high while its dollars run low, and the two errors do not cancel.

A Causality Engine read adds no fifth claim, and none is invented for this page. Its how-it-works page says the output is every channel next to last-click, with Direct handed back to the channels that sent those buyers, a data-health score from 0 to 100 and a next step. Where its Email share and AWeber's Sales tab pull apart, withhold email from a tagged group for one send before changing how often you mail.

A holdout by tag, before any purchase

AWeber's split testing guide divides a list with a slider, 10/10/80 in its example, but it is built to send every group a version. A holdout therefore takes handwork with documented parts. In a spreadsheet, mark one subscriber in eight at random. Re-import those rows, choosing to update existing subscribers, and apply a tag such as holdout at the tagging step of the import guide. Save a segment of everyone without the tag and schedule the broadcast to it, as the segment guide shows; saved segments need a paid plan.

For example, 8,400 subscribers give 1,050 tagged and 7,350 mailed, seven times as many. Three weeks on, the order list shows 259 orders from mailed addresses and 31 from tagged ones. Expected without the email: 31 x 7 = 217. Caused by it: 259 - 217 = 42. That answer is free and complete.

What the read cannot do for an AWeber list

It cannot work without GA4 purchases. The start page has you pick your purchase key event and export 12 months or more, so a seller whose checkout GA4 never records has no file to give it. It also declines when spend is too small for the model to find a signal, as its home page says. And it will not list buyers by name, which AWeber's Sales tab does.

The sales tracking guide fences the feature off from the Free plan, so the number arrives as a reason to pay, and a count with no stated expiry grows with every old click that later ends on the order page.

If email is one of several channels you fund, the read comes after the holdout. Causality Engine, which I founded, gives the first finding away on the start page and charges €99 for the full read, one payment with a 30-day refund (pricing, checked on 11 November 2026).

See also

• AWeber: features, plans and common complaints
• How to use AWeber: mailing new blog posts automatically
• AWeber's affiliate program terms
• Causality Engine: the entry, with prices and limits
• How to use Causality Engine: six steps from CSV to decision
• Causality Engine's affiliate program terms
• How to export GA4 data for attribution: checks on the CSV before upload

FAQ

Do AWeber and Causality Engine share any data?

No. There is no plug-in, API link or login between them. Causality Engine sees AWeber only as Email sessions inside a GA4 export you download yourself.

How long after a click does AWeber still count a sale?

The sales tracking guide gives no window. It ties the sale to a cookie set by an email click, so ask AWeber how long that cookie lasts.

Why does GA4 show two AWeber sources?

Automatic tags use lowercase aweber, while AWeber's older article suggests "AWeber" for hand-built links, and Google treats the two spellings as different values.