From click to paid job
We follow the money, not the paperwork
A lead is a form fill or a ringing phone. It tells you almost nothing. This page explains, step by step, how we track an enquiry through to the job you got paid for, and what we do with that number once we have it.
Why "14 leads" is a bad number
Not every lead is a job. Some are wrong numbers. Some are price shoppers who were never going to book. Some are 40 miles outside the area you cover. Some are a €90 callout and some are a €4,000 install. Counting all of them as "1 lead" hides the only difference that matters to you.
What most agencies show you
14
leads
You don't know which ones paid.
What you see with LeadVine
| Keyword | Spend | Jobs | Revenue |
|---|---|---|---|
| boiler replacement | €340 | 3 | €6,200 |
| emergency plumber | €190 | 4 | €1,050 |
| bathroom fitting | €260 | 1 | €3,400 |
| Total | €790 | 8 | €10,650 |
Example figures, to show the shape of the report.
The trap that makes ads quietly worse
Google Ads bids for you automatically, and it learns from whatever you tell it a success looks like. Tell it that a form fill is the win, and it goes and finds more people who fill in forms. The monthly report keeps improving while the work coming through the door gets smaller. This is very common, and it is hard to spot from a lead count alone.
You tell Google: "a form fill"
So Google goes looking for
- Price shoppers
- People outside your area
- Small callouts
You tell Google: "a €4,200 job"
So Google goes looking for
- Bigger jobs
- People in your area
- People ready to book
The €4,200 job is an example figure, used to show how the two ends differ.
The five steps
-
We tag the click
Every visitor who arrives from one of your Google ads carries an invisible click ID. We store it the moment they land on your site, and we keep it with them while they read your pages.
-
We track the call
The phone number on your site swaps per visitor. When the phone rings we can say which ad, which search term and which page produced that ring. The call recording is kept, so you can listen back.
-
We stamp the form
A form submission is saved with the same click ID, plus the page they landed on and the page they filled the form in on. Nothing is guessed after the fact.
-
The job outcome comes back
When that enquiry turns into a booked and paid job, the value of the job comes back to us from your CRM. Something has to record whether a job was won and what it was worth, so we connect to your system as part of setting you up.
-
We tell Google the real number
That job value is sent back to Google Ads against the original click. Google stops treating a form fill as the win and starts bidding for the kind of person who paid you.
Step five is the one that matters. The first four are basic tracking, and most agencies will tell you they have them. Sending the value of the finished job back to the ad that produced it is the part almost nobody does.
Why most agencies cannot do this
It needs four things sitting in one system: the ads, the website, the call tracking and the job outcome. An agency that only runs your ads never sees what the job was worth. A CRM that holds the job value never sees the ad click. The two ends never meet, so nobody joins them up. We build and run all four, which is the only reason we can.
- Your ads
- Your website
- Call tracking
- The job outcome
All four in one system. That is the whole trick.
Being straight with you about where this stands
Live and running today: the click ID is captured on every form and every call, call tracking records which page and which search term produced each ring, we receive job outcomes from a CRM over a secure connection, and completed jobs are uploaded back to Google Ads automatically.
What this needs from you: somewhere that records whether a job was won and what it was worth. We connect to your CRM as part of setting you up. If you do not use one, we will work out with you how job outcomes reach us before your ads go live.
This is how the system is built and what it is for. We are not going to make up a percentage and print it on this page.