What the Google Local Services Ads Update Means for Calls

NPI Screening, Pay-Per-Lead Billing, and What Google Now Withholds

Google admits addiction treatment and behavioral health providers into the Local Services Ads inventory only after category-specific screening that includes National Provider Identifier verification, license checks tied to the states an advertiser wants to serve, and business-entity validation. The screening layer is not cosmetic. It determines which service categories a facility can bid on, which geographies unlock, and which entity name appears on the profile the caller sees before dialing.

Billing runs on validated contacts rather than clicks. In healthcare verticals, that almost always resolves to a phone call of qualifying length and intent, with Google reserving the right to credit back leads that clearly fall outside the advertised service. For a treatment operator, the practical effect is that the cost per lead line item on a monthly invoice corresponds to live conversations the admissions team already handled, not to top-of-funnel impressions or form fills that never picked up the phone.

What Google withholds inside healthcare categories reshapes the workflow more than the billing model does. Message-based booking leads are unavailable, and platform-side call recordings are not provided. Everything Google would normally hand a home-services advertiser for coaching, dispute resolution, and lead review has to be reconstructed by the operator using tools that sit outside the ad platform and inside a compliant environment ¹.

No Booking Leads, No Call Recordings: The Measurement Gap

The absence of recordings creates a specific measurement gap: the operator is billed for a lead the platform cannot describe. Google confirms the call connected and its duration, but the content that determines whether the caller was a qualifying inquiry, a wrong number, a family member gathering information, or a competitor auditing pricing lives only in the admissions coordinator’s notes and whatever telephony system the facility routes traffic through.

That gap has two operational consequences. First, dispute workflows tighten. Without a recording, an operator challenging a billed lead is arguing from CRM notes and call-log metadata rather than audio evidence, so intake documentation standards need to be strict enough to support a credit request within Google’s dispute window. Second, quality assurance moves in-house. Coaching admissions staff on script adherence, insurance verification, and clinical fit questions requires a recording layer the facility owns and controls, subject to federal guidance that leaves telephone-recording rules largely to state law ³.

The removal of message-based booking leads matters less for admissions economics than for expectation-setting. Behavioral health inquiries rarely convert through a text thread anyway, but operators migrating from home-services LSA benchmarks or from generalist agency dashboards should not expect a chat funnel to appear inside the healthcare product.

Evoke Wellness and Why Call Volume Is Not a Compliance-Safe KPI

The January 2025 FTC complaint against Evoke Wellness offers the clearest recent counterexample to any dashboard that treats inbound calls as a self-validating metric. The FTC alleged Evoke disseminated at least 68,510 misleading Google search ads between 2021 and 2023, generating at least 3,500 calls to its call center, and the June 2025 settlement required $1.9 million in monetary relief along with prohibitions on impersonating other providers or making deceptive treatment claims ^{4, 11}. The complaint’s specific mechanism matters for LSA operators: the alleged deception concerned who consumers believed they were calling, not the volume of calls produced.

That distinction changes how a treatment center should read its own call reports. A monthly LSA invoice showing several hundred billable leads confirms that phones rang and conversations lasted long enough to qualify for pay-per-lead billing. It does not confirm that the caller intended to reach that specific facility, that the ad identity accurately represented the entity answering, or that the intake conversation aligned with what the ad promised. In the Evoke matter, thousands of connected calls became evidence for the government rather than evidence for the advertiser.

Mercury Marketing and the Identity Problem in Search-to-Call Routing

The Mercury Marketing complaint, filed by the FTC in June 2025, sharpens a question LSA operators have quietly worked around for years: what counts as impersonation when a paid placement uses another clinic’s name, brand cues, or geographic signals to route callers elsewhere? The FTC alleged that defendants used Google search ads impersonating substance-use-disorder clinics to route consumers trying to call those clinics to other clinics, and it brought the case under the FTC Act, the Opioid Addiction Recovery Fraud Prevention Act, and the FTC’s Impersonation Rule ⁵.

LSAs sit closer to that fault line than standard search ads because the format collapses ad, identity, and call action into a single tap. The profile name, license badge, service area, and phone number all appear together, and the caller reaches an admissions coordinator without an intervening landing page where clarifications could occur. If a call center answers with a brand different from the LSA profile, or if a shared call floor handles inquiries for multiple entities without clear disclosure, the identity chain a regulator would examine runs from ad impression to greeting to intake note.

The operator response is procedural. The entity listed on the LSA profile, the entity named in the admissions greeting, and the entity documented on the intake record should match, and any handoff to a different licensed facility should be disclosed on the call, not buried in a downstream referral.

Monument and the End of Casual Conversion Tracking for SUD

The April 2024 FTC action against Monument closed the door on a common measurement pattern: feeding call events, intake form submissions, and conversion signals into advertising platforms as if they were ordinary e-commerce data. The FTC alleged Monument shared consumers’ health information with third-party advertising platforms, including Meta and Google, without consent after promising confidentiality, and the settlement required the company to stop disclosing health information for advertising and to obtain affirmative consent before sharing health information with third parties for other purposes ⁶.

For LSA operators, the implication is narrow but firm. A call from a Google Local Services Ad, tied to a caller’s phone number and matched back to a CRM record indicating SUD intake, becomes health information the moment it identifies the person as seeking treatment. Piping that identifier into an ad platform’s offline conversion upload, an audience-matching tool, or a pixel-based attribution flow is the exact activity the Monument settlement addresses.

The workable path is to measure LSA performance using de-identified aggregates and internal attribution, and to keep any caller-identifiable conversion data inside systems governed by business-associate agreements and, where applicable, patient authorization.

A Compliant Call-Recording and QA Layer You Own

Because Google does not supply call recordings in healthcare verticals, the recording layer becomes an operator responsibility rather than a platform feature. That reframes vendor selection. A telephony or contact-center system used for LSA traffic should sit under a business associate agreement, because the moment a caller identifies as seeking treatment, the audio and any transcript become protected health information subject to HIPAA’s authorization and disclosure limits ^{1, 12}. Off-the-shelf sales-focused call platforms that route recordings through unrelated analytics vendors do not meet that bar.

State law sets the consent script. The FCC does not impose a general federal recording rule and defers to state statutes, which vary between one-party and all-party consent regimes ³. A facility taking calls from multiple states through a single admissions floor should default to an all-party consent disclosure at the top of every call, delivered before the caller shares clinical or insurance details. That single change resolves most interstate ambiguity without requiring a state-by-state routing tree.

The QA program those recordings feed should measure what the FTC and HHS actually examine: ad-to-greeting identity match, accuracy of any efficacy or outcome statements made on the line against the substantiation standard for health claims ⁷, and the absence of testimonial-style representations that would fall under the Consumer Reviews and Testimonials Rule ². Score sheets and coaching notes should retain those fields for the length of the applicable records-retention policy, because they are the evidence trail if a billed lead, a claim, or an ad identity is ever questioned.

Attribution Without Impermissible Disclosure

Attribution has to be rebuilt around what can lawfully leave the covered entity’s environment. The HHS OCR tracking bulletin treats identifiers tied to a healthcare interaction as protected disclosures when they reach a tracking vendor without a HIPAA-compliant basis, and it applies to call-tracking numbers and CRM webhooks, not only to website pixels ⁹. For SUD-specific calls, 42 CFR Part 2 tightens that further and generally requires patient consent before information identifying someone as seeking SUD treatment is disclosed ¹⁰.

A workable stack keeps caller-identifiable data inside systems governed by business associate agreements and pushes only de-identified aggregates outward. Dynamic number insertion tied to LSA traffic can attribute a call to the channel without transmitting the phone number, name, or intake status to an ad platform. Conversion counts, cost per qualified call, and cost per admission can be calculated internally and reported at the campaign or geography level rather than uploaded as offline conversions keyed to individual callers, which is the practice the Monument settlement addressed ⁶.

Two disciplines make that stack hold. Vendor contracts should specify what fields the call-tracking or CRM provider may receive, retain, and forward, with any advertising-platform integrations disabled by default. And any campaign-optimization report shared with an outside agency should carry aggregates only, so the measurement improvements from attribution do not recreate the disclosure the regulation was written to prevent.