This post is for clinic owners and marketing leads whose patients walk in, and who want to know whether Google Ads is sending them. It is aimed at the stage before offline conversion imports are working, when the only evidence of a visit is a click on a map, a call or a request for directions. It compares those signals as footfall proxies, shows how to test them against what actually happens at the front desk, and explains why Google's own store visit reporting is often not available to healthcare locations.
The goal is a measurement approach you can defend. Proxies are not visits. They are indirect signals, and their value depends on how closely they track real arrivals in your clinic, which you can check. The post gives a method for doing that check with your own data. It does not report results from any account.
If you are further along and can import appointment outcomes, the article on offline conversion tracking for clinics is the better route. This one is for the weeks or months before that works.
What a location asset is
A location asset attaches a clinic's address, map and travel information to an ad. Google's help page on location assets says location data comes from Google Maps and Google Business Profile, that you link the profile in Location Manager, and that locations marked closed in the profile do not show in ads. On mobile search the asset can show the address and phone number with a tappable call button, and the asset can also appear on Google Maps.
Two practical consequences follow. First, your Business Profile is the source of truth. If the address, hours or phone number are wrong there, the ads inherit the error. The Google Business Profile setup guide for doctors covers getting that right. Second, location assets support calls only when call reporting is switched on. The same help page recommends enabling it, and notes that account-level reporting must be on to see calls from location assets.
Why Google's store visit measure may not be available to you
Google can estimate store visits for eligible advertisers and report them as conversions. The conditions, listed on its page about store visit conversions, include that the stores are in a country where store visits measurement is offered, that the ads use location assets, that location assets are active and campaigns are opted in, and that clicks, impressions and foot traffic reach privacy thresholds. Eligibility is checked at sub-account level when you use a manager account.
For healthcare there is a further condition. The page says locations related to religion, sexual interests, children and certain health issues are considered sensitive and ineligible. It names "certain health issues" without defining them, so you cannot know from the page alone whether a particular specialty is affected. A clinic that serves a sensitive speciality may find that store visits never appear, and small clinics often fall below the privacy thresholds in any case.
Treat that as the baseline. Assume you may not receive Google's store visit figures, and plan a proxy measure from the start rather than waiting for one to appear. If it does appear, you can compare it against your proxies.
The candidate proxies
The signals worth considering fall into three groups. None proves a visit.
Directions requests and map interactions. A person who taps for directions has, at least, looked for a route to your clinic. This is the closest signal to travel intent. Where it is available, directions requests are often reported through the Business Profile's performance reports rather than in Google Ads. Check what your account and your profile report; do not assume the numbers will match across the two.
Calls from ads. Calls placed from a location asset are counted under Calls from ads when call reporting is on. A call is a stronger signal of booking intent than a map tap, but it is not a visit. Google's page on tracking calls from ads explains the setup, including a minimum call length.
Asset clicks or interactions. Clicks on the location asset to open the details page, with hours and photos, show interest. They are noisy: the same person may tap to check opening hours and never come.
| Proxy | Strength as a footfall signal | Main weakness |
|---|---|---|
| Directions requests | Closest to travel intent | Often reported outside Google Ads; no proof of arrival |
| Calls from ads above a length threshold | Strong booking intent | A call may lead to a booking at a different time or none |
| Location asset detail clicks | Weak interest signal | Includes hours checks and curiosity |
| Click-to-call from landing pages | Intent from people who read the page first | Counted separately; may double up with calls from ads |
Validate the proxy against the front desk
A proxy is useful only if it moves with real arrivals. You can test that with a method that needs no special software.
- Choose a single clinic location and a period of at least eight weeks. A shorter window gives you too few observations to see a pattern.
- Record weekly arrivals from paid search. Ask the reception team to record, for every new patient, how they found the clinic. Add a category for Google Ads or "saw an ad on Google". The answers are imperfect, but they are consistent over time. You may also use a booking-form field that records the source.
- Record the weekly proxy counts. For the same weeks, export directions requests, calls from ads above your threshold and location asset interactions.
- Plot the weeks side by side. For each proxy, check whether it rises and falls with the reception count.
- Test the lag. People may call in week one and arrive in week two. Compare each proxy with the front-desk count for the same week and for the following week.
If one proxy tracks arrivals reasonably across these weeks, it is a candidate to report. If none does, that is a finding too: the clinic's walk-in volume may be dominated by other sources, or your tracking of sources is unreliable.
A worked example, with invented numbers for illustration only. Suppose a clinic in Gurugram records over eight weeks that its reception logs between 6 and 14 new patients per week as "found via Google ad", and the directions requests range from 20 to 45. If the weeks with the highest directions requests tend to be the weeks with the highest reception counts, the proxy is consistent. If the directions requests rise steadily while the reception count stays flat, the proxy is picking up something else, such as people checking a route they will not take.




