How-To Guide 3 min read

How to Send ServiceTitan Data to Google Ads as Offline Conversions

Learn how to connect ServiceTitan revenue data to Google Ads offline conversions using The Upload Offline Conversions App's Fusion Relays. Close the loop between ad clicks and completed jobs.

Last verified: 2026-11-09

Your call tracking report shows which ad brought in a lead. ServiceTitan shows what happened to the job. To report revenue back to Google Ads, you need to connect those records without confusing the lead date with the job date.

TUOCA Fusion Relays are designed for that matching work: attribution comes from an earlier tracked lead; value and conversion time come from the later business event. Before configuring a relay, check that your source connections expose the event and fields you need.

Start with one real job

Find a completed job and the original tracked call. Check these details before setting up automation:

RecordWhat to inspectWhy it matters
Earlier tracked leadPhone/email, lead time, Google click ID where availableSupplies attribution and a shared identifier
ServiceTitan outcomeStable record ID, customer contact data, event date and revenueDefines what happened and what it was worth
Google Ads actionIntended business outcome, value/currency settings and conversion windowDetermines where the conversion belongs

For example, a call on April 1 and a completed job on April 10 can share the customer’s phone number. The conversion should describe the April 10 outcome. A matching phone number alone does not prove an ad interaction was eligible.

Connect ServiceTitan with the right credentials

ServiceTitan’s authentication documentation describes two steps: exchange the client ID and client secret for an access token, then use that token and the app key to call the resource API.

For the TUOCA connection, have these ready:

  • App key identifying the application.
  • Tenant ID identifying the ServiceTitan customer account.
  • Client ID and client secret for the intended integration or production environment.
  • Approved API access and scopes for the data the connection needs.

The connection may be labeled API key in TUOCA, but app key plus tenant ID alone is insufficient. TUOCA’s ServiceTitan service obtains the OAuth token internally. This is not a normal “sign in with ServiceTitan” popup.

Ask your tenant administrator to confirm the application connection and access. ServiceTitan’s app-key and client-key FAQ explains that relationship. Keep credentials in the connection setup, never in screenshots or shared exports.

Configure the conversion you actually want

Connect your call tracking source and ServiceTitan, then configure a Fusion relay with the tracked lead as attribution source and the supported job outcome as conversion source.

Fusion matches normalized phone or email data. Review the matching priority, lookback and first/last-touch choice against your sales process. A long matching lookback does not extend Google’s upload eligibility window.

Decide whether your outcome means job completed, invoice issued or invoice paid. These are different events. Inspect the fields exposed by your connection instead of assuming a field named “total” means collected revenue. Confirm whether the amount includes tax, deposits or adjustments, and avoid uploading both a job total and its invoice as two sales.

Validate before activating

Use dry-run mode to inspect a small set of known jobs. Include a matched job, a job with no earlier tracked lead and a record with missing contact data. Check the source event time, value, currency, destination action and identifiers before enabling recurring sends.

If a record does not match, investigate the source data. Do not assume TUOCA sends every organic or referral job using hashed contact data. Enhanced conversions has its own setup, consent and matching requirements; it does not guarantee attribution or bypass upload deadlines.

After activation, inspect execution history and Google Ads import results. A successful request is only one checkpoint; compare the imported outcome with the job you started with.

Make this a recurring workflow

If you are repeatedly exporting calls, finding the corresponding jobs and preparing uploads, that is the work Fusion Relays can bring into one configured workflow. Start with one supported source pair and one conversion action, validate it, then expand. Compare TUOCA plans for Fusion availability.

ServiceTitan authentication guidance checked November 9, 2026. Confirm source event availability for your account during setup.

Frequently Asked Questions

An app key, tenant ID, client ID and client secret for the intended environment, plus the required API access. ServiceTitan uses OAuth 2.0 client credentials; an app key and tenant ID alone are not sufficient.

In this workflow, an earlier CallRail or CallTrackingMetrics lead supplies the click ID and ServiceTitan supplies the later job outcome. Inspect your actual records: neither the presence of a phone number nor a matching job guarantees usable Google Ads attribution.

No. Matching requires a shared identifier and an eligible earlier lead within the configured lookback. Missing or changed contact details, shared phone numbers and absent click IDs need investigation. Do not assume an unmatched job is automatically uploaded using enhanced conversions.

Stop Guessing. Start Proving ROI.

TUOCA connects your CRM and call tracking data directly to your ad platforms. Set up in minutes.