How do I separate calls from Google Business Profile, Local Services Ads and organic search?

Three surfaces, three mechanisms

These look like one channel to a customer and behave like three systems to you. A tap-to-call from a map listing never touches your website, so no amount of website tagging will see it. A Local Services lead is generated and recorded inside that product before you ever hear the phone ring. Only the third case — a visitor who lands on your site — is visible to normal web tracking.

Trying to solve all three with the same tool is the usual reason operators cannot explain where their calls come from.

The Business Profile number question

The common worry is that putting a tracked number on a listing will harm local visibility because it breaks name-address-phone consistency across the web. The practical convention is to use the tracked number as the primary displayed number and keep the original number in the additional-number slot, so the historically consistent number remains associated with the listing.

This is a widely used approach rather than a guarantee, and it deserves monitoring after you make the change. Treat it as a controlled experiment on your own listing, and pair it with the rest of your local listings management so the change is made consistently everywhere rather than on one profile.

Why Local Services has to be reconciled separately

Local Services leads live in their own record set, with their own dispute and credit workflow. Matching them to jobs in your field service system is a name-and-phone join done after the fact, and it needs to happen on a schedule, not by hand at month end.

That reconciliation also pays for itself in disputes. When you can show which leads became jobs and which were out of area or the wrong service, the credit requests write themselves. We build that join as part of Local Services Ads integration.

The overlap nobody catches

A homeowner sees your Local Services listing, does not call, then finds you in the map pack an hour later and calls that number. Two systems, two records, one human. If you sum lead counts across surfaces you will overstate volume, and the overstatement is largest exactly where you are most visible.

Dedup across surfaces on phone number and address, and expect the deduplicated total to be meaningfully lower than the sum. That is not a bug in your reporting; it is the first honest number you have had.