Hello Bar With Causality Engine: From Signups to Sales

The short answer: Hello Bar will tell you how many people signed up. It will not tell you whether they bought, and nothing in its help centre claims to. Hello Bar, the bar and popup builder for blogs and small shops, reports views, calls and emails collected on its Summary tab (performance guide), and its A/B test hands 90% of views to the leading version once each has 1,000 (A/B article). So this is a partial fit: no revenue claim to audit, and a sales question nobody has answered yet. The bar's value, if any, turns up later in other channels, mostly email. Causality Engine reads those channels from a GA4 export, with a free first finding 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.

What to know before calling the bar a sales tool:

• Do the conversion sum first. For example, 1,152 emails from 96,000 views is a conversion rate of 1,152 ÷ 96,000 = 1.2%. That is a signup rate. It says nothing about orders.
• Follow the addresses. Hello Bar sends no email of its own; addresses leave through an integration, a webhook, Zapier or a CSV (export guide). Whatever they buy later is credited to the email tool and to GA4's Email row.
• Plan a comparison the product does not run. No version of the A/B test shows nothing, so a by-hand on and off schedule is the only way to see what the bar itself is worth.

Hello Bar and the read in one table

What Hello Bar calls a conversion

The performance guide describes two places to look. The Summary tab tiles show views, calls, emails collected and the rest over a date range you choose, with a Download button for an Excel file. The graph icon beside each popup in Manage opens that popup's own figures. A conversion is the goal the popup was built for: an email entered, a call placed, a click.

The A/B test decides by that same conversion. Two popups of the same type on the same page form a test, each new IP address sees one version, and after 1,000 views apiece the better converter is shown on 90% of views and a random one on the other 10%. Edit anything beyond content, colours and timing and the pair stops counting as a test (A/B article). Hello Bar's A/B testing page presents the shifting as the point: more visitors see the winner before you have declared one.

That is a sensible design for signups. Every arm shows a popup, though, so the test can rank two bars and never say whether a bar beats no bar.

Getting Hello Bar's events into GA4

GA4 sees a bar only if you send it. The GA4 guide, last modified in January 2023, goes through Google Tag Manager:

1. Create a GA4 Event tag, named something like "HelloBarEvent to GA4", on your existing GA4 configuration.
2. Add a Custom Event trigger on the event name HelloBarEvent.
3. Add an Action parameter and a Label parameter, each read from a Data Layer Variable. Action carries views and conversions; Label carries the popup or bar ID.

Those events land inside visits that already have a source. Google files each session by source and medium under the rules on its default channel group page, so a reader who came from Organic Search and signed up in a modal is still an Organic Search session. There is no Hello Bar channel, and there should not be.

The signup's later effect has a channel, though. When the welcome email goes out with a medium of email, the click that brings the subscriber back is filed under Email. Untagged, it can land in Direct: Google's (direct) / (none) page names links without UTM parameters as a cause.

A worked example: one bar, eight weeks, two schedules

For example, with made-up figures that belong to no shop: a coffee roaster runs a signup bar on every page. In a month it logs 96,000 views and 1,152 emails, the 1.2% from the list above. In GA4 the HelloBarEvent conversions match: 1,152.

How many orders did the bar cause? Hello Bar's report has no answer, so the roaster switches the bar on and off by week for eight weeks, on, off, on, off, to spread paydays and promotions across both sides. The four weeks on bring 52,000 sessions and 1,404 orders, an order rate of 1,404 ÷ 52,000 = 2.70%. The four weeks off bring 52,000 sessions and 1,326 orders, or 2.55%. The difference is 1,404 - 1,326 = 78 orders over four weeks.

Those 78 orders do not appear under any bar. Some show in GA4's Email row, from subscribers who clicked a welcome email; some sit in Direct. A causal read of the export splits Direct back to the channels that sent those buyers and sets Email's caused share next to its last-click figure, per the how-it-works page, with a data-health score and a next step. If the read rates Email well above last-click, the bar that feeds the list is part of why, and a held-out week is still the way to confirm it before budget moves.

The free check, by hand

Hello Bar documents no control group, so this is by hand and says so:

• Pick whole weeks and alternate them, at least four of each.
• Switch the bar off in Manage, not by removing the snippet, so nothing else changes.
• Take sessions and purchases per week from GA4's Traffic acquisition report and compare order rates, as in the example.
• Do not compare buyers who triggered a HelloBarEvent conversion with buyers who did not. They chose to sign up, and that choice already separated them.

A week-by-week comparison is weaker than a random split, since weeks differ in ways a split would cancel out. Alternating them is what makes it usable.

For every channel at once, drop the GA4 Attribution paths CSV on the start page; the first finding is free and stays in your browser. Causality Engine, which I founded, sells the full read of that file for €99 once, excluding VAT, refundable within 30 days (pricing, checked on 11 November 2026).

Where this pairing ends

• The read cannot see a bar, a modal or a headline. It reads channels.
• It wants 12 months or more of GA4 data (how it works) and declines when spend is too small for a signal (homepage).
• A small list can fall below the floor: a channel under 1% of credit on both methods is called too small to act on (pricing for agents).

Hello Bar sells its plans by popup views, 50,000 a month on Growth (pricing page, checked on 11 November 2026), and its A/B test has no arm that shows nothing, so every visitor in a test is a billed view and the one comparison that could find a bar not worth its views is the one the product never runs.

See also

• Hello Bar: its plans, views and A/B testing
• How to use Hello Bar: building an email list from blog traffic
• Hello Bar on the marketplace: Hello Bar's affiliate program terms
• Causality Engine: the product, its prices and its limits
• How to use Causality Engine: a GA4 file to a budget decision
• Causality Engine on the marketplace: its affiliate terms, from the owner
• Hello Bar vs OptinMonster: view billing against impression billing
• Email marketing ROI calculator: what a list earns, on your inputs

FAQ

Can Hello Bar pass its signups to Causality Engine?

No. The two never connect. Causality Engine reads the channels in a GA4 export (integrations page), so a bar shows up only through what its subscribers do later, in rows such as Email.

Does Hello Bar report revenue from a popup?

Not in the help centre. The performance guide covers views, calls and emails collected; an order total is not among them.

Is Hello Bar's A/B winner a proof that the bar sells?

No. It shows which of two popups converts better on its goal, and keeps showing the leader to 90% of views (A/B article). Whether either beats no popup needs the on and off schedule above.