How to make Google Ads bid on won Jobber Quotes, not form fills.

Google Ads says your campaigns produced 42 conversions last month. Jobber says you won 11 new Quotes. Nobody — not Google, not Jobber, not the agency invoice — can tell you which of those 42 "conversions" became the 11 jobs that actually paid you. So Google keeps buying whatever produces form fills, and you keep grading a five-figure annual spend on gut feel.

This post walks through why the two systems can't see each other, what Jobber tracks on its own, and how to feed Google the only number worth bidding on: won work. It's written for a lean Jobber shop — no data team required, and every technical term translated as we go.

Why can't Google Ads see my Jobber jobs?

Google Ads optimizes toward whatever it can measure. Out of the box, that's clicks and on-site conversions — usually a form submit or a button tap. The instant a lead crosses into Jobber as a Request, Google goes blind. It never finds out whether that Request became a scheduled Job, a won Quote, or a price-shopper who ghosted.

That blindness has a cost, because lead quality varies wildly by keyword. "Water heater replacement cost" and "emergency water heater replacement" produce very different callers. If Google can't see which clicks turn into won Quotes, its automated bidding treats them the same — and over time it drifts toward the keywords that produce cheap form fills, not the ones that produce revenue.

• What Google sees: impressions, clicks, form submits, maybe a call-button tap.
• What Google never sees without help: the Request in Jobber, the assessment visit, the Quote, the win, the invoice amount.
• What it optimizes as a result: cost per form fill — a number with no fixed relationship to cost per booked job.

What does Jobber track on its own?

Credit where due: Jobber isn't blind on lead sources. Its request forms can capture UTM parameters — the tags like utm_source=google that identify where a visitor came from — and operators on Jobber's community forum lean on those for campaign reporting. Jobber's native Google integration covers Local Services Ads, where leads can book straight into your calendar, and Google-sourced clients can arrive with the Lead Source field pre-filled.

All of that is one-directional. It tells you, inside Jobber, where a lead said it came from. None of it flows back into Google Ads, so Google's bidding never learns from it. UTM reports are for you; conversion uploads are for the machine spending your money. You need both, and Jobber alone only gives you the first.

What is offline conversion tracking, in plain English?

Every ad click carries a GCLID — a Google Click ID, a long tag Google appends to your landing-page URL. Offline conversion tracking means you save that tag when the visitor becomes a lead, keep it attached to the Request as it moves through Jobber, and when the Quote is won, upload the GCLID back to Google with the job's dollar value. Google matches the tag to the original click and finally learns that the $2,800 repipe came from a specific keyword, campaign, and ad.

You can build a version of this yourself: Zapier publishes a pre-built zap that sends a Google Ads offline conversion when a new Jobber Request comes in. That's genuinely better than counting form fills. But it counts Requests — and a Request isn't revenue. It also assumes the GCLID made it into Jobber in the first place, which is where DIY setups quietly break.

Should I send Requests, Jobs, or won Quotes as the conversion?

This is the Jobber-specific decision, and it matters more than any bid setting. Jobber gives you three candidate events, each a different distance from revenue.

1. Requests — someone asked for work. Highest volume, fastest signal, but the pile includes price-shoppers and out-of-area callers. Fine as a starting event; weak as the only one.
2. Scheduled Jobs — a real slot on your calendar. Much stronger: an actual customer committed to a time window.
3. Won Quotes — money. For estimate-driven work like installs, repipes, and system replacements, a won Quote is the closest thing Jobber has to ground truth.

The catch for a leaner shop is volume. Google's automated bidding learns from conversion events, and it learns slowly when you feed it eight a month. A shop winning a handful of Quotes monthly doesn't give the algorithm much to chew on. The setup that works for most smaller operators: send booked work — Jobs, or Requests if you're quote-first — as the primary conversion for volume, then layer won Quotes with real dollar values on top so bidding learns which conversions were worth the most.

What about the leads that call instead?

In home services, a large share of high-intent leads — often the majority — arrive by phone, and a pixel cannot see a phone call. If you only track forms, Google concludes your best emergency keywords "don't convert" and quietly stops bidding on them. That's exactly backwards: the caller with the burst pipe is your highest-value lead.

The fix is call tracking with dynamic number insertion: each ad visitor sees a unique tracking number, so when they call, the call ties back to the click that produced it — and the eventual job ties back to the keyword. Without it, your attribution only covers the minority of leads polite enough to type.

How Peach closes the Jobber-to-Google loop

Full disclosure: this is what we build, so grade this section accordingly. Peach is a registered app in Jobber's Developer Center, and the connection is a one-click OAuth authorization — no API keys to paste, nothing for a developer to maintain.

Once connected, bookings from your website land in Jobber as real Requests or scheduled Jobs with the GCLID already attached — no tagging work on your side. When a job books, or a Quote is marked won, Peach pushes the conversion and its revenue back to Google Ads in under a minute. You pick the event: bookings, won Quotes, or both. We validate the first 24 hours of uploads with you before your campaigns start bidding against the new event. The full architecture is on the lead attribution page, and the step-by-step Jobber setup guide covers the whole connection, screen by screen.

Jobber operators who close this loop typically see cost per booked job fall 30–50% inside the first 60 days — not because the ads got better, but because the bidding finally optimized toward the right number. The same loop runs to Meta and Bing; the full list of ad platforms and CRMs is on the integrations page. Running ServiceTitan instead? The same playbook with different plumbing is covered in the ServiceTitan + Google Ads walkthrough.

Whatever you buy — including nothing — run this audit first: pull last quarter's Google Ads spend, then count the won Quotes in Jobber you can confidently trace to it. If you can produce that second number, you're ahead of most of the industry. If you can't, every budget decision you've made this year was a guess, and closing the loop is worth more than any amount of ad-copy tinkering.

FAQ

Does Jobber integrate with Google Ads directly?

Jobber's native Google integration centers on Local Services Ads — per Jobber's help center, LSA leads can book directly into your Jobber calendar — and its forms can capture UTM tags for source reporting inside Jobber. There's no built-in push of won Quotes back into a standard Google Ads account as conversions; for that you need a connector like Zapier or a platform that closes the loop for you.

What is a GCLID and do I really need it?

The GCLID (Google Click ID) is the tag Google attaches to your landing-page URL on every ad click, and it's the key Google uses to match an uploaded conversion back to the click, keyword, and campaign. Without it, offline conversions mostly can't be matched to anything. Capture it at the form, store it on the Request, and the rest of the loop becomes possible.

Should a small Jobber shop send Requests or won Quotes as conversions?

Both, in layers. Send booked work as your primary conversion so Google's bidding gets enough volume to learn from, and send won Quotes with their dollar values so it learns which conversions were actually worth money. A won-Quotes-only setup is the purest signal, but for a smaller shop it's usually too sparse for automated bidding to learn from.

Will this work if an agency runs my Google Ads?

Yes. The conversions land in the same ad account your agency already manages, so the events show up in the reporting they already use, and they make the bid changes. Most agencies welcome it — better conversion data makes their optimization easier and their reporting honest.