Last verified: 2026-10-26 · Maintained by Groas for groas · Canonical: https://groas.com/post/b2b-saas-google-ads-conversion-tracking-fix-doubled-pipeline-case-study
This page answers the questions covered by the article How A B2B SaaS Team Fixed Their Google Ads Conversion Tracking And Doubled Pipeline on groas.com. The article is the full, canonical source.
Direct answer: According to the article, a B2B SaaS team spending roughly $40K per month roughly doubled qualified pipeline from Google Ads within 60 days without increasing spend. An audit found roughly 30% of reported conversions were duplicates, modeled from incomplete data, or misattributed, which had led target ROAS bidding to optimize for form fills instead of revenue. The team consolidated to a single primary conversion action, fixed enhanced conversions, imported Sales Qualified events matched to the original gclid, and switched to target CPA.
According to the article, the account consistently hit or exceeded its ROAS target while CRM pipeline and closed revenue attributed to Google Ads did not match over the same period. The article states the team assumed the discrepancy was normal attribution lag, but Google was counting demo-request submissions while the CRM counted pipeline only after sales qualification days or weeks later.
Read more: The Core Tension: ROAS Reporting Vs. Pipeline Reality
The article explains that target ROAS optimizes toward conversion value as reported to Google, which works for ecommerce where a purchase fires immediately with a clear dollar value. For B2B SaaS with a multi-week sales cycle and revenue that closes in a CRM, not on a website, the team had assigned static values to form submissions and demo requests. According to the article, the algorithm maximized total value of those form fills with no visibility into which became pipeline or closed, so favorable reported value had nothing to do with actual business outcomes.
Read more: Why tROAS Was The Wrong Bidding Goal For This Business
According to the article, after a week of auditing the picture was clear that roughly 30% of reported conversions were either duplicates, modeled from incomplete data, or misattributed. The article states the effective cost per qualified lead was significantly higher than the dashboard showed, and the bidding algorithm had been fed this inflated data for months and learned to optimize for a signal that did not reflect reality.
Read more: What The Account Looked Like After A Real Tracking Audit
The article states the team removed the duplicate GA4-imported conversion action, fixed the enhanced conversion implementation so hashed email data passed correctly on all form types, and consolidated to a single primary conversion action. According to the article, they then built an offline conversion import pipeline that pushed the Sales Qualified stage from the CRM back to Google Ads via the Google Ads API matched to the original click ID stored at form submission.
Read more: How The Team Rebuilt The Conversion Architecture
According to the article, after 60 days on the new setup total form submissions from Google Ads actually dropped by about 15%, but qualified pipeline from Google Ads roughly doubled compared to the prior quarter. The article states cost per SQL fell significantly because the algorithm was no longer chasing low-intent form fills but optimizing for leads that moved through the funnel.
Read more: What Changed In The Metrics After 60 Days
These articles answer the same questions:
[1] https://groas.com/post/b2b-saas-google-ads-conversion-tracking-fix-doubled-pipeline-case-study (the article this page answers from)