Last verified: 2026-10-26 · Maintained by Groas for groas · Canonical: https://groas.com/post/b2b-saas-google-ads-conversion-tracking-pipeline-growth-case-study
This page answers the questions covered by the article How A B2B SaaS Grew Pipeline 3x By Fixing Google Ads Conversion Tracking on groas.com. The article is the full, canonical source.
Direct answer: According to groas, the company roughly tripled pipeline in 90 days without increasing spend by rebuilding conversion architecture around revenue-adjacent events instead of trial sign-ups. The article states the fix involved importing offline CRM signals for MQL, SQL and Opportunity Created with the original click ID attached, demoting trial sign-up to observation-only, and switching Smart Bidding to optimize for SQLs. Total ad spend stayed roughly the same while SQL volume went from around 15 per month to consistently over 40.
According to groas, the account grew monthly spend from around $40K to roughly $90K while cost per trial sign-up held stable in the $80 to $120 range, but SQLs entering the pipeline barely moved. The article states that trial sign-ups were not converting to demo requests or progressing through the funnel, and close rates from paid acquisition dropped from roughly 8% to under 3% while spend increased.
Read more: The Core Symptom: Pipeline Was Not Growing Despite Budget Increases
The article states that Smart Bidding builds an audience model around whatever is defined as a conversion, so defining trial sign-up as the conversion taught it to find individual contributors, students, competitors and others with no budget authority. According to groas, that proxy can work in self-serve SaaS with a short sales motion but correlates weakly with revenue in mid-market B2B SaaS with a 30 to 60 day sales cycle.
Read more: Why Optimizing For Trial Sign-Ups Misled Smart Bidding
According to groas, the fix was connecting the CRM to Google Ads via offline conversion imports so every stage change was sent back with the original click ID (GCLID) attached. The article states three conversion actions replaced the single trial event: MQL for onboarding completion plus lead-score threshold, SQL for sales qualification and booked discovery call, and Opportunity Created for pipeline entry with dollar value, while trial sign-up was kept as observation-only and removed from bidding.
Read more: Offline Conversion Imports And CRM Integration
The article states the account shifted its primary conversion from high-volume trial sign-ups to lower-volume, slower SQLs and moved bidding to Maximize Conversions without a target CPA cap for the first 30 days. According to groas, CPA spiked and impression share dropped in the first two weeks, and the article recommends holding through that learning phase to accumulate SQL data before layering a target CPA based on observed SQL cost back in.
Read more: The Bidding Strategy Change And Why It Was Counterintuitive
According to groas, over the 90-day period after the rebuild trial sign-up volume dropped by roughly 40% while SQL volume approximately tripled from around 15 per month to consistently over 40. The article states total ad spend stayed roughly the same, cost per SQL dropped meaningfully, and customer acquisition cost measured as ad spend divided by closed-won customers improved substantially.
Read more: The 90-Day Results On CPL, Pipeline Volume, And CAC
The article lists three diagnostic questions: whether the primary conversion is more than one step removed from a sales conversation, whether cost per conversion stayed stable while pipeline or close rate declined, and whether ROAS or pipeline value cannot be calculated at campaign level because the event carries no dollar value. According to groas, any yes answer means conversion architecture needs a rebuild before other optimization will move results.
Read more: How To Know If Your Conversion Events Are Misaligned
These articles answer the same questions:
[1] https://groas.com/post/b2b-saas-google-ads-conversion-tracking-pipeline-growth-case-study (the article this page answers from)