Google Is Moving Local Services Ads Into Google Ads. Export Your Baseline and Build a Lead-Quality Loop.

Google has announced that Local Services Ads will transition from its standalone dashboard into Google Ads as specialized Performance Max campaigns with pay-per-lead goals. The first migration phase begins in August 2026 for select U.S. home and storefront service advertisers, followed by broader U.S. migration later in 2026 and remaining categories and non-U.S. accounts in 2027. Google’s migration documentation is the source of truth for timing and account behavior.

The immediate operational issue is measurement continuity. Google says historical campaign-level performance reports, including impressions, clicks, weekly spend, and ad-level performance reports, will not migrate. Lead history, contact details, message history, and older call recordings will transfer into Lead Manager. That means this is not simply an interface change. It is a reason to preserve your benchmarks and own the outcomes that happen after a paid inquiry arrives.

For local-service operators and agencies, the practical question is not only “How many valid leads did Google report?” It is “Which leads were serviceable, contacted quickly, booked, estimated, won, and profitable?”

What Google is changing, and what it is not

Google’s terminology can make this sound like a conventional Performance Max migration. It is not. Google describes the destination as a specialized Performance Max campaign type for pay-per-lead goals. The campaign remains keywordless, serves only on Search and Maps, and charges for valid leads such as calls, messages, and bookings rather than clicks. Google confirms these placement, targeting, and billing details, and Search Engine Land’s coverage independently describes the same model.

Export the reporting baseline before the dashboard changes

Google says historical Local Services Ads performance reports will not migrate to Google Ads. That limitation is explicit in Google’s documentation. Exporting now is not a Google requirement. It is the sensible way to retain a comparable record before access and reporting change.

Create one baseline file per account, service area, and meaningful service category. Save the raw Google exports, then add a simple internal outcome layer. The first preserves what the platform reported. The second tells you what the business actually did with each inquiry.

Export or document these Google-side benchmarks

• Monthly lead volume, spend, and cost per lead.
• Lead type, where available, such as call, message, or booking.
• Service category, service area, campaign, and date range.
• Invalid or disputed lead counts and any documented resolution status.
• Historical impressions, clicks, weekly spend, and ad-level performance reports that your team uses for optimization or client reporting.
• The current budget, bidding configuration, callouts, business details, and any campaign-level settings that need post-migration verification.

Add these business-owned outcome fields

The following fields are an internal operating model, not Google-required reporting. They make a valid paid lead useful for sales, dispatch, and finance decisions.

• Serviceable: Is the requested service offered in the submitted location?
• First-response time: When did a team member first attempt contact?
• Qualified: Does the job fit the business’s availability, scope, and commercial criteria?
• Booked: Did the prospect accept an appointment or scheduled next step?
• Estimate status: Not needed, sent, accepted, declined, or pending.
• Closed outcome: Won, lost, invalid, out of area, duplicate, or another reason your team can act on.
• Estimated and actual value: Separate these fields when your sales process needs both.

Use the same definitions before and after migration. If “qualified” means one thing in July and another in September, trend comparisons will be misleading even if the ad platform is unchanged.

The bidding change makes service-level data more important

After migration, Google says manual bidding, including maximum cost-per-lead settings, will no longer be supported. It also says vertical-level Target CPA will be replaced by a unified campaign-level Target CPA. When advertisers need different bidding rules for distinct verticals, Google’s stated recommendation is to use separate campaigns. See Google’s bidding guidance. PPC Land also highlights the reporting and control implications.

This makes mixed service economics harder to ignore. Consider a fictional contractor that offers emergency plumbing, routine drain cleaning, and boiler replacement. Each can produce a legitimate lead, but the urgency, staffing needs, margin structure, sales cycle, and value of the eventual job may differ. A single raw lead count cannot tell the operator whether the campaign is producing the mix the business wants.

Start with a service taxonomy that dispatch and sales teams will actually use. For example: emergency repair, scheduled repair, installation or replacement, maintenance, and unsupported request. Then decide whether each category needs distinct campaigns, distinct routing, or simply distinct reporting. Do not create campaign splits merely because the categories exist. Split when the business needs different budget, bidding, capacity, or follow-up rules.

Build a post-lead qualification workflow instead of relying on a raw lead count

A Google-reported valid lead and a commercially useful job are related but different operational concepts. Google can remain the acquisition source and Lead Manager can remain the place where transferred lead records live. The business still needs a consistent record of what happened after the call, message, booking, or website inquiry.

This is where Stepform fits. It is not a replacement for Local Services Ads, Google Ads, or Google Lead Manager. It can serve as the managed operational layer for short follow-up intake, website inquiries, structured qualification, routing, assignments, pipeline stages, and outcome reporting.

A five-step home-services estimate flow

1. Service request: Ask what the customer needs. Use choices that match the service taxonomy used in reporting.
2. Location and eligibility: Capture the address in structured fields, then check service-area coverage and any basic eligibility rule.
3. Job context: Ask focused scoping questions. For quote or repair work, allow photo uploads when images help a dispatcher or estimator understand the issue.
4. Contact and timing: Collect the preferred contact method, availability, urgency, and any access constraints that affect scheduling.
5. Confirmation and next action: Route emergency requests to immediate handling, direct suitable quote requests to booking or an estimate queue, and give out-of-area or unsupported requests a clear answer.

Use branches because the next action changes, not because a flow should look sophisticated. An emergency request might bypass a long photo-and-scope sequence. A routine estimate request may benefit from photos, preferred appointment windows, and detailed job context. An unsupported request should not enter the same sales queue as a serviceable one.

For more question-level guidance, see Stepform’s guide to quote request forms that produce better estimates.

Keep Google’s lead data and your operational data separate, but connected

Do not require every Local Services lead to complete a form. That would add friction at the wrong moment for many inquiries.

• Emergency callers: Handle the call immediately. A dispatcher can record the structured outcome after the conversation, or send only the shortest necessary follow-up later.
• Quote requests: Send a concise follow-up link when photos, dimensions, property details, or appointment preferences change the quality of scoping or routing.
• Booking leads: Use pre-appointment intake to collect details the field team needs before arrival.
• Website researchers: Use a structured service-request flow with hidden fields and UTM capture so the inquiry has declared context and source information from the beginning.
• Out-of-area or unsupported requests: Mark the reason promptly and provide a clear next response rather than leaving the lead in an ambiguous queue.

The connection can be as simple as an internal lead ID, source field, campaign field, or a documented process that joins Google’s lead record with your operational record. The goal is traceability, not forced consolidation. A manager should be able to answer: “This inquiry came from this source, was handled by this owner, reached this stage, and closed for this reason.”

For broader routing design, read how to qualify visitors before they book.

Migration preparation checklist

Before the migration notice

• Export campaign-level reporting and preserve the date ranges your team uses for benchmarks.
• Confirm who has account-administrator access and who will receive Google’s migration emails.
• Audit service categories, service areas, capacity constraints, and differences in service economics.
• Define lead stages and one owner for each handoff: new, contacted, qualified, booked, estimate sent, won, lost, invalid, and out of area.
• Review business name, physical address, and standard hours in Google Business Profile. Google says these details sync one way into Google Ads. Significant name or address changes may trigger a verification review that typically takes 24 to 48 hours and can temporarily pause a campaign. Google provides the synchronization and verification details here.
• Prepare structured callouts. Google says Better Business Bureau callouts will no longer be supported and directs advertisers to use at least six other structured callouts.

During and after migration

• Check that campaigns, daily average budgets, locations, services, callouts, and lead access appear as expected.
• Confirm that calls, messages, and bookings reach the intended people and that the team can record outcomes consistently.
• Monitor spend, response time, invalid-lead handling, and routing errors immediately.
• Avoid declaring a performance trend from the first day or two. Google advises allowing up to two weeks for migration and campaign performance to stabilize. See Google’s stabilization guidance.
• Compare post-migration performance against the exported baseline using both Google-side metrics and downstream business outcomes.

Common mistakes to avoid

Assuming “Performance Max” means network expansion

It does not in this specialized format. Google says migrated Local Services campaigns remain on Search and Maps. Plan for management and reporting changes, not a presumed move to YouTube, Display, Gmail, or Shopping.

Waiting for the 14-day email to export reports

The notice is useful for account timing, but Google says historical campaign-performance reports will not migrate. Preserve your baseline before the account is queued for change.

Saying all historical data disappears

This is incomplete. Campaign-performance reporting does not migrate, while past lead history, contact details, message history, and older call recordings transfer to Lead Manager.

Optimizing only to cost per lead

CPL remains useful, but it cannot reveal whether a lead was in area, reachable, bookable, estimate-worthy, or won. Pair acquisition metrics with the stages that determine commercial value.

Mixing unlike service types without visibility

If emergency work, maintenance, and replacement projects have different capacity or value, label them in your internal process. Then decide whether the difference warrants campaign separation, routing rules, or reporting cuts.

Making casual Business Profile changes near migration

Because business name, address, and standard hours sync one way and significant changes may trigger review, schedule nonessential edits carefully and ensure someone is watching campaign status.

Build the operational layer in Stepform

A practical setup is a Service Request Follow-Up form connected to a pipeline. Start with custom fields for source, campaign, service type, serviceability, urgency, first-contact timestamp, appointment status, estimate status, closed outcome, lost reason, estimated value, and actual revenue.

In Stepform, use conditional logic to route service type, urgency, geography, and next actions. Use structured address capture for service-area checks, file uploads for job photos, and Person or custom fields to keep records consistent. Assign a responsible owner, add notes after calls, and move each submission through a pipeline such as New, Contacted, Qualified, Booked, Estimate Sent, Won, Lost, Invalid, or Out of Area.

Automations can notify an internal team by email or Slack, send an external confirmation when appropriate, update fields, or send a webhook to an existing system. For website-originated requests, hidden fields and automatic UTM capture can preserve source context. Partial-response capture can support an approved recovery process, but should not replace prompt human handling for urgent inquiries.

The useful output is not more form submissions. It is a lead-quality record your business can use to compare paid acquisition with real operational outcomes.