Littledata MonitorAI guide

The value banner in the Littledata app shows one or more dollar (or percentage) figures that say “this is what Littledata is worth to your store.” Each figure is a tier — a single, named way of measuring value.

This page is a plain-English dictionary of every tier you might see. For each one: the label that appears on screen, what it means without the maths, when it shows up, and a worked example.

For the detailed calculations (windows, formulas, edge cases) see Value metrics — how they’re calculated.

How to use this page

The banner usually shows one “headline” tier (picked because it tells the clearest ROI story) plus a few secondary tiers for context.
Most tiers are a monthly USD figure. A few are percentages.
All figures are estimates from platform reporting (Klaviyo, Google Ads, Meta, GA4, Microsoft Ads). They are not contracts or guarantees — see Limitations.

Klaviyo tiers

Measured incremental Klaviyo revenue

What it means: Revenue earned by Littledata-triggered Klaviyo abandonment flows (Viewed Product, Added to Cart, Checkout Started) that would not have been earned by Klaviyo’s native flows for the same shoppers — because the Littledata flows are set up to exclude anyone the native flows already caught.
When you see it: When flow exclusion rules pass (so we trust there is no double-counting) and the Littledata-triggered flows have positive attributed revenue.
Example: “Measured incremental Klaviyo revenue: $4,200/month.” Littledata’s Viewed Product and Checkout Started flows brought in $4,200 of order revenue last month from shoppers the native flows did not reach.
Unit: USD / month.

Littledata Klaviyo flow revenue

What it means: The total Klaviyo-attributed order revenue from flows triggered by Littledata metrics, before subtracting anything. It does not check whether the same shoppers were also reached by native flows — it’s the “gross” figure.
When you see it: Whenever Klaviyo flows are connected and the Littledata-triggered ones have made some revenue. Often shown alongside Measured incremental Klaviyo revenue for context, or on its own when exclusion rules are not yet passing.
Example: “Littledata Klaviyo flow revenue: $6,800/month.” That’s the sum of Placed Order revenue attributed to all three Littledata-triggered flows over the last 30 days.
Unit: USD / month.

Predicted incremental Klaviyo revenue

What it means: A modelled estimate of how much extra Klaviyo revenue Littledata is likely worth to the store, based on how many more people Littledata reaches at each funnel stage than the native triggers, and the revenue native flows are already producing. It is an estimate used when we cannot yet measure the real incremental number directly. The Littledata-flow contribution is scaled by measured audience uplift and held to a 30% floor when uplift is low or not yet measurable, so the figure stays conservative rather than crediting the full attributed amount (see how the multiplier is calculated).
When you see it: When there is enough native and/or Littledata flow revenue to anchor the maths and a Klaviyo connection to measure audiences. For Klaviyo connections newer than ~30 days, the figure is blended with a peer-store benchmark so a half-warmed audience doesn’t distort it.
Example: “Predicted incremental Klaviyo revenue: $3,500/month.” Native flows brought in $20,000 last month; Littledata reaches roughly 18% more profiles than native triggers at each stage, so we estimate Littledata adds about $3,500/month on top.
Unit: USD / month.
Note: When this tier appears alongside a positive Littledata Klaviyo flow revenue tier, the label switches to “Total incremental Klaviyo revenue” because the actual flow revenue is already in scope and “predicted” would be misleading.

Google Ads tiers

Google Ads ROAS

What it means: Compares the return on ad spend (ROAS) Google Ads sees from Littledata’s server-side purchase upload (Purchase - Littledata) against the next best purchase conversion goal in the account — the one Google Smart Bidding is already optimising against. The dollar figure is the coverage gap: the revenue Littledata reveals that the next-best goal isn’t tracking. A 10% lift factor is then applied to estimate the Smart Bidding contribution, capped at 50% of ad spend.
When you see it: When the account has a baseline purchase action and Littledata’s upload — i.e. most accounts that have been live more than two weeks.
Example: “Google Ads ROAS improved from 3.59x to 3.87x with Littledata.” The ratio is what the copy states — never “Google Ads ROAS: $1,800”, which would label dollars as a multiple. In the chosen 30-day window, Littledata uploaded $32,000 of purchase value to Google Ads; the next best conversion goal (a Shopify pixel) only reported $14,000. The $18,000 gap × 10% Smart Bidding lift = $1,800/month of additional auction value Littledata’s data is unlocking, stated on its own line as the Smart Bidding contribution.
Unit: USD / month (plus an underlying ROAS ratio shown in the tooltip).
Variant label: “Google Ads ROAS (estimated)” appears on older legacy data where the headline falls back to a flat 20% of ad spend.

Google Ads incremental conversions

What it means: The fallback tier shown when there is no baseline purchase conversion action in the account (e.g. a brand-new Google Ads account where Littledata is the only purchase signal). The dollar figure is the value of Purchase - Littledata itself, with a small lift applied for the ROI line.
When you see it: New accounts, or accounts whose only purchase tracking is Littledata’s server-side feed.
Example: “Google Ads incremental conversions: $9,600/month.” Littledata uploaded $9,600 of purchase value over the comparison window — without it, the account would be running blind to purchase outcomes.
Unit: USD / month.

Predicted additional Google Ads attributed revenue

What it means: The prospect version of the two tiers above, for a Google Ads account an agency has connected but which has no Littledata install to measure. There is no Purchase - Littledata action to compare against, so the figure is modelled: the account’s own purchase conversion value — counting only the actions its campaigns actually bid on — multiplied by the peer ratio, how much more purchase revenue Littledata’s connection attributes than the account’s own best purchase goal across customers running both. It is a forward-looking 30-day projection (“next 30 days”), never a measurement of this account.
When you see it: Only on a Google Ads prospect audit (/audit/google-ads/{customerId}), and only for an account Littledata isn’t already feeding. The moment there is real data to read, Google Ads ROAS supersedes it — the prospect page shows the measured tier and drops this one entirely, so the two are never stated together. That holds on the prospect page as much as the customer dashboard: an agency looking at a client already on Littledata sees what it is earning them, not a forecast of value they already have.
Example: “Increase Acme Outdoor’s Google Ads revenue by $9,000 over 30 days.” The account’s campaigns optimise to a Shopify pixel purchase goal that attributed $50,000 last month; the peer cohort attributes 18% more than an account’s own best goal, so ≈$9,000/month more would be attributed — revenue Smart Bidding currently cannot bid against because it cannot see it.
Unit: USD / month.
Caveat: Until the cohort has four donor accounts with settled history it quotes a flat 10% launch assumption (GOOGLE_ADS_PROSPECT_ASSUMED_UPLIFT, matching the v2 connection assumption) and shows no quartile range — a range would present an assumption as a measured distribution. The measured cohort median replaces it automatically once enough accounts qualify.
Caveat: Where no purchase action is primary in the account’s bidding at all, the anchor falls back to its largest purchase action and the tooltip says so — the uplift is then against what the account would optimise to.
Caveat: The mirror case quotes nothing. Where a Littledata purchase action is already what the campaigns bid on, Smart Bidding is already seeing Littledata’s conversions and the uplift has been realised, so no figure is offered — the audit checks carry what is left to tune instead. Read under the same precedence as the anchor (campaign goal usage first, account-level primary as the fallback), so the two can never disagree about what bidding uses.

Microsoft Ads tiers

Microsoft Ads ROAS

What it means: Compares ROAS on Littledata’s offline conversion goal against the Microsoft Channel app’s baseline purchase goal on the same Microsoft Ads account. (Messages name the Microsoft Channel app rather than the UET tag it installs — Littledata’s own server-side uploads land on that same tag, so “UET” would not distinguish the two.)
When you see it: Accounts with both a Littledata offline goal and a client-side purchase goal, where Littledata’s goal is included in bidding.
Example: “Microsoft Ads ROAS: 3.2× with Littledata vs 2.1× without.” Same spend, more measured revenue once Littledata’s goal is in the bidding mix.
Unit: USD / month equivalent (and an underlying ROAS ratio in the tooltip).
Variant label: “Microsoft Ads ROAS (baseline only)” appears when Littledata’s offline goal is excluded from bidding — Microsoft suppresses its data, so we can only show the standalone Microsoft Channel app baseline ROAS and a note explaining the merchant needs to enable the goal in bidding to measure incremental lift. See Microsoft Ads exclude-from-bidding suppression.

Meta tiers

Meta additional conversions (ACR)

What it means: A percentage uplift figure from Meta’s own reporting: the share of attributed conversions that only became visible because of the Conversions API, on top of what the browser pixel would have seen on its own.
When you see it: When Meta reports per-event ACR figures back to us. The label may include the strongest event, e.g. “Meta additional conversions for Purchase”.
Example: “Meta additional conversions for Purchase: 18%.” Out of every 100 purchases Meta attributes to your ads, 18 are visible only thanks to Littledata’s server-side events.
Unit: Percentage (not a dollar figure).

Meta Ads pixel ROAS uplift

What it means: When the same Meta ad account has more than one pixel, this compares the ROAS on the Littledata-managed (primary) pixel against the other pixels on the account over the last 30 days. The dollar figure is the extra purchase value the Littledata pixel is attributing that the others are not.
When you see it: Accounts running multiple Meta pixels side by side.
Example: “Meta Ads pixel ROAS uplift: $2,400/month.” The Littledata pixel posts a 3.8× ROAS; sibling pixels post 2.6× on the same spend — the gap is worth about $2,400/month.
Unit: USD / month (and a ROAS multiplier in the tooltip).

GA4 tier

Additional revenue tracked in GA4

What it means: A rough estimate of the extra purchase revenue Littledata’s server-side tracking captures in GA4, beyond what browser-only tracking would see. Calculated as 30% of GA4’s reported purchase revenue over the last 30 days — a conservative rule of thumb, not a full incremental attribution model.
When you see it: When GA4 is connected and reporting purchase revenue.
Example: “Additional revenue tracked in GA4: $14,000/month.” GA4 reported $47k of purchase revenue last month; about 30% of that would not be there without Littledata’s server-side hits.
Unit: USD / month.

Combined tier

Klaviyo and paid media incremental value

What it means: A single headline total that adds up the best Klaviyo dollar tier, the Google Ads ROAS tier, and the Meta Ads pixel ROAS tier — when more than one of them is positive. Used as the ROI denominator against the store’s Littledata subscription cost.
When you see it: Stores with positive value in more than one channel.
Example: “Klaviyo and paid media incremental value: $9,500/month.” That’s $4,200 (Klaviyo) + $1,800 (Google Ads Smart Bidding lift) + $3,500 (Meta pixel uplift), all expressed on a monthly basis.
Unit: USD / month.

Supporting figures (not standalone tiers)

These show up next to the tiers above, in tooltips or secondary lines, to give context.

Additional flow revenue (missing triggers)

The estimated extra incremental USD/month the store could earn if it set up Klaviyo abandonment flows for stages that currently have neither a live native flow nor a live Littledata flow. Stays in the same incremental-revenue units as the tiers above, scaled to the brand’s size: it anchors on the store’s deepest live abandonment flow’s incremental uplift and multiplies by the cohort-median ratio uplift(missing stage) / uplift(anchor stage). Those ratios come from peers running every flow in the funnel span between the two stages, so they are already net of cannibalization (Klaviyo attributes each order to a single last-touch flow, so a shallower flow only books what the deeper one wasn’t already catching). When no flow is live to anchor on — or a stage has no trusted ratio — it falls back to the flat per-trigger peer-median monthly value. Omitted when there are no missing stages or when the peer cohort is too small.

In the audience-maturity modal these per-trigger values render as the dashed “potential if enabled” bars: on the peer-benchmark path the headline prediction is attributed only to the triggers the store actually runs a flow on (the predicted-tier breakdown flags the rest with lockedPotential), so a single-flow store shows its whole prediction on that one trigger and the missing stages appear as separate upside that is not counted in the headline.

Before/after Littledata comparison card

A separate card above the audit check table showing the customer’s most impressive value metric — Klaviyo abandonment flow revenue (Littledata-triggered and native flows combined) — before vs after Littledata was installed, as a 2-bar chart with a short explanation. The “after” bar is the monthly-equivalent combined flow revenue from the recent snapshot window; the “before” bar is the estimated counterfactual baseline: that revenue minus the incremental slice we measure Littledata adding (the observed incremental tier, or the measured-uplift prediction — never the peer-benchmark model). Only shown when Littledata’s Klaviyo connection is at least ~30 days old, combined flow revenue is positive, and the measured uplift leaves a meaningful baseline. Served as valueMessages.beforeAfterCard (strings are server-built).

Net-new Klaviyo profiles

A side figure shown alongside the Klaviyo prediction: how many people whose Klaviyo profile was created after Littledata connected. Useful for showing list growth, but not used as the revenue multiplier (see why).

Days to value

How many days of the current monthly value run-rate would cover one month of Littledata subscription. A rough talking-point for trials and onboarding — not a forecast.

ROI multiple

The headline value divided by the monthly Littledata cost, e.g. “12×”. Used in monthly ROI emails and the value banner where plan cost is known.

Alternative plan

A cheaper active pricing tier for the store’s current order volume, shown on the banner as “On the {plan} plan this would be X× ROI”, with the plan’s price and saving in the ROI tooltip. Appears when a store is paying heavy per-order overage on a plan it has outgrown — see ROI and days to value. Banner copy only; the ROI figure itself still uses what they pay today.

Quick reference table

Label in the banner	Unit	Channel	Headline candidate?
Measured incremental Klaviyo revenue	USD/month	Klaviyo	Yes
Littledata Klaviyo flow revenue	USD/month	Klaviyo	Yes
Predicted incremental Klaviyo revenue	USD/month	Klaviyo	Yes
Total incremental Klaviyo revenue	USD/month	Klaviyo	Yes (label variant)
Google Ads ROAS	USD/month	Google Ads	Yes
Google Ads ROAS (estimated)	USD/month	Google Ads	Yes (legacy label)
Google Ads incremental conversions	USD/month	Google Ads	Yes
Predicted additional Google Ads attributed revenue	USD/month	Google Ads	Yes (prospects only)
Microsoft Ads ROAS	USD/month	Microsoft Ads	Yes
Microsoft Ads ROAS (baseline only)	ROAS ratio	Microsoft Ads	No
Meta additional conversions (ACR)	%	Meta	No
Meta Ads pixel ROAS uplift	USD/month	Meta	Yes
Additional revenue tracked in GA4	USD/month	GA4	Yes
Klaviyo and paid media incremental value	USD/month	Combined	Yes

Value metrics — how they’re calculated — Full mechanics: windows, formulas, edge cases, suppression rules.
Klaviyo flows — The audit checks behind the Klaviyo tiers (exclusions, competitor flows, coverage).
Customer emails (Intercom) — How these tier values are surfaced in monthly ROI and trial emails.
Customer API — Loading the same value messaging from other Littledata apps.