beehiiv With Causality Engine: Do Verified Clicks Buy?

The short answer: the issue shows hundreds of Verified Clicks to the shop, and the shop's orders that day look like any other day's. beehiiv, the newsletter platform built around growth and monetisation, tags post links with UTM parameters by default and counts clicks with care; by default its Clicks Report covers posts scheduled in the last 30 days (Clicks Report). It documents no order or revenue figure for a store, so the fit is partial: beehiiv's number ends at the click. What the click sold is GA4's to record, and weighing the newsletter against ads and search is a job for Causality Engine, a causal attribution tool that reads GA4's export and gives its first finding 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.

Before the newsletter gets the credit:

1. Give the click count a second number. For example, 640 Verified Unique Clicks and 16 purchases that GA4 files under Email: 16 ÷ 640 = 2.5% of clickers bought, by last click. A click total on its own has no such partner.
2. Check a default you already have. Automatic UTM Tagging is on unless someone switched it off, under Settings, General Info, UTM Analytics (UTM tracking article).
3. Read one real link. Open a sent issue, click through to the shop and look at utm_medium in the address bar. The next section says why.

Who records what: beehiiv, GA4 and the read

What beehiiv writes on every post link

Per the UTM tracking article, updated on 13 August 2026 and marked for all plans, beehiiv sets three values without being asked. UTM Source is the publication's domain. UTM Medium is 'Email' for a reader in the inbox and 'Referral' for a reader on the web version. UTM Campaign is a URL-friendly form of the post title. You can overwrite all three in the UTM Analytics section, or switch the toggle off. UTM Term and UTM Content cannot be set there, and any utm_source, utm_medium or utm_campaign you type on a link yourself takes precedence.

Google files a session under Email when source or medium is email, and says its channel definitions are not case sensitive (default channel group). So 'Email' passes. Two things still deserve a look.

First, the article gives two answers. Its text says 'Email'; the sample link in its own FAQ carries utm_medium=newsletter. Google has no Email rule for newsletter, and a visit that matches no rule becomes Unassigned. That is why step 3 above asks you to read a real link.

Second, one issue lands in two GA4 rows. Inbox readers arrive as Email and web readers as Referral, so the Email row alone undercounts the newsletter.

Verified Clicks: the result beehiiv reports

beehiiv filters its click counts. The Verified Clicks article describes checks on IP addresses, user agents and click patterns, and flags several clicks within seconds of an open as likely bots. Each post then shows four figures: Total Clicks, Verified Total Clicks, Unique Clicks and Verified Unique Clicks.

On paid plans, from $49 a month on yearly billing at 1,000 subscribers (pricing, checked on 11 November 2026), the Clicks Report adds a URL Contains filter. Type the shop's domain and it totals the Verified Clicks sent there.

The same article states beehiiv's position plainly: the Clicks Report "should be considered the central source of truth for campaign performance". It also lists why a tool such as Google Analytics shows fewer: the reader leaves before the tracker fires, platforms define clicks differently, and ad blockers stop third-party tags.

What is not documented: orders. The integrations page says the WooCommerce integration syncs new customers into a publication, and nothing on it sends orders back.

The claim gap, as a worked example

For example, in figures made up for the sum and belonging to no real shop: a tea shop mails its weekly issue and books 240 orders in the seven days after.

Start with clicks: 900 - 760 = 140 never became a session, for the reasons beehiiv lists. Then orders: 27 + 131 + 112 = 270 claimed against 240 booked, so 270 - 240 = 30 are counted twice. The owner's 27 and GA4's 19 differ by 8.

A causal read adds no fourth claim to this pile. As how it works puts it, the read separates what each channel caused from what it only touched, sets that beside last-click rebuilt out of the same export, and attaches a data-health score from 0 to 100 and a next step to every channel. Should it rate Email well above 19, that is a reason to test the newsletter, not yet to double it.

beehiiv also runs an ad network, and the article that names the Clicks Report the source of truth recommends that network as the cure for mismatched counts. The party counting the clicks is the party selling them.

Where a store gets nothing from this pairing

• The newsletter is the product. With no shop and no purchase key event in GA4, the read has nothing to work on. Paid subscriptions and ad earnings are reported inside beehiiv.
• Short history. The start page asks for an export of 12 months or more.
• A small list. A channel under 1% of credit on both methods is called too small to act on (what causal attribution costs), and the home page says the product declines where spend is too small for a signal.
• Link-level questions. Which link in which issue drew the clicks is beehiiv's answer to give.

Free first: leave a segment out of the offer

beehiiv documents the exclusion on every plan. The Audience page of the post flow has an Include and exclude segments toggle that takes up to 5 segments (Audience page guide), and a Manual segment is a list you upload (segments guide). Pick a random tenth in a spreadsheet, upload it as Holdout, exclude it from the issue with the offer, and send that segment a duplicate without the offer. On Enterprise, Limit send size draws the random sample for you (random cohort guide).

For example, 7,200 readers who saw the offer include 144 buyers and 800 who did not include 12: 144 ÷ 7,200 = 2.0% against 12 ÷ 800 = 1.5%. The offer added (2.0% - 1.5%) × 7,200 = 36 orders.

The A/B test is a different tool: up to four subject lines on 10% of the audience by default, and every reader still gets the issue (A/B test guide).

The holdout is free and complete in itself. To place the newsletter among paid channels, pull the Attribution paths CSV from GA4 and try the free first finding on the start page, which runs in the browser without uploading the file. Causality Engine, which I founded, offers the full read at €99, one time, VAT not included, with money back within 30 days (pricing, checked on 11 November 2026).

See also

• beehiiv: plans, growth tools and reader complaints
• How to use beehiiv: growing a list with referrals
• beehiiv on the marketplace: beehiiv's affiliate program terms
• Causality Engine: definition, pricing and where it declines
• How to use Causality Engine: the whole job, step by step
• Causality Engine on the marketplace: the program's affiliate terms
• beehiiv vs Mailchimp: a newsletter platform against a store's email tool
• Email marketing ROI calculator: turn orders and costs into a return

FAQ

Can Causality Engine read a beehiiv publication?

No. It has no access to beehiiv and asks for none. Its integrations page says the product reads every channel a GA4 export records, so the newsletter is seen only through the visits GA4 logged from tagged links.

Why does GA4 show fewer visits than the Clicks Report shows clicks?

beehiiv's Clicks Report article gives three reasons: readers who bounce before the tracker fires, different definitions of a click, and ad blockers or privacy settings.

Will beehiiv traffic show as Email in GA4?

Inbox readers will if the link's medium is email, which the UTM tracking article gives as the default. Web readers are tagged Referral. If a link carries newsletter as its medium, expect Unassigned, and change the Medium field in UTM Analytics to email.