How did an Australian roofing company learn which Google Ads leads became paying jobs?

What was the problem?

An Australian roofing company was running Google Ads and could see the leads coming in. What it could not see was which of those leads went on to become paying jobs. The jobs themselves were managed in ServiceM8, completely separate from the ad account.

That gap matters more than it sounds. Google Ads Smart Bidding learns from the conversions you give it. If the only conversion it sees is a lead, it treats every enquiry as equally valuable and optimizes for more enquiries, whether or not they ever turn into work.

What did I build?

I built an offline conversion pipeline between ServiceM8 and Google Ads. When a job in ServiceM8 is marked as a sale, that job is sent back to Google Ads as a conversion and matched to the ad click that originally brought the customer in.

The result is that Google Ads now sees two different things: the leads it generated, and the jobs that actually produced revenue. Smart Bidding can optimize towards the second one.

How does a ServiceM8 offline conversion pipeline work?

Every pipeline of this kind follows the same basic logic, whatever tools sit in the middle:

1. 1

   Capture the click ID

   When someone arrives from a Google ad, the website stores the Google click ID (GCLID) and passes it along with the enquiry.

2. 2

   Keep it with the job

   The click ID travels into ServiceM8 with the lead, so the job always knows which ad click it came from.

3. 3

   Trigger on the sale

   When the job reaches the status the business treats as a sale, ServiceM8 notifies the pipeline.

4. 4

   Send it to Google Ads

   The pipeline uploads the job as an offline conversion against the original click, so Google Ads credits the right campaign and keyword.

The full technical walkthrough, including the choice between a Google Sheet import and server-side GTM, is in the ServiceM8 to Google Ads guide.

Why does this change how Smart Bidding behaves?

Lead-based bidding rewards whatever produces the most form fills and calls. Price shoppers and out of area enquiries count the same as serious buyers. Once paying jobs flow back as conversions, Google Ads can see which searches lead to revenue and which only lead to enquiries, and it shifts budget accordingly. For a trade business where job sizes vary a lot, that difference is the whole point of tracking.

What should you check before building a pipeline like this?

A few questions decide how smooth the build will be. Does the website already capture the Google click ID on every form and booking path? How do leads actually enter ServiceM8: by email, by an integration, or typed in by staff after a phone call? Which job status really means a sale for your business? And is there a Google Ads conversion action set up to import conversions from clicks? Answering these first avoids building a pipeline that has nothing to match.

Who is this approach right for?

• Trades and field service businesses that manage jobs in ServiceM8 and advertise on Google Ads.
• Businesses where the sale happens after the website, on the phone, on site or at quote stage.
• Accounts that want to move from lead-based bidding to bidding on real revenue.