What Can Jobber Actually Track for Marketing?
Jobber provides customizable lead source fields, automatic UTM parameter capture on web booking forms, and basic lead reports that show which sources generate the most requests. It's cleaner data than most CRMs provide — especially the UTM capture, which removes the human error of CSR tagging for form submissions.
Jobber's UTM capture is its strongest marketing feature. When a lead submits a request through your Jobber-powered booking page, the system automatically reads the UTM parameters from the URL — capturing the campaign, source, medium, and even keyword that brought them there. This means digital form submissions get accurate source data without relying on a CSR to ask and tag correctly.
The lead source field is customizable, so you can create categories that match your actual marketing channels: Google Ads, Facebook, LSA, Angi, mailer, referral, yard sign, etc. Lead reports then show how many requests came from each source over any time period.
- Customizable lead source fields matching your actual marketing channels
- Automatic UTM parameter capture on Jobber web booking forms (no CSR entry needed)
- Lead reports showing request volume by source over any time period
- Source tracking on both form submissions and manual entries
- Clean, simple interface that your team will actually use
How Do You Set Up Lead Tracking in Jobber?
Setup involves three parts: configuring your lead source list to match your marketing channels, adding UTM parameters to all your digital campaign links, and training your team to tag phone calls and walk-ins correctly. The digital side (UTMs) is automatic once set up; the phone call side still requires manual entry.
Start by customizing your lead source dropdown to match every marketing channel you use. Don't use generic categories like 'Online' or 'Advertising' — create specific sources like 'Google Ads - AC Repair,' 'Facebook - Spring Campaign,' 'Mailer - Zone 3.' The more specific your categories, the more useful your reports.
For digital campaigns, add UTM parameters to every link. When someone clicks your Google Ad and lands on your Jobber booking page, the UTMs automatically tag the lead with the exact campaign, ad group, and keyword. We've written a complete setup guide covering every detail.
- Step 1: Customize lead source dropdown with specific channel names (not generic categories)
- Step 2: Add UTM parameters to all digital campaign links (Google Ads, Facebook, email)
- Step 3: Train CSRs and dispatchers to tag phone calls and walk-ins correctly
- Step 4: Review lead reports weekly to catch missing or incorrect tags
- Pro tip: name sources consistently — 'Google Ads - AC Repair' not just 'Google'
Where Does Jobber's Marketing Tracking Fall Short?
Jobber can't track phone calls (your primary conversion channel), can't connect lead source data to ad spend, gives single-touch credit to multi-touch journeys, and shows lead counts but not revenue per channel. You know where leads come from, but you don't know which channels produce profitable booked jobs.
The phone call gap is Jobber's biggest marketing blindspot. UTM capture only works for form submissions through your booking page. But for most home service contractors, 60-80% of conversions are phone calls — and Jobber has no way to automatically attribute those calls to the marketing channel that drove them. You're back to relying on CSRs asking 'how did you hear about us?'
Even with perfect lead source data, Jobber can't answer the question that matters most: what's my cost per booked job by channel? Jobber sees leads. Your ad platform sees cost. But nothing connects the two. You end up with a lead report in Jobber and a cost report in Google Ads, and you're doing math in a spreadsheet trying to make them match.
- No phone call tracking: 60-80% of conversions are calls that Jobber can't auto-attribute
- No ad spend connection: Jobber sees leads but not how much you paid to get them
- Single-touch attribution: multi-channel customer journeys get credited to one source
- Lead counts, not revenue: you see how many leads per source but not booked job revenue
- Manual phone tagging: CSRs skip the question or pick wrong source 30-50% of the time
- No keyword-level data: you know 'Google Ads' but not which keyword drove the lead
What's the Difference Between Knowing Lead Source and Knowing ROI?
Lead source tells you where a lead came from. ROI tells you whether that channel makes or loses money. Jobber gives you lead source. ROI requires connecting four data points: ad spend (from your ad platform), leads (from Jobber), booked jobs (from Jobber), and collected revenue (from Jobber) — per channel, per campaign, per keyword.
Here's an example: Your Jobber lead report shows Google Ads generated 40 leads and Facebook generated 25 leads this month. Looks like Google is your best channel. But when you add the data Jobber can't show — Google cost you $4,000 (=$100/lead) and Facebook cost you $1,500 (=$60/lead). Facebook leads are cheaper. But which ones actually became booked jobs?
That's the missing piece. If 20 of the 40 Google leads became booked jobs ($200/booked job) and 15 of the 25 Facebook leads became booked jobs ($100/booked job), Facebook isn't just cheaper per lead — it's cheaper per booked job by half. Without connecting Jobber's lead data to ad spend and job outcomes, you'd have increased Google spend and cut Facebook. The opposite of the right move.
- Lead source: 'This lead came from Google Ads' (Jobber can do this)
- Cost per lead: 'This Google Ads lead cost $100' (requires ad platform data Jobber doesn't have)
- Cost per booked job: 'This booked Google Ads job cost $200' (requires connecting leads to jobs to spend)
- Revenue ROI: 'Google Ads generated $45K revenue on $4K spend' (requires full-funnel connection)
- Jobber gives you step 1. You need all four steps to make smart marketing decisions.
How Does Rivet Close the Gap for Jobber Users?
Rivet enriches Jobber's lead source and UTM data with phone call attribution, ad spend data, and full-funnel revenue tracking. You get a single dashboard showing cost per booked job by channel, keyword-level attribution, and multi-touch journey mapping — turning Jobber's basic lead reports into an actionable marketing intelligence system.
Rivet adds the three things Jobber is missing. First, phone call attribution: using call tracking numbers integrated with your ad platforms, every phone call is automatically attributed to the marketing channel that drove it — no CSR tagging needed. Second, ad spend connection: Rivet pulls cost data from your Google Ads, Facebook, and LSA accounts and matches it to Jobber's lead and revenue data.
Third, multi-touch journey tracking: when a homeowner sees your Facebook ad on Monday, Googles your company name on Wednesday, and calls your tracking number, Rivet credits both Facebook (awareness) and Google (conversion) instead of giving 100% credit to Google. The result is a clear, accurate view of which channels actually produce profitable booked jobs.
- Phone call attribution: every call automatically matched to the right marketing channel
- Ad spend connection: cost data from Google Ads, Facebook, LSA matched to Jobber revenue
- Multi-touch tracking: credit both awareness channels and conversion channels
- Cost per booked job dashboard: the metric Jobber's reports can't calculate
- Keyword and creative-level data: see which specific ads drive the best jobs
- Works alongside Jobber: your team keeps using Jobber exactly as they do now
Real Example: A Plumbing Company Using Jobber + Rivet
A 6-tech plumbing company spending $3K/month on Google Ads and $1K on Facebook. Jobber showed: 'Google Ads: 35 leads, Facebook: 18 leads.' With Rivet: 'Google Ads: 35 leads, 14 booked jobs, $42K revenue, $214 cost per booked job. Facebook: 18 leads, 11 booked jobs, $38K revenue, $91 cost per booked job.' Facebook produced more revenue at less than half the cost per job.
Before Rivet, this contractor was considering cutting Facebook because Jobber showed fewer leads from that channel. After seeing the full attribution data, they realized Facebook leads were converting at 61% vs Google's 40% — and at a much lower cost per booked job. They shifted $1K from Google to Facebook and increased total booked jobs by 15% the following month.
The multi-touch data also revealed that many 'Google' leads in Jobber had actually interacted with a Facebook ad first. Cutting Facebook wouldn't just lose the direct Facebook leads — it would reduce the Google leads that Facebook was quietly generating through brand awareness.
- Jobber alone: Google Ads looks like the clear winner (35 leads vs 18)
- With Rivet: Facebook has half the cost per booked job ($91 vs $214)
- Facebook conversion rate: 61% of leads became booked jobs vs Google's 40%
- Budget shift of $1K from Google to Facebook increased booked jobs by 15%
- Multi-touch data prevented cutting the channel that was feeding Google leads
How Does Implementation Work With Jobber?
Implementation takes 2-3 weeks: audit your current lead source setup, clean up your lead source categories and UTM naming conventions, connect call tracking and ad platforms to Rivet, and build your custom ROI dashboard. Jobber integration is simpler than ServiceTitan because there's less configuration involved.
Week 1 is the audit: we review your current lead source setup, UTM naming conventions, and identify where attribution data is breaking or missing. This often reveals quick wins — like missing UTM parameters on your highest-spend campaigns or inconsistent lead source names that split data across multiple categories.
Weeks 2-3 are connection and dashboard building: we set up call tracking numbers for each channel, connect your ad accounts to Rivet, and build a dashboard customized to your business. Most Jobber users are seeing actionable data — including their first accurate cost-per-booked-job report — within 3 weeks.
- Week 1: Audit lead sources, UTM setup, and identify attribution gaps
- Week 2: Connect call tracking, ad platforms, and Jobber data to Rivet
- Week 3: Build custom ROI dashboard and train your team
- Simpler implementation than ServiceTitan (less configuration required)
- Your team keeps using Jobber exactly the same — zero workflow changes