Can I use my own call tracking number with Local Services Ads?
Not inside the ad itself. Google supplies its own forwarding number for Local Services listings, so dynamic number insertion and swap-based call tracking do not apply the way they do on your website. What you can do is forward Google's number into a tracked line behind it, and pull the lead records and call recordings that Google retains through the Local Services account or its API before the retention window expires.
Why the usual playbook does not transfer
On your website, dynamic number insertion swaps the displayed number per visitor so the call carries session, campaign and keyword context. The Local Services unit is rendered by Google, not by you. There is no page to insert anything into, and the displayed number is Google's.
This is not an oversight. It is how Google identifies which calls are billable and how it measures your responsiveness. Any workaround that hides the call from Google would also break billing and ranking, which is why none exist.
Two workable approaches
Most operators end up doing both: the forwarded line for routing and immediacy, the API pull for the authoritative lead record and the Google lead identifier.
- Forward into a tracked line. Point Google's forwarding destination at a number in your call tracking or phone system rather than at the front desk directly. You get your own recording, your own routing rules, and your own timestamps, and Google still sees a connected call.
- Pull from the source. Google retains LSA lead records and, in supported markets, call recordings for a limited period. Pull them programmatically on a schedule so they land in your own store before they age out.
Retention is the trap
Recordings do not live in your Local Services account forever. If your quality review process runs quarterly, a meaningful share of the calls you want to review will already be gone. Anyone who has tried to investigate a complaint from two months ago has discovered this the hard way.
Set up the pull before you need it. Once the audio is in your own storage, it can feed call analysis on your schedule rather than Google's.
Consent and recording obligations do not change
Recording rules vary by state and by the location of both parties, and they apply whether the recording is made by Google, by your phone system, or by a tracking vendor. Some states require all-party consent; others do not. Announcements, retention policies and access controls are all part of the picture.
Treat this as a legal question rather than a technical one and confirm your setup with counsel who knows the states you operate in. The engineering side — where audio is stored, who can hear it, how long it is kept — should be designed around whatever answer you get, which is part of how we approach systems integration generally.
Topics: call tracking · call recordings · DNI · API
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.