LSA Target CPA Changes for Multi-Service Businesses

Google is replacing vertical-level LSA Target CPA controls with one campaign-level Target CPA during migration. A multi-service account that once held different targets for plumbing, HVAC, electrical, or other categories may show one target after the move into Google Ads.

Google's LSA migration announcement says vertical-level Target CPA settings are deprecated and that Google calculates and applies a unified campaign-level Target CPA. The announcement does not disclose the calculation formula, weights, or lookback period.

Save the old targets before migration, record the value that appears after transfer, and keep service-line outcomes in the business reporting layer. One campaign control does not erase differences in demand, lead price, close rate, capacity, job value, margin, or seasonality.

The control changes from service-level targets to one campaign-level setting. The business evidence should remain segmented. Without the old target inventory and service-line results, a later reviewer cannot tell whether the unified campaign shifted mix or whether demand and operations changed.

Google's migration table says the specialized campaign reports charged leads as Conversions, spend as Cost, and cost per charged lead as Cost / conv. Those campaign totals are the starting layer. Add lead category and business outcomes to judge the result by service.

Multi-service businesses rarely have one uniform lead economy. An emergency plumbing lead, full HVAC replacement inquiry, seasonal tune-up, drain cleaning call, and electrical panel request can differ in demand, lead price, qualification, booking probability, schedule fit, job value, and margin.

The same campaign Target CPA can still produce a useful blended result. Problems arise when the blend hides a service-line shift. A campaign can meet its overall cost per charged lead while sending more volume to a category with lower booking rate, limited technician capacity, or weaker contribution.

Track counts before interpreting rates. A service with three charged leads and one job can swing sharply from a single outcome. Keep sample size, date range, weekday mix, season, and operating capacity beside the service comparison.

Before migration, capture every visible vertical Target CPA with the business, Customer ID, location, service label, currency, screenshot date, and account time zone. Pair each target with 28 complete days of spend, charged leads, qualification, bookings, completed jobs, and revenue when those records are available.

Save the settings inventory separately from the performance export. A target is an account control, not an achieved cost. Keep actual cost per charged lead and cost per booked job beside the configured value so future reviewers do not confuse intent with outcome.

Record operating constraints by service. Note hours, on-call coverage, technician capacity, minimum job type, service radius, seasonal demand, financing availability, and any category paused for staffing. Use plain notes and dates without storing customer contact details.

The example below is fictional. Its calculations trace how a different lead mix changes a simple weighted planning reference. It does not represent Google's migration formula, a PrimeLSA benchmark, or a recommended Target CPA.

Assume a plumbing planning reference of $80 and an HVAC planning reference of $140. A 75% plumbing and 25% HVAC mix produces $95. A 50/50 mix produces $110. A 25% plumbing and 75% HVAC mix produces $125.

The arithmetic multiplies each service share by its planning reference, then adds the results. The three rows make the mix effect visible. Use the actual migrated Target CPA from Google Ads as the account record and actual business outcomes for decisions.

After migration, open the specialized Local Services campaign and record the campaign-level Target CPA. Compare it with the saved target map, but do not infer Google's formula from a close numerical match. A single result cannot reveal the calculation method.

Use the first 14 days to verify campaign status, services, areas, schedule, budget conversion, Business Profile connection, routing, Lead Manager, and charged-lead reporting. Add Google Ads Change history to the account record. Correct material transfer defects without waiting for a performance study.

Start the durable post period after the stabilization window. Match the pre-migration period length and weekday mix. Report campaign totals and service rows together so the owner can see whether cost movement came with a service-mix, lead-quality, booking, capacity, or revenue change.

Keep one row per account, location, service, and period. Use the same service identifier on the pre-migration export, lead record, CRM outcome, and worksheet when the systems permit it. Document any mapping from Google's lead category to the business's service label.

Calculate cost per charged lead as spend divided by charged leads. Calculate qualification rate as qualified leads divided by charged leads. Calculate booking rate as booked jobs divided by charged leads. Calculate cost per booked job as spend divided by booked jobs. Use Not available when the denominator is missing.

Add completed jobs and revenue only from the approved business system. State whether revenue follows lead date, booking date, completion date, or payment date. Multi-week jobs and seasonal service plans can make a short lead-date comparison look different from completed revenue.

A combined campaign can keep one budget, one campaign status, and shared learning across related services. It can fit businesses that share service area, hours, intake team, capacity planning, and broadly compatible economics.

Separate campaigns can make sense when the business needs distinct bidding rules, budgets, territories, schedules, teams, or economics. Google's migration documentation names separate campaigns as the option for separate bidding rules. That statement does not guarantee immediate self-service creation for every account.

Google currently says new pay-per-lead campaign creation is not directly available in Google Ads yet. Account rollout, eligibility, and support paths can limit a structure change. Confirm current availability in the signed-in account before building a plan that depends on an immediate split.

Splitting campaigns can isolate budget and bidding rules, but it also divides data, increases review work, and creates more places for settings or lead routing to drift. A narrow service line may lose useful shared volume or become difficult to judge over short windows.

Keeping services together reduces campaign overhead, but a blended result can mask category movement. Solve the reporting problem first. If service-line outcomes are visible and operations can respond, the business may not need a structural change solely because the control became unified.

Write the decision before implementation: problem observed, evidence period, affected services, proposed structure, expected measurement, owner, review date, and rollback path. Do not treat a campaign split as proof that performance will improve.

During Days 0 through 14, review transfer accuracy and lead operations. Confirm the campaign-level Target CPA, services, areas, schedule, budget, call and message routing, Lead Manager access, Business Profile connection, and account status. Keep the transition period separate from the durable comparison.

At Day 14, run a directional check for spend, charged leads, service mix, lead types, qualification, bookings, and material operational problems. Avoid declaring a long-term result from a small sample or partial week.

After 28 complete post-transition days, compare an equal pre-migration period. Add prior-year context for seasonal services. Review settings and Change history beside service-line cost, quality, booking, completed work, revenue, and capacity before changing the target or campaign structure.

A higher blended Cost / conv. with a shift toward higher-value work may still produce acceptable booked-job economics. A stable blended Cost / conv. with lower qualification or booking can signal a more serious business problem. Review counts, service mix, and operating context before choosing a response.

When one service loses volume, check demand, eligibility, category mapping, schedule, territory, capacity, and account changes. When one service receives more leads but books fewer jobs, review query and job fit, intake, answer behavior, response, pricing, and schedule availability.

Keep cause language measured. Migration timing, a unified target, seasonality, competition, staffing, service mix, and business operations can move together. State what changed, what evidence supports the observation, and which next check can reduce uncertainty.

Source review completed July 30, 2026. The deprecation of vertical-level Target CPA, application of a calculated campaign-level target, option of separate campaigns for separate bidding rules, budget conversion, reporting labels, setup availability, and stabilization guidance come from Google's LSA migration announcement.

The service-line scorecard, 28-day comparison, review cadence, structure decision table, and change-record process are PrimeLSA operating recommendations. The plumbing and HVAC example is fictional planning arithmetic. It does not describe Google's calculation method, a platform benchmark, or an expected performance result.