Why Platform ROAS and Real ROAS Are Often Different Numbers
What is "closed-loop ROAS" and why does it often differ from the ROAS an ad platform reports?
An ad platform's reported ROAS is based on the conversions it can see — a form fill, a pixel event, a reported sale — not on what actually happened to that lead afterward. Closed-loop ROAS instead links each won deal back to the specific campaign and creative that sourced it, using real CRM outcomes, so the ROAS number reflects revenue a business actually collected rather than revenue a platform inferred.
Every ad platform is, in a real sense, grading its own homework. Meta, Google, TikTok, and LinkedIn each report performance using their own attribution windows, their own conversion definitions, and data they themselves collected. That is a structural conflict of interest, not a conspiracy — the platforms have no visibility into what happens after a lead leaves the ad, and no reason to report conservatively even if they did. A lead that looks like a conversion in Ads Manager can turn out to be a spam submission, a tire-kicker who never replies, or a deal that closed for a fraction of the average contract value. None of that shows up in a platform dashboard.
Loomstrat's three live products exist, in part, because this gap is exactly where a lot of marketing budget gets allocated wrong. Loomstrat CRM captures and scores the lead the moment it lands. Loomstrat Analytics unifies ad spend across platforms and closes the loop back to what the CRM shows actually closed. Loomstrat OS takes that closed-loop number one step further and adjusts it for incrementality — whether the spend actually caused the sale, or whether it would have happened anyway. Together, they describe one continuous chain: ad click, scored lead, real deal outcome, incremental profit.
Loomstrat CRM: Every Lead Keeps Its Source, All the Way to Won
How does Loomstrat CRM keep a lead connected to its original ad campaign as it moves through the pipeline?
Every lead that enters Loomstrat CRM through Meta Lead Ads, a website form, or a booking page is tagged with its source and campaign at capture, scored 0–100, and tracked through pipeline stages (New, Contacted & Qualifying, Proposal, Won) with a visible SLA clock at every stage — so the deal that eventually closes still carries the campaign and creative that originally sourced it.
This matters because attribution breaks most often at the handoff points — the moment a lead moves from the ad platform into a spreadsheet, or from a sales rep's memory into a CRM field filled in days later, inaccurately, or not at all. Loomstrat CRM's pipeline cards show the source directly (“Instagram · Spring promo,” “Facebook · Free audit,” “Embed form · /pricing”), captured automatically through signed webhooks rather than typed in by a rep after the fact. Duplicate leads are flagged on arrival, which matters for attribution accuracy too — a lead counted twice inflates both the platform's reported conversions and a naive revenue-per-lead calculation.
The pipeline also carries real deal value, not just a lead count. Quotes built inside the product — with line items, tax, and discounts — are shared as links the prospect can open, and the system tracks every view and the exact moment a quote is accepted. A manager's forecast view rolls open pipeline, weighted by each stage's historical win probability, up against quota, per rep. By the time a deal is marked Won, there is a real dollar figure attached to it, not an assumed average order value — which is the number that actually needs to make it back to the ad platform data for ROAS to mean anything.
Loomstrat Analytics: Closing the Loop From Ad Spend to Closed Revenue
How does Loomstrat Analytics calculate closed-loop ROAS, and how is it different from the ROAS in an ad platform's own dashboard?
Loomstrat Analytics connects to a team's CRM and links every won deal back to the campaign and creative that sourced it, then compares that real closed revenue against what the ad platform itself reported — producing a “true ROAS” figure per lead, with spam and junk leads automatically quarantined so they don't distort the number.
The product's own framing of this is direct: “Stop reporting on leads. Start reporting on revenue.” Loomstrat Analytics already unifies spend, cost per lead, ROAS, and funnel metrics across Meta, Google, TikTok, and LinkedIn into one cross-channel view with campaign-to-creative drill-down. The closed-loop layer is what turns that into a revenue number rather than a volume number — a performance dashboard can show a lead costing $21.40, with a closed-loop view showing that specific lead's campaign converting at a true ROAS of 6.2x once the deal actually closed, or showing a different lead still sitting at “—” because the deal hasn't resolved yet.
This is also where the automation layer connects back to something real: the product's automation rules can be weighted by closed-loop ROAS rather than platform-reported cost per lead, so a rule like “reduce budget 20% when ROAS falls below 2.0x” is responding to a number that reflects actual closed revenue, not a platform's optimistic conversion count. An agency acting on platform-reported ROAS alone can end up cutting budget on a campaign that is actually producing the agency's best-closing leads, simply because the platform doesn't know those leads closed.
“Link every won deal back to the campaign and creative that sourced it. Closed-loop ROAS compares that real, closed revenue against what the ad platform reports.”
- Loomstrat Analytics, product description
Loomstrat OS: Profit That Only Counts Revenue the Spend Actually Caused
What does it mean for Loomstrat OS to model 'incremental' profit rather than total attributed revenue?
Loomstrat OS's planning engine explicitly counts only incremental revenue toward profit — revenue the marketing spend actually caused, not revenue that would likely have arrived anyway — which is the step beyond closed-loop attribution that most planning tools skip entirely.
Closed-loop ROAS answers “did this ad spend produce a deal that closed?” It doesn't fully answer a harder, related question: would that customer have found the business anyway — through organic search, a referral, or direct traffic — even without the ad? Loomstrat OS's own site names this gap directly, describing “incrementality-adjusted profit” as one of the five specific failures of typical business plans it is designed to close, alongside the related problem of attributed revenue that “includes sales that would have happened anyway.”
This is where the three products' roles become genuinely complementary rather than redundant. Loomstrat CRM supplies the real, traceable deal data. Loomstrat Analytics turns that into closed-loop ROAS per campaign and creative. Loomstrat OS takes that closed-loop number into a full planning model — one that also runs the funnel with realistic lags, tracks cash and interest month by month, and stress-tests the plan's weakest assumption before any budget decision based on it gets approved. A budget decision made on platform ROAS alone skips two real adjustments a careful plan makes: is the revenue real (closed-loop), and is it incremental (would it have happened without the spend)?
One Loop, Not Three Disconnected Tools
Most agencies already run some version of this chain — an ad platform, a CRM, and a spreadsheet or planning tool — but as three separate systems that each only see part of the picture. The platform sees spend and its own conversion count. The CRM sees pipeline and deal value, often with the original ad source lost somewhere in a manual data-entry step. The planning tool sees whatever numbers get typed into it, usually without a clear record of whether they came from the platform, the CRM, or someone's best guess.
| Stage | What it sees | What breaks if it’s disconnected |
|---|---|---|
| Ad platform (Meta, Google, TikTok, LinkedIn) | Spend, clicks, and its own reported conversions | No visibility into whether a "conversion" ever became a real customer |
| Loomstrat CRM | Lead source, score, pipeline stage, real deal value, win/loss | Attribution gets lost if the source isn’t captured automatically at intake |
| Loomstrat Analytics | Cross-channel spend joined to CRM outcomes — closed-loop, true ROAS | Budget decisions default back to platform-reported ROAS, which overweights volume over revenue |
| Loomstrat OS | Closed-loop revenue adjusted for incrementality, inside a stress-tested plan | Plans count revenue that would have happened anyway, inflating projected returns |
The Part Most Attribution Tools Skip: Bad Leads Poisoning the Number
How does bad lead quality distort a closed-loop ROAS number if it isn't filtered out?
A spam or junk lead that enters the pipeline still counts as a “lead” in most reporting, which drags down cost-per-lead and distorts conversion-rate-based ROAS estimates even though that lead was never going to close. Loomstrat Analytics applies reversible, heuristic spam-lead quarantine so those leads don't silently poison the closed-loop number, and the quarantine can be reviewed and reversed rather than permanently discarding a lead that was flagged incorrectly.
This is a small detail with an outsized effect on trust in the number. If 15% of “leads” from a given campaign are actually bot traffic or disposable-email form spam, every metric built on top of that lead count — cost per real lead, expected close rate, projected ROAS — is wrong in the same direction, usually making the campaign look worse than it is. Quarantining those leads before they enter the closed-loop calculation keeps the eventual ROAS number closer to what a sales team would say if you asked them directly: which of these leads were ever real.
Where to Start
The full loop is strongest when all three products are connected, but each one also stands on its own for the specific gap it closes.
Leads losing their source on the way to a sale
Loomstrat CRM captures Meta Lead Ads, website forms, and bookings with the source attached automatically, and keeps real deal value attached through Won.
See Loomstrat CRM →Reporting platform ROAS your team doesn’t fully trust
Loomstrat Analytics links closed CRM deals back to the campaign and creative, with spam-lead quarantine and automation rules weighted by true ROAS.
See Loomstrat Analytics →Planning next quarter’s budget on unverified assumptions
Loomstrat OS builds the plan on incrementality-adjusted, sourced numbers, then stress-tests it before anyone signs off.
See Loomstrat OS →Frequently Asked Questions
What is closed-loop ROAS?
A return-on-ad-spend figure calculated from real, closed deal outcomes recorded in a CRM, rather than from conversions an ad platform reports on its own. It links a specific won deal back to the campaign and creative that sourced it.
Why is closed-loop ROAS usually different from the ROAS shown in Meta or Google Ads?
Ad platforms only see what happens up to a tracked conversion event (a form fill, a pixel fire) — not whether that lead ever closed, for how much, or whether it was a real customer at all. Closed-loop ROAS reflects what actually happened afterward, inside the CRM.
How does Loomstrat CRM preserve lead source through the whole pipeline?
Leads are captured through signed webhooks from Meta Lead Ads, website forms, and booking pages, tagged with their source and campaign automatically at intake rather than entered manually, and that source stays visible on the lead through every pipeline stage to Won.
What is "incrementality" and why does Loomstrat OS adjust for it?
Incrementality is the share of a result that the marketing spend actually caused, as opposed to revenue that would have arrived anyway through organic search, referral, or direct traffic. Loomstrat OS models incrementality-adjusted profit specifically so a plan doesn’t overstate the return on ad spend by counting non-incremental sales.
How does Loomstrat Analytics handle spam or junk leads in the ROAS calculation?
It applies reversible, heuristic spam-lead quarantine to flag likely junk leads before they distort cost-per-lead and closed-loop ROAS figures, with the quarantine reviewable rather than a permanent, unappealable deletion.
Do I need all three Loomstrat products to get closed-loop ROAS?
No — Loomstrat Analytics can connect to any CRM to produce closed-loop ROAS. Using Loomstrat CRM alongside it removes a manual integration step and ensures lead source is captured automatically rather than relying on reps to log it correctly.
“More leads” is an easy number to report and a poor proxy for the number that actually matters: more profit, caused by the spend, that a business can verify. Closing that loop — from ad click, to scored lead, to real deal outcome, to incrementality-adjusted profit — is what Loomstrat CRM, Analytics, and OS are each built to do their part of, separately or connected end to end.