Google Ads for SaaS: B2B search that bids on revenue
Run Google Ads for a SaaS or B2B product: choose search intent, import trials, qualified leads and won deals, and bid on value once it is real.
By DATALYR · · 4 min read
Contents
What Google Ads needs from a SaaS account
Google Ads works for SaaS and B2B when Smart Bidding learns from paying customers or qualified pipeline rather than from form fills. Search captures people already looking for a solution; the harder part is reporting back the outcome that happens days or weeks after the click.
That makes SaaS PPC a measurement problem as much as a keyword problem. A campaign that produces cheap demo requests from the wrong companies will look efficient until sales reviews the pipeline. Feeding Google the later stage closes that gap.
This guide covers self-serve products that bill through Stripe and sales-led products that close in a CRM. The same steps apply to 'Google Ads for B2B' and to SaaS paid acquisition in general.
Group keywords by intent you can serve
Most SaaS search accounts split into four groups: your brand, the category ('payroll software for agencies'), the problem ('how to automate payroll approvals') and competitor or alternative terms. Each group has different conversion rates and different sales cycles, so give each its own campaign and its own target.
Brand terms usually convert well because the searcher already knows you. Category and competitor terms carry more new demand and more uncertainty. Problem terms often produce earlier-stage visitors who need content before a trial or demo.
Keep the landing page matched to the group. A competitor-term visitor wants a comparison; a category visitor wants pricing, proof and a clear trial or demo path.
Import the outcome, not the form
Google's offline conversion import lets you upload a conversion that happened after the click, such as a qualified lead or a won deal. The upload is matched through the Google Click ID (GCLID) you stored with the lead. Google says conversions uploaded more than 90 days after the associated click are not imported.
Enhanced conversions for leads adds hashed customer data, such as an email address, to improve matching when a click ID is missing. Google describes it as an upgraded version of offline conversion import. Google points these uploads to the Data Manager API: from June 15, 2026, the Google Ads API stopped accepting new adopters of offline conversion imports, including enhanced conversions for leads.
DATALYR uploads to a Google Ads conversion action of type Import from clicks, through the Data Manager API by default. Each upload needs a click ID, an email or a phone number. The lookup window for a Google click is 90 days.
From click to imported outcome
1. Click
GCLID on the landing URL
Stored with the visit before any redirect drops it.
2. Lead
Form, trial or booked demo
Tied to the visit by email or visitor ID.
3. Outcome
Qualified, won or paid
Uploaded within 90 days of the click.
Example: value changes the winner
This is a hypothetical example with contract values, not collected cash. Two campaigns each spend $6,000.
The category campaign produces 120 demo requests, so each costs $6,000 ÷ 120 = $50. Twelve deals close at an average contract of $6,000, which is $72,000 in contract value. The competitor campaign produces 60 demo requests at $100 each. Nine deals close at an average of $9,000, which is $81,000.
A bid strategy optimizing on demo requests would push spend toward the category campaign. Measured on won contract value per dollar, the competitor campaign returns $81,000 ÷ $6,000 = 13.5 against $72,000 ÷ $6,000 = 12.0 for the category campaign.
Contract value is a bidding signal, not revenue. Report cash from your billing system, and keep the two numbers on separate lines.
Cheaper demos, smaller contracts
Category terms
$50 per demo → $72,000 won
120 demos, 12 deals at $6,000 average contract.
Competitor terms
$100 per demo → $81,000 won
60 demos, 9 deals at $9,000 average contract.
Bid on value once value is real
Maximize conversion value is the Smart Bidding strategy that aims for the most conversion value within your budget. It needs conversion values that mean something. For a self-serve product, the first Stripe payment is a clean value. For a sales-led product, a won deal's contract value is the usual choice.
DATALYR's HubSpot and Zapier setups create a Google Ads rule for won deals with a dynamic value from the deal amount and the deal ID as the order ID. That value goes to Google for bidding. Inside DATALYR it stays a non-cash fact and never counts as revenue; cash comes from Stripe or another payment source.
For Google Ads you pick the conversion action in DATALYR's rule editor, since it differs per account. Handle refunds outside conversion rules, because Google rejects negative conversion values.
Check one click end to end
Before trusting a bid strategy, trace one real journey. Click a live ad, confirm the GCLID is still on the landing URL after every redirect, complete the conversion with a test email, and find the event in DATALYR.
Google accepts an upload first and validates it later. A DATALYR delivery row reads processing after the upload and sent once Google confirms it, usually within 40 minutes. Then check the conversion action's own diagnostics in Google Ads.
If rows fail with a missing click ID and no enhanced conversion data, the landing page lost the GCLID or no email reached the event. Fix capture first; changing the bid strategy cannot repair a missing identifier.
Related articles.
Conversion delivery ·
Offline conversion tracking: connect a lead to the sale that follows
Define the lead-to-sale record, preserve eligible matching data, and verify imported outcomes without confusing acceptance with advertising credit.
Google Ads ·
Enhanced conversions: web and lead workflows, current settings and verification
Understand the different business workflows behind enhanced conversions, Google’s unified settings, and the evidence needed to verify a setup.
Google Ads ·
Google Ads server-side tracking: setup and verification
Choose the right delivery path, connect the intended Google Ads account, and verify one conversion from its source event through reporting.
