Why Your LSA Budget May Look Different After Migration

Your LSA budget after migration may look smaller because Google changes the time unit. Google divides the historical average weekly budget by seven and displays the result as an average daily budget. Google then multiplies that daily average by 30.4 to set the monthly spending limit.

Google's LSA migration announcement supplies both formulas and says demand can produce daily spend fluctuations. The announcement also says monthly billing will not exceed the daily average multiplied by 30.4. Compare equivalent units before calling the new number a cut or increase.

Record three values: the old weekly average, the migrated daily average, and the calculated monthly limit. Then review actual Cost for a complete period. Use the budget setting for the limit and Cost for the amount the campaign spent.

Use two equations. Old weekly average divided by seven equals the migrated average daily budget. Average daily budget multiplied by 30.4 equals the monthly spending limit.

The table uses PrimeLSA arithmetic based on Google's formulas. The dollar amounts are examples, not recommendations or forecasts. Round only for display and keep the full calculated value in the audit file when the interface permits cents.

A $700 weekly average becomes $100 per day and a $3,040 monthly limit. The same unit conversion turns $2,100 per week into $300 per day and a $9,120 monthly limit. Neither example predicts lead volume or actual spend.

An average daily budget is a campaign setting. Daily Cost is the recorded campaign charge for a date. Google says high-demand days can produce fluctuations, so those two numbers do not need to match each day.

Use the specialized migration rule for the migrated LSA campaign: Google says the monthly billing limit equals the average daily budget multiplied by 30.4. The broader Google Ads spending-limit documentation describes daily limits for most Google Ads campaigns, but Google's LSA announcement does not assign that general daily formula to the specialized pay-per-lead campaign.

Review a complete seven-day or 28-day period when you need a pace check. Include dates with the same weekday mix, note campaign pauses, and compare Cost with charged leads and business outcomes. One busy day cannot establish a new monthly pattern.

The planned monthly ceiling remains equivalent when Google transfers the saved weekly average without an account edit. A smaller number on screen reflects days instead of weeks. Use the formula to compare the same unit.

Rounding can create a small visible difference. Account users, automated systems, or API tools can also edit budgets after transfer. A partial month, campaign pause, migration downtime, or different report dates can change actual Cost without changing the original conversion math.

Write down the migration date and the first date the campaign served in Google Ads. Record any correction with the user, timestamp, old value, new value, and reason. That record separates the transfer from later management decisions.

First, divide the saved weekly average by seven and compare the result with Campaigns > Settings. Record the exact result, displayed value, currency, Customer ID, campaign, and screenshot time.

Second, multiply the displayed daily average by 30.4. Save the calculated monthly limit beside the Google Ads setting. Record a rounding note when the screen and calculation use different decimal precision.

Third, set a complete date range in the campaign dashboard and add Cost, Conversions, and Cost / conv. Google defines Conversions for the migrated campaign as charged leads. Compare Cost and charged leads with an equal pre-migration period, then add qualification, bookings, and capacity from approved business systems.

Open Change history within the Campaigns menu. Select the migrated campaign and filter the relevant dates for Budget and Bidding. Review the user, time, old amount, new amount, and surrounding campaign Cost.

Google Ads Change history documentation says the tool lists account, campaign, and ad-group changes from the past two years. It can identify interface users, Google Ads API changes, and some Google Ads system activity. Keep a separate manager note because Google also warns that some account-level or representative changes may not appear.

A clean record uses one reason per intentional edit. If you change budget, Target CPA, territory, and schedule on the same day, the next performance review cannot isolate the contribution of each decision.

Use the fictional account below to separate setting conversion from performance. The old account used a $1,400 historical average weekly budget. Google's formula produces a $200 average daily budget and a $6,080 monthly spending limit.

The business records $5,100 of Cost and 68 charged leads during the last complete 28-day pre-migration period. After the 14-day transition, the next complete 28 days record $5,320 and 70 charged leads. Cost per charged lead moves from $75.00 to $76.00.

The result does not prove a migration effect. The post period spent $220 more and recorded two more charged leads. The reviewer still needs service mix, qualified leads, bookings, completed work, season, capacity, and Change history before recommending a budget change.

The 28-day planning amount of $5,600 comes from $200 multiplied by 28. It is a pace reference for that comparison window, not the calendar-month billing limit. Keep the $6,080 monthly limit and the 28-day comparison in separate fields.

Budget controls the available spend range. Target CPA guides bidding toward a campaign-level cost goal. Service mix changes the blend of lead demand and downstream value. Review all three records before interpreting spend pace.

A multi-service campaign can meet its blended cost per charged lead while producing a different share of plumbing, HVAC, cleaning, or other leads. Add qualification rate, booking rate, cost per booked job, job value, and capacity by service when the business can measure them.

Keep Google's migrated Target CPA as an account fact. Google does not publish the formula used to calculate the unified campaign target. Use your service-line worksheet for business planning without presenting a weighted estimate as Google's method.

A budget edit deserves review when the transfer checks pass and the business has enough complete-period evidence. Confirm the campaign can use more or less spend without creating missed calls, slow replies, schedule gaps, or work that the team cannot deliver.

Use qualified leads, booked jobs, completed work, cost per booked job, revenue basis, seasonality, territory, and staffing. Avoid a universal percentage rule. A $200 daily average can be too high for one operation and too low for another because service value and capacity differ.

Write the decision before editing: evidence period, observed constraint, proposed amount, owner, expected business effect, and next review date. Change one controllable setting when the account can support that sequence.

Do not compare the old weekly label with one new daily Cost value. Convert the units, then compare complete periods. Keep the 14-day migration window separate from the durable performance comparison.

Avoid changing budget and targeting in one action. The next review needs a readable cause record. Check Change history before blaming migration for a number that an account user changed.

Cost per charged lead cannot replace lead-quality and booking measures. A campaign can spend within its limit while the intake team misses calls or the service mix shifts toward lower-value work.

Source review completed July 31, 2026. Weekly-to-daily conversion, the 30.4 monthly limit, daily fluctuation language, migrated reporting metrics, settings path, and stabilization guidance come from Google's LSA migration announcement.

General Google Ads spending-limit background comes from Google Ads spending-limit documentation. The article does not apply the general two-times daily rule to the specialized campaign because Google's migration announcement does not document that rule for pay-per-lead LSA. The tables, reconciliation process, and decision checklist are PrimeLSA calculations and operating recommendations.