A roadside tire business had run for almost a year with less than a job a day. Ad spend needed to increase, but increasing without data was hard. Three ad platforms each reported a fraction of what was happening. None could answer the only question that mattered: did the call turn into work?
GA4
Sessions and call-button taps on the site, but it often couldn't trace a
tap back to a source.
Google Ads
Calls tied to campaigns and keywords, and blind to every call it
didn't serve.
Local Services Ads
A separate console of leads, joining to neither of the other two.
Mobile commercial tire service is a business where a stranded driver searches once and calls whoever answers. Demand isn't the problem. Being easy to find at that moment is.
The owner rarely did more than a job a week. It should have been the busy season. Ads pointed at a Google Business Profile; there was no website for credibility or to place conversion tracking and no landing experience to tune.
Every measurement decision that followed depended on first having somewhere to measure.
The site exists to do one thing: turn a search into a phone call.
Everything on it points at one action: tapping to call the owner,
through a tel: link in the header, again as the main
button, and again at the end of every section.
The site was built with SEO and advertising in mind, structuring itself around the searches and ads being run for the clientelle it the business is trying to reach.
It was built to stay light. A driver on the shoulder of I-20 is on a bad connection and just wants to find help fast.
Each step was a precondition for the next.
tel: click events, which count as real conversions for a business that runs on calls.
Tracing a tap back to its source was difficult and often impossible.
Left alone, that causes two problems: the same call counted twice by two systems that each claim it, and a call counted by none of them, so it gets credited to no source. Both throw off the one number that decides budget: what a source actually returns.
The bigger gap is that all three measure calls, but the business makes money on jobs. An owner who's being asked to spend more doesn't care how many phones rang. He wants to know how much work came out of it.
I started in Google Sheets, fed by a simple Google Form, on purpose. The outcome data could only come from the person answering the phone, so the real risk was whether he'd keep filling it in. A simple tool he uses between jobs beats a better one he gives up on.
Normalize reported phone number to LSA format.
Aggregation by date, source, type, and outcome. Charts built on that data made gaps and trends visible directly.
LSA calls are exported with a time and phone number, Google Ads calls with a 1-hour time range and ad category. This is enough - start with LSA number and time matching, fallback to Google Ads category and time matching = reliable attribution, especially for relatively low call volume.
The owner records what the call was and whether it became work, the same details he still records on job forms today. No platform could supply that column.
Call data is self-reported and entered by hand, so it can be wrong. I checked it against platform call counts to catch gaps, but it isn't exact. It was accurate enough to make budget decisions with, and that was all it needed to be.
The owner didn't want to double his ad spend. Within one to two months, with calls visibly climbing and each one traceable to a source and an outcome, he was spending more than ten times the original budget across channels, and was comfortable doing it.
An owner who won't raise ad spend when he can't see what it returns is making a reasonable call with the information he has.
That decision is the best proof the system worked. Nobody multiplies their ad spend tenfold on a channel they can't see returning.
Better measurement turned up new problems. With calls sorted by outcome, I could see the leaks: some calls Google Ads counted as "conversions" weren't turning into jobs, and some searchers landed on the page and left because it didn't show what they were looking for.
That led to tighter keyword targeting and landing page changes to get more calls, then watching the outcome to make sure it actually improved.
Running the Sheets system revealed how much was tracked by hand elsewhere:
It wasn't six problems. It was six views of one event: a call comes in from a source and becomes a job, the job uses tires, produces an invoice, creates expenses, and belongs to a customer. Model that once and all six are covered.