ServiceTitan to Google Ads
ServiceTitan jobs, reported back to Google Ads.
A booked call is not always a completed job. We connect the point in ServiceTitan where a job is booked, and where it is finished and paid, to Google Ads, so your bidding follows real revenue.
- 10% of ad budget, $600 a month minimum
- No contracts, month to month
- Free proposal within one business day
The workflow
What connects a ServiceTitan job to a Google Ads bid.
The identity match
GCLID is Google's name for the click identifier, and it rides along whenever a lead calls or fills out a form after clicking an ad. Dispatch schedules rarely move that fast, though, so a hashed phone number or email usually ends up doing the matching by the time the job is actually booked.
The field map
ServiceTitan tracks a call, a booked job, a dispatched technician, and a completed and invoiced job. Most HVAC, plumbing, and electrical accounts we build for use job completed and paid as the trigger, since a booked job can still cancel.
Where the data enters
ServiceTitan publishes an API for approved integration partners, which is the path used to push a completed job's value out to Google Ads' offline conversion import. What that API exposes can change between ServiceTitan releases, so we confirm current access before we build, rather than relying on documentation that may already be out of date.
Job value and membership sales
The invoiced total, including a membership plan sold on the same visit, becomes the conversion value. A hundred dollar diagnostic call and a twelve thousand dollar system replacement should not report as equal wins, and treating them that way would push your bidding toward cheap calls instead of the jobs that actually fund the business.
What we check before a trade business trusts this.
Built around completed, not just booked
A booked job that later cancels or no shows should not count. We trigger the conversion at job completed and invoiced, so a busy schedule does not quietly overstate what your ads actually produced, since a full dispatch board on paper is not the same as a full day of finished, paid work.
Emergency calls treated honestly
A burst pipe or a dead furnace at midnight is a different buyer than someone shopping quotes for next spring. We do not force both into one number if your reporting needs to tell them apart, since the search terms and the urgency behind them are not the same thing at all.
Membership plans counted, not hidden
A membership sold during a service call is real recurring revenue. We make sure it shows up in the conversion value, not lost inside a single visit's invoice total.
Re-tested after platform updates
Between ServiceTitan updating its platform and partner API on one timetable, and Google adjusting its offline conversion import rules on another, something is usually moving. Test jobs run through after either side ships a change, not on a fixed calendar of our own choosing.
How we build it.
01
Audit your job flow
The first conversation is entirely about your setup: how calls and bookings get logged today, and exactly what your ServiceTitan account's current API access will let a build like this touch.
02
Build and test the feed
A dispatch board full of booked jobs proves nothing on its own, so the build watches specifically for job completed and invoiced. We run several of your own finished HVAC, plumbing, and electrical jobs back through it and compare the totals against what actually got invoiced.
03
Hand off a plain record
Dispatch keeps a copy of the specifics: which status counts, what a job is worth once it reports, and where to look first if a number ever seems wrong.
ServiceTitan and Google Ads conversions, answered.
Completed and invoiced, in most cases. A booked job can still cancel or no show, and we do not want Google Ads learning from work that never actually happened, especially on a schedule that fills up fast and empties out just as quickly.
That is the normal path for a lot of emergency calls. GCLID is not part of a phone conversation, so ServiceTitan's own call tracking and a hashed phone number carry the weight of the match instead.
Yes, when the membership is sold and recorded as part of the same job. We include it in the conversion value so recurring revenue is not invisible to your ad account.
It needs someone who can grant API access on the ServiceTitan side, which is often an office manager or owner, not necessarily a developer. We tell you exactly what access we need before we start, and we do not ask for anything beyond what the build actually requires.
We plan for it rather than treat it as a surprise. Whenever ServiceTitan's partner API ships a change, jobs get run through the feed again so we can confirm the numbers before anyone leans on them.
Connect a finished ServiceTitan job to the ad that brought it in.
Tell us how jobs move through ServiceTitan today, from first call to invoice paid, and whether you sell membership plans. You will have a free, written proposal back within a business day.