Google’s LSA Move to Performance Max: What Contractors Must Audit Now

September 26 follow-up—not a new migration announcement

The campaign can move successfully while your measurement breaks

How this follows Dispatch’s earlier Google coverage

Dispatch’s coverage has followed four related—but distinct—questions: what changes when the dashboard moves, when a particular account must act, how paid-lead economics affect a contractor’s margins, and what happens when a paid call goes unanswered. Reading those developments together is more useful than treating each one as an isolated software update.

First, audit the right product

Google’s pay-per-lead documentation describes a keywordless local-lead campaign, not a requirement to rebuild the account as conventional pay-per-click advertising. Calls are mandatory; messaging is optional. Google dates the booking option to October 2026, so do not assume it is already active in every account.

The migrated product remains limited to Search and Maps. A contractor should not interpret the Performance Max name as permission for an agency to substitute a different campaign type, expand inventory or change the measurement objective without explaining the distinction. Before discussing performance, ask the person managing the account to identify exactly which campaign is being reviewed.

There are different clocks—not one universal cutover

Google’s category schedule places selected U.S. home-service and storefront advertisers in an August 2026 first wave, with broader service-area and more complex accounts following later in 2026. Remaining categories and non-U.S. accounts follow in 2027; the schedule specifically places advanced-verification categories such as garage-door services and locksmiths in that later phase.

For an operator with several brands or markets, the practical response is an account register: administrator, customer ID, trade, market, notice date, scheduled move and responsible person. Do not assume the plumber next door, a sister branch or a different trade has the same migration date.

Preserve the baseline before comparing results

Google’s migration guide says historical campaign reports do not move, while past customer lead history does. It still describes a historical-report download page as forthcoming and advises screenshots for immediate preservation. Do not assume a promised download is already available.

Save dated copies of the reporting accessible to your account. Keep the period, market and source visible. Ask the agency for the underlying records behind its presentations, not just a slide showing a favorable average. Store lead-level customer information in an access-controlled business system, not in a public reporting deck.

Then mark the transition in your reporting calendar. Comparing a hot summer replacement week with a mild fall service week can mislead even without a platform change. Separate changes in weather, staffing, offers, territory and job mix from the platform cutover. A migration annotation is a starting point for investigation, not proof of causation.

Target CPA survives. Some of the old controls do not.

Google’s lead-quality and budget guidance says manual bidding and vertical-level bid adjustments are unsupported, but campaign-level Target CPA remains available alongside the default Maximize Conversions strategy. Removing a trade-specific control is not the same as removing every cost target. Its Charge Status field also distinguishes charged, uncharged, under-review and credited leads.

Review trade-level economics before changing account structure. A drain-clearing lead and an HVAC replacement inquiry may have different booking rates, labor requirements and revenue potential. An acceptable blended average can hide an unprofitable service line. Conversely, splitting a small account into numerous campaigns can leave each with too little activity to evaluate confidently.

Google’s best-practice guidance recommends considering Target CPA after a campaign consistently exceeds 15 leads per month and warns that a restrictive target can reduce delivery. That is Google’s recommendation, not a universal profitability threshold. Choose the structure around actual job economics and usable volume—not simply around restoring a familiar old setting.

The handoff record: what to capture and who should own it

The phone path belongs in the advertising audit

Google’s campaign-settings documentation lets advertisers configure where calls and messages are routed, select service tasks and set an ad schedule independently or sync it to business-profile hours. Treat these as operating controls, not administrative trivia.

Check the configured destination, its no-answer path and its overflow coverage. Test the business phone system directly, then reconcile actual incoming leads; there is no need to generate artificial paid-ad interactions simply to make a checklist look complete. Verify that somebody owns message responses as well as calls. A setting being enabled does not mean an employee is watching it.

The October 1 notice adds a separate reason to check responsiveness

Search Engine Roundtable’s August 25 report reproduces a Google advertiser notice saying some missed calls during business hours can become chargeable after the caller remains connected for more than 20 seconds, subject to exceptions. For a routing menu requiring a keypress, the reported timer begins after that selection. The report also includes Google’s clarification about one charge for qualifying follow-ups within 15 days, rather than a fresh charge for every callback.

Those details are attributed to the reported notice; they are not a claim that every unanswered call is billable. Dispatch covered the operational implications on September 25. The connection to the migration is management, not an asserted technical cause: billing, routing and outcome reporting need to be reviewed together.

A paid lead is not a booked job—and neither is collected profit

Google’s migration guide defines the campaign’s Conversions column as charged leads. That is an advertising event, not a count of completed, paid jobs.

Consider two hypothetical results from the same $3,000 media budget and 60 charged leads. Both show a $50 cost per lead. In one, 30 opportunities book and 18 jobs complete. In the other, 15 book and nine complete. The second operation pays twice as much in advertising per completed job even though its lead-cost headline is identical.

The illustration below is Dispatch arithmetic, not observed Google performance or a contractor benchmark. It excludes agency fees, labor, materials and other overhead. Completed jobs are drawn from the same acquired-lead cohort, not unrelated jobs finished during the month.

Illustrative only: the same $50 lead can produce very different job costs

An owner’s scorecard should therefore follow one group of acquired leads through contact, booking, completion and collection. Break the results out by service line and geography where volume supports a meaningful comparison. Define what counts as a booking, distinguish cancellations from completed work, and avoid counting a repeat contact as a second acquired customer.

Replacement estimates may mature later than urgent service calls. Keep an immature cohort visibly open rather than calling its current revenue final. When you calculate return, separate invoiced revenue from collected cash and subtract direct job costs before describing the result as gross profit.

This is also why a cheaper lead is not automatically a better lead. A service area that stretches travel time, produces small tickets or overwhelms available technicians may create attractive advertising metrics and poor operating results. The business needs a consistent definition of success outside the ad platform.

The first two weeks: investigate failures, do not chase every fluctuation

• Before the move: confirm the responsible administrator and account-specific notice, preserve accessible reports, and record a comparable operating baseline.
• At the handoff: verify budget, bidding, selected services, geography, schedule and the configured lead destinations. Treat routing failures as immediate issues—not as a learning period.
• During the first week: reconcile real calls and messages with Charge Status and internal outcomes. Record every settings change so performance comparisons have context.
• After two weeks: compare mature-enough lead cohorts and service mix before judging acquisition economics. Continue tracking jobs and collections that have not yet matured.

The real update is the operating discipline around the account

Google advises allowing up to two weeks for migration and performance stabilization. That is not a promise that every campaign will recover a particular result, and it is not a reason to ignore a broken phone destination.

The useful response is neither panic nor blind acceptance. Preserve the evidence, understand which controls changed and require the marketing report to connect to the dispatch board and the financial records.

Dispatch’s early-September coverage explained the move. The subsequent deadline, paid-lead economics and missed-call stories explain why it deserves an owner’s attention. A migrated campaign is only one part of a working customer-acquisition system. The finish line is profitable work—not a new dashboard.

Methodology

Dispatch rechecked Google’s migration, category, campaign-setting, pay-per-lead, lead-quality and best-practice documentation on September 26, 2026. Historical context links to Dispatch’s original guide and September 4 update, September 6 migration notice coverage, September 16 Roto-Rooter analysis and September 25 missed-call article. The October 1 discussion is attributed to Search Engine Roundtable’s reproduction of an advertiser notice and subsequent Google liaison clarification; it is not presented as a new September 26 announcement. No account-specific migration or performance outcome was tested for this article. The two scenarios are explicitly hypothetical, with advertising cost divided by charged leads, bookings or completed jobs from the same cohort. This follow-up adds an operator audit and measurement framework rather than republishing the original rollout announcement.