Jobber Lead Source Tracking: UTM Tags, Click IDs and the Quote That Got Approved

Google, Other and the honest customer

A pressure-washing company spends on search ads in spring and on Facebook in fall, keeps a Google Business Profile busy with photos, and wraps two trucks. Its Jobber lead source report is mostly Google, with a respectable slice of Other. The owner suspects the Facebook money is wasted. He might be right. The report cannot tell him, because the lead source came from a dropdown the customer filled in, and customers remember the last screen they saw, not the first ad that put the name in their head.

Jobber gives you better tools than the dropdown, and most shops use none of them. This page goes through each, shows where Jobber's own tracking stops, and explains the small amount of website work that carries the trail to a paid job. It is part of our Jobber integration section; the platform-neutral version of the problem lives under tracking problems.

Six ways a client's origin reaches Jobber

Jobber's help center documents several routes into the lead source field, and one more appears in search summaries of its developer docs. Jobber's client basics article says the lead source field on clients is available on Grow, Connect and Core.

Read the precision column and the cheapest improvement is obvious: tag every link you control. A booking link in the Google profile, a request link in an email, a button on each service page, a QR code on a truck wrap; each can carry its own UTM tags, and Jobber will fill the source without anyone asking the customer anything. Our Jobber online booking page covers where those links live.

A tagging plan short enough to survive a busy season

UTM tags fail through inconsistency, not complexity. Facebook in one link, facebook in another and fb in a third become three lead sources, and the report quietly splits the channel into pieces too small to judge. These rules keep a Jobber account readable.

1. 1.Pick lowercase source names once (google, facebook, yelp, truck-wrap, mailer) and never vary them.
2. 2.Use utm_medium for the kind of traffic (cpc, organic-profile, email, print) so paid and free Google stay apart.
3. 3.Use utm_campaign for the season or offer, which Jobber reads but does not need in the source name.
4. 4.Give each website page its own request or booking link, so the page that produced the request is never a guess.
5. 5.Keep the list in a shared sheet the office uses when it enters phone leads by hand.

Why the click ID still has to live on your website

A UTM tag tells Jobber the campaign. It does not tell Google Ads which click produced a paying customer, and that is what Google's bidding needs. Google's help pages describe the method: each ad click gets a Google Click ID, you keep that ID with the lead, and once the lead turns into business the ID goes back to Google Ads along with what happened. Nothing in Jobber's help pages describes storing a click ID, and nothing we read says Jobber's embedded form picks one up from the page around it.

So for paid traffic, the website does the catching. It stores the click ID on its own server when the visitor lands. If the visitor then submits a custom request form, the site files the request in Jobber with the click ID in the note and the campaign in a client tag. If the visitor books through Jobber's embedded form instead, the site has the click ID but never sees the booking, which is why ad-heavy shops send paid traffic to pages with a custom request step. The Jobber lead forms page shows that step, and our conversion tracking setup service builds it.

Sending approved and paid work back to Google

We found no Google Ads conversion feature anywhere in Jobber's pages, so the loop closes outside Jobber. The site needs to hear when a request turns into money. Jobber's Zapier triggers include Quote Approved, Job Closed and Invoice Updated, and its API offers webhooks per app, so either route can tell the site. Google adds a dated wrinkle: since June 15, 2026, uploads of offline conversions, and of enhanced conversions for leads, go through the Data Manager API, and the Google Ads API refuses them.

1. 1

   Catch the click

   On arrival, the server keeps the click ID and the UTM tags for that visitor.

2. 2

   Carry it into Jobber

   A custom request form files the request with the click ID in the note and the campaign as a client tag.

3. 3

   Choose the moment that counts

   Usually Quote Approved for big-ticket work and an invoice event for small jobs, agreed with the owner in writing.

4. 4

   Hear it

   A webhook or a Zapier trigger tells the site the moment arrived, and the site matches it to the stored click ID.

5. 5

   Report it

   The conversion and its dollar value go to Google by whichever upload path Google accepts today, and the log records it.

Our PPC advertising team runs campaigns that bid on this data, and the Google Ads library explains costs in general terms. Shops on Housecall Pro will find the same loop, with different events, in our Housecall Pro attribution guide.

The quarterly review: Jobber's numbers joined with the ad accounts

Jobber's reports know requests, quotes, jobs and invoices; Plus adds custom reports. They do not know what each channel cost. A useful review joins the two once a quarter, by the source names you agreed. These are the columns we build, shown without numbers because only yours matter.

Building that join is the same craft as HomeService WebApp, our redesign of a contractor command center that puts open estimates and overdue follow-ups on one screen, on top of ServiceTitan rather than Jobber. Adding this tracking to the site you have is quoted in writing after a free review, from $575 depending on complexity. Our packages for a new site, tracking included, begin at $1,500, as the web design pricing page shows. If you want us running the ads too, local marketing begins at $575 a month, and Google bills the ad spend to your own account. Start with a free site audit or call (210) 346-0848.