Your Google Ads dashboard says the channel drove 120 conversions last month. Your Salesforce pipeline report, filtered to the same source, says 34 opportunities. The CFO wants to know which number is real, and the honest answer — both, they measure different things — is exactly the answer that loses you the room. The way to keep paid budget is not to defend the bigger number; it is to reconcile the two so the shrinkage from platform conversions to recognized pipeline is explained, expected, and defensible.
This post is for revenue-accountable marketing leaders and founders at Series A to Series C B2B SaaS companies with meaningful paid spend ($10k–$100k+/month) and a CFO or board asking what that spend returns. It lays out a reconciliation framework — the bridge from Google Ads-reported conversions to CRM-recognized pipeline — so your paid numbers survive a board review instead of triggering a budget cut.
Why the two numbers will never match
Start by naming the four reasons the platform and the CRM disagree, because a CFO who understands the mechanism stops treating the gap as a credibility problem. First, timing: Google Ads credits a conversion to the click date using its attribution window, while the CRM recognizes an opportunity on the date it is created — often 30 to 90 days later. Second, the model: Google Ads data-driven attribution spreads fractional credit across touchpoints, whereas most CRMs assign all credit to a single source, so the same deal counts differently in each system.
Third, counting rules: if conversion counting is left on "Every" instead of "One," a single lead who submits two forms inflates the platform number without adding pipeline. As the attribution vendor Cometly notes, for B2B lead gen the "One" per-click setting is almost always correct. Fourth, and biggest, lead quality: a form fill is not an SQL. Most of the gap between 120 conversions and 34 opportunities is not a tracking fault at all — it is the funnel doing its job and disqualifying leads that were never going to close.
The reconciliation bridge
The board-facing artifact is a single waterfall that walks from the platform number down to recognized revenue, with the loss at each step labeled. This is the one table that ends the "whose number is right" argument, because it shows both numbers as endpoints of the same chain:
| Stage | Source of truth | Typical step-down | Why it shrinks |
|---|---|---|---|
| Platform conversions | Google Ads | — | Form fills, counted on click date, modeled credit |
| Marketing-qualified leads | CRM | Drops junk / duplicates | Counting rules, bots, non-ICP form fills |
| Sales-qualified leads / opps | CRM | Largest single drop | Lead quality — most form fills are not buyers |
| Closed-won | CRM / finance | Win-rate × cycle | Some deals close past the 90-day GCLID window |
Fill the "step-down" column with your numbers, not benchmarks, and the gap stops looking like a measurement failure and starts looking like a funnel you manage. The CFO's question — "what does paid return?" — is answered at the bottom row, in pipeline and closed-won, with the platform number serving only as the top of the chain. For the full measurement setup behind this, see measuring pipeline from Google Ads.
Fix the 90-day window before it eats your revenue
The single most damaging silent failure in B2B SaaS attribution is the GCLID window. Google Ads offline conversion imports are only attributed if uploaded within 90 days of the click. With an average B2B SaaS sales cycle around 80–90 days — and far longer for deals above $50k ACV — a large share of your closed-won deals close after the window and attribute to nothing. The platform then looks like it stopped producing revenue, and the board starts questioning the channel that is actually working.
The fix is to pick an import event that reliably lands inside 90 days — typically the SQL or opportunity-created stage — and feed that back to Smart Bidding, while recognizing closed-won revenue separately in the CRM. This keeps the bidding algorithm optimizing toward quality without depending on a deal closing inside an impossible window. Our conversion window guide and the GCLID vs enhanced conversions comparison cover the setup choices in detail.
Feed the algorithm the number the board cares about
Reconciliation is not only a reporting exercise — it changes what you buy. When you import offline conversions so Google Ads optimizes toward SQLs and opportunities rather than form fills, the gap between platform and CRM narrows on its own, because the algorithm stops buying the cheap, non-converting leads that created the gap in the first place. This is the highest-leverage change available to most accounts; the vendor Metadata.io, analyzing tens of millions in B2B ad spend, makes the same core point: cheap leads are a mirage once full pipeline attribution is applied.
Mechanically, this means passing the GCLID into a hidden form field, storing it on the lead in HubSpot or Salesforce, and uploading the qualified-stage conversion back to Google Ads when the lead crosses it. The offline conversion tracking guide and the offline conversion stack walk the full implementation.
Make it a monthly ritual, not a fire drill
A reconciliation that only happens when the board asks is a reconciliation you will lose. Run the waterfall every month, on the same definitions, and store the step-down ratios so the trend is visible. When lead quality slips, the SQL step-down is the first place it shows — before the closed- won number moves — giving you a month or two of lead time to fix the account before the board sees a revenue miss.
Lock the definitions once and defend them. The fastest way to lose a CFO's trust is a metric whose definition drifts quarter to quarter; the fastest way to keep it is a number that reconciles to the system of record every single month. Pair this reconciliation with the five Google Ads metrics SaaS boards care about and report them together, every cycle.
The Two Spouts view
Stop trying to win the argument about which number is bigger. In our experience advising funded B2B SaaS teams, the marketing leaders who keep their paid budget are the ones who hand finance a reconciled waterfall and say, "here is the platform number, here is where it becomes pipeline, and here is what closed." The CFO does not need the platform number to be large; they need it to tie out. A reconciled 34 opportunities beats an unexplained 120 conversions in every board meeting we have ever sat in.
The one hard call is which system is the board-facing source of truth. Our answer is almost always the CRM: it is where finance already recognizes revenue, so aligning paid reporting to it removes an entire category of cross-functional argument. Use Google Ads data-driven attribution to steer bids and manage the channel; use the CRM to report up. For how the pieces fit, see our attribution models guide.
If you want an outside read on where your platform numbers and your pipeline diverge — and whether the gap is a tracking fault or a lead- quality problem — a Google Ads audit will map the full reconciliation for your account, or start with the free 10-point audit to pressure-test your tracking yourself.