Replo With Causality Engine: Which Revenue Rule, Which Channel

The short answer: the page rows in a Replo report add up to more than the Replo sites earned in total, and the ad platforms claim more again. The first is a definition, not a bug. Replo, an AI agent that builds and hosts store pages on a subdomain of your own domain, offers two revenue rules in Insights: Session revenue gives every page a visit touched the full purchase value, so its rows "cannot be added together", while Attributed revenue splits the purchase equally across eligible page views (Insights). Pick the rule before reading the report. Then, for which channel sent the buyers, Causality Engine, which reads a GA4 export and estimates what each channel caused, offers 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.

Before reading an Insights report:

1. Run one order through both rules. For example, a visit views an advertorial and a product page on Replo, then buys for $84. Session revenue puts $84 on each page, $168 across the rows; Attributed revenue puts $84 ÷ 2 = $42 on each.
2. Use the reports Replo already builds. The Overview breaks sessions down by referrer and by UTM source, and the analytics guide suggests cross-checking Replo's numbers against a connected GA4 property before acting on them.
3. Confirm both tags see the same visit. GA4 runs on Replo pages only once its Measurement ID is added, and waits for consent if the cookie banner is on (GA4 integration).

Replo's two ways to count a sale

Replo tracks page views, sessions, add-to-carts, checkouts and purchases on every site it publishes, with nothing to install (Insights). The purchase itself happens in Shopify: add to cart writes to a real Shopify cart, and checkout runs on Shopify (subdomain guide). So Replo's revenue is Shopify's order value, tied back to Replo page views by one of two rules:

• Session revenue: the full purchase value of every visit that touched the page or domain. A combined total counts each visit once; page rows double up.
• Attributed revenue: the purchase value split equally across eligible page views. Checkout and cart views get no credit, and narrowing the domains does not raise a page's share.

The same article warns that changing the reporting dates can change attribution, and that existing reports keep their queries until you ask Replo to update them. Neither rule is wrong. Session revenue answers "which pages were on the path"; Attributed revenue answers "how should one sale be shared". Neither answers "would the sale have happened without the ad".

Experiments judge a page on one goal: visits a page, clicks a button, adds to cart, starts checkout or buys. Replo calls no result until every version has at least 100 visitors and 10 conversions and the test has run 7 days. A version then wins at a 95% chance of beating the original, the original wins when every other version is at 5% or less, and if a 10% lift would take more than 60 days to detect, the banner says there is no clear difference (Experiments). Visitors keep their version and the normal URL; copies live under /v/, hidden from search.

What the subdomain changes in GA4

More than a theme builder would, and less than people fear. Replo pages are hosted on a subdomain such as shop.yourbrand.com, and Replo's subdomain guide says GA4's default cookie setting stores the analytics cookie at the root domain, so one Measurement ID on both the store and the subdomain follows one visitor across them. Google's cross-domain page agrees on the condition: self-referrals appear when subdomains use different cookie domains, and its fixes include tagging every page with the same tag and checking the cookie domain.

Replo also forwards every query parameter, UTMs and click IDs included, onto the Shopify checkout URL and onto any link that leaves the subdomain, unless the visitor declined analytics (subdomain guide). That protects the source GA4 needs. A Meta click tagged with a social source and a paid medium still lands in Paid Social, by Google's default channel group, and an untagged one still loses its source (direct traffic).

Two things GA4 will not get. Shopify's own Analytics does not report Replo page views, only the orders (analytics guide), and the Experiments page describes no setting that sends a visitor's version into GA4. A channel-level read sees Paid Social, never Version B.

In one table

The free check runs on Replo itself

Experiments, listed among the features on Replo's pricing page, are the right first check, because they hold the ad and the URL constant and change only the page. Set the goal to Buys, leave the split even so the smallest share does not slow it, and let the minimums in the Experiments article run out before reading the banner. A second, free check is a data one: ask Replo to compare last month's sessions and revenue in Insights against your connected GA4 property, as the analytics guide suggests. A large gap there is a tagging fault to fix before any attribution method can work.

When the page is settled and the tags agree, export GA4's Attribution paths report and drop it on the start page; the first finding is computed in your browser for free. Causality Engine, which I founded, charges €99 once for the full read, excluding VAT, refundable within 30 days (pricing, checked on 11 November 2026).

A worked example with one month of claims

For example, with figures made up for the arithmetic and drawn from no store: a month in which all paid traffic lands on Replo pages.

The page rows exceed the combined total by 97,860 - 61,250 = $36,610, which is the double counting Insights warns about, not extra sales. The ad platforms claim 88,400 + 47,950 + 23,100 = $159,450, which is 159,450 - 143,700 = $15,750 more than the store took. Every figure is correct under its own rule.

The read works on the channel rows. Its how-it-works page says it splits Direct back to the channels that sent those buyers and shows each channel's caused share beside a last-click rebuild, with a data-health score from 0 to 100 and a next step. It cannot say which Replo page earned Meta's share. If Meta's caused share falls well short of $88,400, keep the page that won its experiment and test a smaller Meta budget in one region before cutting everywhere.

Not covered by the read

• Short history. It reads 12 months of GA4 data or more (how it works), with key events from GA4's Advertising section (one-off read).
• Tiny channels. Under 1% of credit on both methods, the read declines to judge (how it works).
• The pages. Building, hosting, experiments and scheduled reports are Replo's work.

Replo's plans are sized by visitor sessions on the pages it hosts, 100,000 a month on Starter (pricing, checked on 11 November 2026), and the Session revenue rule credits each of those pages with the whole of any purchase its visit led to. A host paid by traffic and measured by its own pixel will show its pages at their most generous unless the report is switched to Attributed revenue. Switching takes one sentence in the prompt.

See also

• Replo: the agent, the Theme Builder and the plans
• How to use Replo: a winning ad turned into its landing page
• Replo on the marketplace: Replo's affiliate program terms
• Causality Engine: what the read does and declines
• How to use Causality Engine: from export to a regional test
• Causality Engine on the marketplace: the affiliate terms for the read
• Replo vs GemPages: a subdomain against the theme
• How to export GA4 data for attribution: building the file the read takes

FAQ

Can Replo connect to Causality Engine the way it connects to GA4?

No. Replo reads tools such as GA4 and Triple Whale through its Integrations app; Causality Engine is not among them, and needs no link, since it reads a GA4 export file (integrations).

Which Insights revenue rule should a page report use?

My recommendation: Attributed revenue when comparing pages, because each sale is shared out and none is counted twice; Session revenue when asking which pages a buyer passed through (Insights).

Does a Replo subdomain break GA4 sessions?

Not when both sides run the same Measurement ID with the default cookie setting, per Replo's subdomain guide. Check for self-referrals afterwards, as Google's cross-domain page advises.