--- title: "Google LSA Migration: Call Recordings Expire in 60 Days - Carlos Arias" description: "The Google LSA migration leaves your call recordings in the Ads API for 60 days. How to capture and score that audio before Google deletes it." url: "https://carlosarias.com/blog/law-firm-marketing/google-lsa-migration-your-law-firm-s-call-recordings-are-api-data-for-60-days" --- [Law Firm Marketing](/blog/categories/law-firm-marketing) # Google LSA Migration: Call Recordings Expire in 60 Days The Google LSA migration leaves your call recordings in the Ads API for 60 days. How to capture and score that audio before Google deletes it. [Carlos Arias](/blog/authors/carlos-arias) · October 8, 2026 · 7 min read ![An ink drawing of a corded phone handset, a sound waveform, and a cloud trailing circuit lines.](/_astro/cover.CfF3DNk7_Z1JptJv.webp) *An ink drawing of a corded phone handset, a sound waveform, and a cloud trailing circuit lines. AI-generated illustration by Carlos Arias .* Here is the part of the Google LSA migration almost nobody is writing about: your law firm’s call recordings are API data, for 60 days. Every Local Services lead you have been charged for already exists as a structured record in the Google Ads API, carrying a timestamp, a call duration in milliseconds, a charged flag, a credit state and a recording URL. Google retains recordings and messages in legal verticals for 60 days. Then they are gone. Most coverage of this migration is a list of losses. This is the asset underneath it. I am not an attorney and none of this is legal advice. I build the marketing and intake infrastructure that sits behind the phone number, and I have shipped production AI on top of it since 2022. ## What the Google LSA Migration Confirmed, and What It Hasn’t Google announced on July 20, 2026 that Local Services Ads is folding into Google Ads as a Performance Max campaign with pay-per-lead goals, starting with a phased rollout in August 2026 for a small group of US advertisers. Pay-per-lead billing survives. The placement in Search and Maps survives. The standalone LSA dashboard does not. ### The Reporting That Doesn’t Come With You Read this next part twice. Your historical lead records move into the new Lead Manager, but aggregate campaign performance reporting does not migrate. Spend history, lead counts, cost-per-lead trends, service-level breakdowns: export them or lose them. ### Legal Still Has No Date Not confirmed, as of today: a migration date for legal categories. Google’s own transition page describes a staged rollout that begins with home and storefront service categories in the US and reaches remaining categories and non-US accounts through 2027. Legal is not named with a date. Anybody selling your firm a legal migration date is guessing, and I would rather tell you that than fill the gap with a confident number. ### One Target CPA for Every Matter Type One more change matters more than the interface. Manual cost-per-lead bidding per service category is going away, replaced by a single campaign-level Target CPA, with Maximize Conversions as the default and a recommendation to wait until the campaign produces more than roughly 15 leads a month before you set a target. So the most consequential number in your paid acquisition is about to be one number, set by you, for every matter type at once. If you do not know what a car accident lead is worth versus a contested custody inquiry, that number is a guess with a budget attached. ## The 60-Day Clock Running on Your Call Recordings Google’s Local Services documentation puts retention for recordings and messages in legal verticals at 60 days, and notes that recordings and messages are not offered at all for health care verticals or tax specialists, per Google’s lead management guidance. Google is already making per-vertical decisions about this data. Legal gets 60 days. Sit with the arithmetic. Industry benchmarks had legal LSA leads running roughly $195 to $250 each in early 2026. A firm taking 50 charged leads a month is letting the primary evidence of about 100 paid intake conversations expire every two months. Not the lead row. The audio. ## The Fields You Actually Get Two resources carry the weight. local_services_lead gives you lead_charged, lead_status, credit_details.credit_state, lead_type, category_id, service_id, contact_details and creation_date_time. local_services_lead_conversation gives you the per-event detail, documented in the Local Services campaigns guide: `SELECT local_services_lead_conversation.lead, local_services_lead_conversation.conversation_channel, local_services_lead_conversation.participant_type, local_services_lead_conversation.event_date_time, local_services_lead_conversation.phone_call_details.call_duration_millis, local_services_lead_conversation.phone_call_details.call_recording_url, local_services_lead_conversation.message_details.text FROM local_services_lead_conversation` Duration in milliseconds, per call, joined to whether Google charged you. That pairing is the whole reason this is worth building. Google’s own lead rules already treat a missed call as chargeable, and the threshold arrived in the notice Google emailed advertisers on August 24, 2026 under the heading “Upcoming changes to lead charge policy”: from October 1, 2026, a caller who holds past 20 seconds during your business hours is a billable lead whether anyone picks up or not, per the policy notice. I unpacked the billing math when missed LSA calls started costing law firms twice. The API is where you watch it happen instead of arguing about it. ### Build Against v25, Not Last Year’s Fields Build against current fields, not last year’s blog posts. v25, released July 22, 2026, removed ContactDetails.email from LocalServicesLead and added phone_number_extension. There is no consumer email address coming out of that resource anymore. Separately, v24.2 on June 24, 2026 added pmax_campaign_settings.local_services_enabled, which is how you will identify a Local Services Performance Max campaign once your account moves. v25.2 shipped September 23, 2026. ## What the API Will Not Do, and Why I Won’t Pretend Otherwise The recording URL comes back in the response. A URL is not a download. Google’s documentation says you must sign in with an email address that has at least read-only access to the Google Ads client account that owns the campaign the lead belongs to. In December 2024, the Google Ads API team told a developer on the official forum that direct API access to Local Services recording downloads is not supported, and contrasted it with message attachments, where message_details.attachment_urls can be fetched using authorized Cloud project credentials. Attachments, yes. Audio, no. My own read is that an authenticated audio path will land eventually, because the metadata is already there and the demand is obvious. I am not going to publish an endpoint that does not exist today. Here is the honest architecture instead: the API for the ledger, an authenticated browser session for the audio file. Uglier than the version in a vendor deck. It works, and it does not depend on a feature announcement. ## How I’d Build the Pull 1. Read-only access first. OAuth credentials and a developer token against the manager account that owns the LSA campaigns. Read-only is enough for every step below. 2. Run it daily. Not weekly, not monthly. With a 60-day horizon, a monthly job means a third of your evidence is already at risk before the job fires. 3. Join conversations to leads on the lead resource name, then store the row with lead_charged and credit_details.credit_state alongside the duration. 4. Capture the audio in the same pass, through an authenticated session, into storage you control, named with the lead ID. That file is now yours past day 60. 5. Transcribe, then score against a rubric you wrote. Matter type, jurisdiction, whether a human answered, seconds to a human voice, whether anyone collected a callback number, whether the caller was ever told what happens next. 6. Write the score back into the CRM record for that matter, so intake sees it where intake already works. Step 5 is where firms reach for an agent and let it off the leash. Don’t. A model that labels the matter type and flags a dropped handoff is doing production work. A model deciding whether you take the case is not a system, it is exposure, which is why human review stays wired into the agents I ship. ## What the Score Actually Buys You Three things, in the order they usually pay off. Intake leaks become evidence. “We answer our phones” is an opinion. A table showing 18 charged legal leads last month where the recording contains hold music and a voicemail greeting is a fact, with timestamps, and it ends the conversation in about four minutes. This is the same failure I traced in why law firm leads die after the click, except now you can prove which calls died and when. Lead quality gets rated against something. Google moved to automated lead credits rather than manual disputes, so your leverage is no longer the dispute form. It is knowing, by category_id and service_id, which services actually produce signable matters, because that is what your single Target CPA will be pointed at. And the bid stops being folklore. Transcribed, scored, joined to signed matters in your CRM, you get a real value per lead per service. That is the input Performance Max is going to ask you for. ## The Constraint I’m Not Going to Pretend Away This does not make your phone ring more. It makes the money you have already spent legible, and it preserves evidence that currently evaporates on a 60-day timer. It also will not be free of friction. The audio capture is a session-authenticated workaround, not a supported endpoint, and Google could change it. Recording and transcribing caller audio carries consent and confidentiality considerations that are your firm’s call and your ethics counsel’s call, not mine. I will build the pipeline. I will not tell you it is risk-free, and I will not tell you what your bar rules permit. ## Questions I Get Does this only matter if my account has already migrated? No, the opposite. The 60-day recording clock runs today, under the current dashboard. Migration is the deadline for your aggregate reports, not for the audio. Can’t I just download recordings from the lead inbox? You can, one at a time, for as long as the standalone interface exists. At 50 leads a month that is someone’s afternoon, every month, done inconsistently. The point of the API is that the ledger is already structured. What if Google ships a real audio endpoint next quarter? Then step 4 gets simpler and nothing else changes. The rubric, the storage and the CRM write-back are the durable parts. I built it in that order deliberately. Is this worth it for a firm taking 10 leads a month? Honestly, probably not as an engineering project. At that volume, listen to all ten yourself this month and write down what you hear. The build earns its keep when the volume exceeds what a principal will actually review by hand. ## If This Is Your Problem Pull one number before you do anything else. Count your charged legal LSA leads from the last 60 days, then count how many of those recordings anyone at your firm has listened to. If the second number is near zero, you are buying evidence and throwing it out. If you want a second set of eyes on the pipeline behind your Local Services leads, write me at hi@carlosarias.com. Information first, no deck. I am a marketing engineer, not an attorney. Nothing here is legal or ethics advice, and no outcome is promised. Platform behavior and API fields were verified against the sources linked above on October 9, 2026; both change often, so re-check before you build. Tags [#Law Firm Marketing](/tags/law-firm-marketing/)[#Local Services Ads](/tags/local-services-ads/) #Google Ads Api [#Intake Automation](/tags/intake-automation/)[#Local SEO](/tags/localseo/) Share Written by [Carlos Arias](/blog/authors/carlos-arias) Marketing Engineer for law firms. I combine digital marketing, software, data, automation and AI to improve the whole system — from first click to signed case. On this page - What the Google LSA Migration Confirmed, and What It Hasn’t - The Reporting That Doesn’t Come With You - Legal Still Has No Date - One Target CPA for Every Matter Type - The 60-Day Clock Running on Your Call Recordings - The Fields You Actually Get - Build Against v25, Not Last Year’s Fields - What the API Will Not Do, and Why I Won’t Pretend Otherwise - How I’d Build the Pull - What the Score Actually Buys You - The Constraint I’m Not Going to Pretend Away - Questions I Get - If This Is Your Problem ## Continue reading [Law Firm Marketing](/blog/categories/law-firm-marketing) · September 8, 2026 [### Missed LSA Calls Could Cost Your Law Firm Twice From Oct 1](/blog/law-firm-marketing/missed-lsa-calls-could-cost-your-law-firm/) Missed LSA calls become billable leads on October 1, 2026. Here is how to fix your intake path before Google starts invoicing the ones you never answered. Carlos Arias · 8 min [Law Firm Marketing](/blog/categories/law-firm-marketing) · September 11, 2026 [### How Law Firm Marketing Actually Works: The Systems Guide (2026)](/blog/law-firm-marketing/law-firm-marketing-systems-guide-2026/) Law firm marketing is not posts and ads — it is the system from search to signed case. SEO, local, paid, website, intake and measurement, with the places firms lose cases they already paid for. Carlos Arias · 18 min [Law Firm Marketing](/blog/categories/law-firm-marketing) · October 5, 2026 [### Law Firm Blog Output Doubled. Page-One Rankings Fell 82%](/blog/law-firm-marketing/a-law-firm-doubled-its-blog-output-its/) A law firm doubled its blog output and its page-one rankings fell 82%. Here is what the audit found, and what a law firm should publish instead. Carlos Arias · 9 min ## Stay in the loop. One email when it’s worth it — new posts and updates, no spam. Thanks — check your inbox to confirm. Free. Unsubscribe in one click.