How do you connect ServiceTitan to Google Ads so you can see real revenue?
You connect them through a shared identifier — usually the phone call or web lead — then follow that identifier into ServiceTitan's booking, job and invoice records. Google Ads reports the click and the conversion; ServiceTitan knows what the job was worth. The integration layer joins them so you can report revenue by campaign instead of conversions by campaign.
Why the two systems don't talk on their own
Google Ads is optimized around events it can observe in the browser or on the phone network: a click, a form submit, a call over a certain duration. ServiceTitan is optimized around the operational record: a customer, a booking, a dispatched job, an invoice. Neither system has the other's primary key, so neither can answer the question owners actually ask, which is whether the campaign produced money.
The join has to happen in a third place. That is what an integration layer does — it holds both identifiers, resolves them to one customer journey, and stores the result so it can be reported on.
The identifiers that actually work
In practice three identifiers carry most of the weight.
- Tracked phone numbers. Dynamic number insertion ties a call to the session, campaign and keyword that produced it. The call record then carries into ServiceTitan as the booking source.
- Web form submissions. Captured with the click identifier and UTM parameters, then matched to the customer record created in ServiceTitan.
- Customer identity matching. Phone number and service address resolve repeat customers whose original source predates the current campaign.
What you can report once it's joined
Once the journey is stitched, campaign reporting changes character. Instead of cost per conversion you get cost per booked job and cost per completed job. Instead of conversion volume you get revenue by campaign, revenue per lead by source, and the booking rate for each source — which is often where the real differences between channels show up.
It also exposes the uncomfortable cases: a campaign generating plenty of cheap leads that book at half the rate of another, or a source whose jobs complete at a much lower average ticket. Those are invisible in the ad platform. See revenue intelligence for how this gets reported.
What it cannot do honestly
No integration resolves every journey. Some customers call from a number you never tracked, some were referred and searched your brand later, some booked months after the click. A credible setup reports its own match rate and treats the unmatched portion as unknown rather than silently assigning it. Attribution answers what it can; correlation analysis covers the rest.
Topics: ServiceTitan · Google Ads · attribution · revenue
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.