How call-tracking attribution works for local search — and where it usually lies to you

Local merchants don't have a visibility problem — they have a phone-call problem. The way a customer gets on the phone is the metric a merchant can act on, and the way that call routes through the per-merchant call-tracking plate — the routed number that swaps in for every published directory number — is where attribution actually lives. Google Business Profile is the largest single dial-driver for most single-location merchants, so whatever happens between the listing card and the dial is the question that matters most.

Most plates swap a JavaScript-inserted number in for the merchant's real number on the website — the visitor lands, the plate fires, the number on the page is replaced with a routed number that forwards to the merchant's voice line, the plate logs the swap against the session. That part is uncontentious. The part that is contentiously impossible is doing the same swap on the GBP listing. The on-listing number is the published number; Google's policies require it to match the call the merchant answers, and any silent swap on the listing card is a policy violation. The honest implementation keeps the GBP number on the GBP listing itself and uses tracking numbers only on the off-GBP surface area — the website, the landing pages, the paid clicks.

So GBP shows one number — the published, real number — and every other directory gets a different, plate-routed number, and the merchant's real business line still answers both. The caller's experience is unaltered; what is altered is the plate's ability to attribute the GBP call to GBP and the Yelp call to Yelp. Each directory surfaces a different number, and the plate knows which one originated each call.

Ranking is decided by NAP consistency across the four-channel stack — GBP, Yelp, Apple Maps Business Connect, Facebook — not by whether the merchant can play back the call recording. The local pack derives ranking signal from citation consistency: every place on the web that mentions a merchant's name, address, and phone. A single stale hours string on Yelp, or a phone that drifts on Facebook when someone updates the page casually, can drop a merchant out of the local-3-pack faster than a re-recorded greeting moves them up. The merchant's own recordings don't feed the ranking signal at all — they sit on a server.

This is where the Pinmark Monday visibility report plays its small role — the place where the NAP audit and the call conversion audit meet. Same merchant, same week, two views of the same data: see a sample weekly report. Neither view, alone, answers whether the merchant is losing ranking, losing calls, or both.

There is a practical gap on the call-conversion audit that most stacks quietly hide. GBP-driven calls are easy: the caller saw the listing card, tapped Call, the dial started, and the GBP number — the published number — rang. We know it came from GBP because nothing else uses that number; confidence is high, the read is near-real-time. Organic-search calls are different, and the difference is the bug most stacks hide.

The caller searched a phrase, landed on the site, the plate swapped a JavaScript-inserted number in at session-start, and the plate logged the swap. If the session-tracking pixel loaded before the dial, the call attributes to organic search. If it didn't — and it doesn't always — the call is unattributable. Honest attribution reports do not inflate unattributable calls into "direct." Most stacks do, because the inflated number makes the merchant feel better about their spend than the website deserves.

What to do with the gap is the question the Pinmark weekly view (Pinmark pricing is per-GBP-location so a single-location merchant gets the full stack) is built to keep on one page. If the GBP-share of calls is rising while organic flattens, the answer is invest in the GBP listing — it is doing the work. If GBP is flat and organic is the swing variable, the answer is invest in the organic surface. Without both numbers on the same Monday, the answer is guesswork.