How to set a fixed test period before scaling or stopping Google Ads
How to set a spend cap, end date, and decision point for a Google Ads test. The industry calls this a proving period. I call it a fixed test with an end date.
How to set a spend cap, end date, and decision point for a Google Ads test. The industry calls this a proving period. I call it a fixed test with an end date.
A fixed test period is a bounded test of a defined business outcome. It gives the campaign a spend cap, a time boundary, and a decision date before hope turns into an open-ended invoice.
A campaign without those three numbers is not a test. It is a donation.
The short answer
Write three numbers before launch: what the test may spend, how long the defined outcome needs to mature, and the date the answer is given. The right length is not 30, 45, 60, or 75 days by default. It comes from your own booking record and conversion lag.
The test should answer one question: does this defined advertising outcome justify another bounded period of spend?
Write the spend cap, the period length, and the decision date before the first dollar moves. The cap bounds the downside, the length covers the conversion lag of the outcome you defined, and the decision date forces a continue, adjust, or stop decision in writing.
Together these three form a fixed test budget and an end date: the spend cap that bounds the downside, the fixed test period that lets the outcome mature, and the decision date that forces a decision. Named once, then used plainly for the rest of the page.
The spend cap is the maximum amount you are willing to commit to the test. Write down what it includes.
You may choose a media-only cap for advertising spend, or an all-in acquisition cap that also includes management, landing-page work, tracking, creative, or software. Neither is automatically correct. What matters is that the numerator stays visible and comparable.
A cap set from the owner’s actual cash position is more honest than a benchmark borrowed from another trade. It should be an amount you can lose without changing the business’s ability to operate, while still being large enough to observe the outcome you are testing.
If the campaign crosses the cap, it pauses. Continuing needs a new written decision, not an automatic extension conversation.
The period is the time allowed for the defined outcome to mature. It should cover the relevant conversion lag and enough of the sales cycle to judge the outcome without pretending that incomplete data is final.
Google defines a conversion window as the period after an ad interaction during which a conversion can be recorded. Conversions that happen after the window are not included in the report. Google says that if 75% of conversions happen between days 25 and 30, the window should be at least that long. Search and Display use a 30-day default when the conversion window is not customised, and different conversion actions can use different windows.
The campaign’s fixed test period and Google’s conversion window are related, but they are not the same setting. The fixed test period is your business decision boundary. The conversion window is a measurement setting. Both should reflect the actual path from click to lead, booking, completion, and confirmed value.
On the decision date, your one-page monthly report answers one question: continue, adjust, or stop?
The decision date is not necessarily the day the calendar reaches zero. If conversions are still inside the reporting tail, the report should show the mature and immature portions separately. Waiting for existing evidence to arrive is different from spending more without a new decision.
Most arguments about test length are really arguments between three different clocks. They are related. They are not the same.
How long an automated bid strategy needs to calibrate after a change.
How long a click takes to become a reported or imported conversion.
How long until you know which leads became qualified, booked, finished, and paid work.
Google says a Learning status may appear after a change to an automated bid strategy, and that the duration depends primarily on conversion volume, conversion-cycle duration, and bid strategy. Google says learning can take up to three weeks or one to two conversion cycles, although it may be faster with more conversion data, and that previous campaign conversion data can help speed the initial learning period.
That is platform guidance about calibration. It is not a promise that every local business will have enough booked-job evidence by the end of three weeks. The absence of a Learning label does not mean the platform has stopped learning.
Google’s documentation also advises against frequent changes to budgets, targets, or conversion goals during the learning phase. That does not mean an owner must tolerate an obvious tracking failure or unsafe spend. Fix material errors and document the change.
Google defines a conversion cycle as the time from a click to a conversion, and for imported conversions it also includes the time until the conversion is reported in the account.
A call may be reported shortly after the interaction. A booked estimate may occur later. A finished installation and its payment may happen later still. Use the bid-strategy status and conversion-delay reporting where available, and do not close a test while expected conversions are still missing because of normal reporting delay.
The business-verdict clock runs from the lead through the owner’s actual outcome.
Different service types complete that third clock at different points. An emergency drain-cleaning call may be answered, booked, and finished quickly. An HVAC or roof replacement may involve inspection, multiple estimates, financing or an insurance process, and a scheduled installation. A recurring pest or cleaning plan has a first booking followed by later visits and renewals. A mobile detailer has a short booking path but a constrained radius and package capacity.
These are patterns to investigate, not universal calendars. Any starting window you write down is a starting hypothesis, and the final window comes from your own booking and conversion-lag record. The table names what to track, not how many days to wait.
| Service type | Where the cycle usually lags | What to track before the verdict |
|---|---|---|
| Emergency repair | Contact and booking may be fast, but dispatch, completion, payment, and repeat work still lag | Answer rate, booked dispatch, completion, payment, and service area |
| Scheduled maintenance | Booking may happen quickly while the service date and renewal fall later | Accepted work, appointment completion, then repeat or renewal value separately |
| Installation or replacement | Quote, decision, deposit, installation, and final payment occur at different times | Inspection, signed contract, and finished projects; do not close the test at the form stage |
| Recurring service | The initial booking is not the whole value | Activation, finished visits, collection, cancellation, retention, and contribution by cohort |
| Mobile or route-based service | A short booking path can still exceed the radius or the schedule | Package, location, travel, capacity, and finished appointments |
A fast lead can still be an unprofitable or unserved job, the first call may precede the commercial outcome by days or weeks, and first-visit value is not plan value. That is the whole reason the decision date comes from the service type and not from a fixed number of days.
A campaign test can contain several questions. Write the main one before launch.
| Question | Minimum outcome to define |
|---|---|
| Can the market produce relevant demand? | Relevant search terms and qualified leads |
| Can the offer generate leads? | Calls, forms, messages, or other defined leads |
| Can the business turn leads into work? | Confirmed booked jobs, accepted estimates, or dispatched jobs |
| Can the work carry the acquisition cost? | Revenue plus a stated contribution or margin model |
| Can the team fulfil more work? | Capacity, routing, staffing, inventory, and schedule availability |
| Can the result be repeated? | A mature period with consistent definitions and no unexplained tracking break |
Do not ask a lead-generation campaign to prove profit if the booking and margin records are not connected. Do not ask a high-ticket campaign to prove finished revenue on the same calendar as an emergency service.
The verdict should show how complete the evidence is.
Activity data: impressions, clicks, spend, search terms, calls, forms, and platform-reported conversions.
Lead data: contactable leads, service fit, location fit, requested service, and answer status.
Sales data: estimates, deposits, accepted work, booked jobs, dispatched jobs, and signed contracts.
Delivery data: finished jobs, refunds, cancellations, repeat visits, plan status, and client-confirmed revenue.
Economics data: variable job costs, contribution margin, acquisition costs, capacity, and estimated payback at the client’s stated margin.
The report should say which layer is present. A platform lead result is not a booked-job result. A booked-job result is not a completed-revenue result. Revenue is not profit.
Do not use one universal count. Use evidence quality.
| Evidence level | What it can answer | Limitation |
|---|---|---|
| Clicks and impressions | Is the campaign eligible and receiving demand? | Not whether the demand is useful |
| Contact events | Are people calling, submitting, messaging, or booking? | Contact may be duplicated or irrelevant |
| Qualified leads | Is the demand serviceable and commercially relevant? | Qualification may be incomplete or subjective |
| Booked jobs | Is the business turning qualified demand into commitments? | Jobs may later cancel or fail to complete |
| Finished jobs | Is the business fulfilling the work? | Revenue and costs may still be pending |
| Paid jobs | Has money been collected? | Margin and attribution may still be uncertain |
| Estimated contribution | Does the result fit the owner’s economics? | Depends on confirmed revenue and owner-stated margin |
The right stopping point depends on the decision the owner needs to make.
Start from the outcome you must observe and how many instances of it a responsible decision needs. Multiply by your own early cost evidence, add room for variation, and test the total against the cash boundary. If it does not fit, narrow the scope rather than stretch the promise.
Name the outcome you must observe
A qualified lead, an accepted estimate, or a booked job, defined in writing before launch.
Estimate how many of those you need for a responsible decision
Not a statistical claim. A judgement about how much variation you are willing to accept in the answer.
Multiply by the expected cost under the account’s own early evidence
Use your own record where one exists. Where it does not, say the figure is a planning estimate and correct it as data arrives.
Add room for variation, then test it against the cash boundary
If the amount is unaffordable, narrow the service, shrink the geography, change the offer, or wait. Do not stretch the promise to fit the budget.
Write the cap, the review date, and who confirms bookings
The cap should not rise merely because the campaign has spent it. A new cap needs a new reason.
Write these fields before launch:
| Field | Example definition |
|---|---|
| Campaign scope | Search ads for residential drain cleaning in the stated service area |
| Main outcome | New client with a confirmed appointment on the calendar |
| Secondary outcomes | Qualified call, form, estimate, finished job, client-confirmed revenue |
| Included spend | Advertising spend only, or an explicitly stated all-in acquisition cost |
| Excluded spend | Costs intentionally outside the test, stated in writing |
| Cap | Maximum amount authorised before the campaign pauses |
| Review date | Date when the evidence is reconciled |
| Verdict owner | Person responsible for confirming bookings and value |
| Continue, change, and stop rules | Written before launch, not chosen after seeing the number |
A test without a maximum exposure is not a controlled test. It is an open-ended spend decision.
A plumbing company runs a search campaign covering emergency repairs and scheduled drain service.
| Test period | Defined cost | Unique leads | Qualified leads | Booked jobs | Finished jobs |
|---|---|---|---|---|---|
| Days 1 to 7 | $420.00 | 12 | 7 | 3 | 2 |
| Days 8 to 14 | $460.00 | 14 | 9 | 4 | 3 |
| Days 15 to 21 | $480.00 | 15 | 10 | 5 | 4 |
| Total | $1,360.00 | 41 | 26 | 12 | 9 |
Booked-job rate is 12 ÷ 26, or 46.2% of qualified leads. Cost per booked job is $1,360.00 ÷ 12, or $113.33. At day 21 the platform may have finished or nearly finished a learning period, depending on the bid strategy and conversion cycle, while three of the twelve booked jobs are still not finished work.
If the business has a target acquisition cost below $113.33, that is a reason to investigate service mix, travel, call handling, booking, or query quality. It is not on its own a reason to pause a small or delayed sample.
If Google’s conversion window ends before a meaningful share of the business’s conversions occurs, some outcomes may not appear in the report. Google warns that conversions after the selected window are not recorded, and suggests a window long enough to cover the observed conversion distribution.
Before setting a decision date, review the account’s conversion-lag report, CRM timestamps, booking calendar, sales pipeline, and the time from lead to finished work. If the account has no history, state the uncertainty and use the first bounded period to learn it.
Do not reset the fixed test period every time an outcome arrives late. Mark the original period, record the lagged outcome, and explain whether the verdict changed because the evidence matured.
Many local-service outcomes occur by phone or after the lead leaves the website. Google explains that offline conversion imports can measure what happens after an ad click or call in the offline world, including a signed contract or a finished sale. Google also documents call conversion tracking and imported call conversions based on a business’s own outcome criteria.
Where the technical setup, consent, identifiers, CRM, and conversion definitions support it, import qualified leads, booked jobs, contracts, or finished jobs back into Google Ads. The platform can only improve toward the outcome and data you define and send. Offline imports do not repair an unclear booking definition or missing client confirmation.
On the decision date the Ledger returns one of three answers. Continue when the defined outcome hit target and capacity can serve more. Adjust when one named problem deserves one bounded change. Stop when the evidence cannot justify more spend. Each verdict is written, dated, and acted on.
Continue when the defined outcome is within target or the evidence supports a clearly stated next test. Check capacity, marginal demand, tracking quality, and whether the period is mature enough before increasing spend.
Adjust when the campaign has a specific problem, or the result is close enough to justify one bounded change. Name the change, write a new cap, define the next outcome, and set a new date. Do not make five simultaneous changes and call the result a lesson.
Stop when the evidence does not justify more spend, the offer cannot serve the demand, the geography is uneconomic, the tracking cannot be trusted, capacity is unavailable, or the contribution model cannot carry the acquisition cost. The account pauses. The owner keeps the search-term, lead-quality, and measurement findings.
A stop verdict is not a failure of the engagement. It is the engagement working. The owner paid a bounded amount to learn something expensive and will not pay it again on faith.
A test can be paused early when there is a documented business reason: tracking is recording false conversions, the phone line is not working, the business cannot serve the area, the campaign is spending outside the approved exposure limit, the offer is unavailable, the service is unsafe or legally unavailable, capacity is gone, or search intent is clearly outside the service model.
Pausing for a real operating failure is different from pausing because one day had no leads.
Wait for more evidence when the campaign is still inside the defined conversion cycle, booked jobs are pending in the CRM, the sample is small and outcomes vary by job type, the account recently changed bid strategy or conversion goals, the phone system or CRM has not reconciled the recent period, duplicate contacts cannot yet be identified, or the only evidence is clicks, impressions, and cost per lead.
Waiting is not the same as ignoring performance. It means holding the exposure limit while the defined evidence matures.
An extension is not a default fourth verdict. It can be justified when a defined portion of the existing evidence is still inside the conversion tail, the sales cycle has not yet matured, tracking was interrupted and the missing data can be recovered, or a material operational event made the original period unrepresentative.
An extension must state the reason, the remaining question, the new cap, the new date, and what will count as a decision. If it has no new question, it is only delay.
The test becomes harder to interpret when several major variables change at once: a new bid strategy, a new conversion goal, a large budget change, a new service area or service line, a new landing page, new call routing, new operating hours, a major negative-keyword change, a new offer or price, or a change in campaign composition.
If a change is needed, record it and start a new evidence segment rather than pretending the whole period is homogeneous.
| Metric | What it tells you |
|---|---|
| Total advertising spend | Dollars spent within the written scope |
| Other acquisition cost | Management, tracking, creative, software, or other included costs |
| Qualified leads | Client- or rule-defined leads that fit the service and area |
| Booked jobs | Client-confirmed outcomes using the written booking definition |
| Cost Per Booked Job | Attributable spend divided by attributable booked jobs |
| Revenue confirmed | Revenue the client confirms, with timing and source stated |
| Contribution or margin | The stated model after defined variable costs |
| Estimated payback | Only when the time series and margin model support it |
| Conversion delay still pending | What the report is still waiting for |
| Major changes during period | Every change that split the evidence into segments |
| Evidence maturity | Mature, still in lag, incomplete, or affected by a tracking break |
| Verdict | Continue, adjust, or stop |
If the client’s margin is on file, profit is estimated at that margin and labelled accordingly. Without a margin, the report stops at revenue and says so. Revenue crossing advertising spend is not automatically payback.
Do not move the goalposts from leads to booked jobs after the campaign starts. Do not compare a mature 60-day period with a seven-day period and call the difference performance. Do not raise the cap because the first leads were interesting. Do not keep spending because a platform reports a conversion while the booking calendar says nothing happened. Do not declare a channel impossible because a tracking break, capacity problem, policy issue, or weak offer prevented a fair test.
Do not use universal cost-per-click, cost-per-lead, close-rate, answer-speed, or budget claims as substitutes for the business’s own record. Benchmarks can generate a hypothesis. They cannot close your books.
Before the first dollar moves, you should know:
If those answers are missing, the campaign is not ready for a promise.
Your one-page monthly report
The right test length is the shortest period that produces a defensible answer without exposing the business to uncontrolled downside. I count conservatively: each call and form once, and nothing I cannot show.
A fixed test period only works if the verdict number is defined before launch. The CPBJ calculator fixes that number, and the budget calculator sets the cap it runs inside. If you want that structure run for you rather than by you, start a conversation.
Long enough for the defined outcome and a meaningful share of its conversion lag to mature, but not indefinitely. Emergency bookings may mature faster than high-ticket projects or recurring plans. Use historical booking data when you have it. Without it, write a bounded starting hypothesis and label the uncertainty.
Sometimes, but not universally. Google's default Search and Display conversion window is 30 days when it is not customised, but your business may have conversions that occur later or outcomes that happen offline. A 30-day test should not be called complete merely because the calendar reached day 30.
There is no universal fair budget. The amount depends on service area, competition, cost per click, offer, conversion volume, sales cycle, capacity, and the outcome being tested. Set the cap from the owner's cash boundary and the evidence required, then write it down before launch.
If the written cap or decision date has arrived, pause rather than spend by inertia. Reconcile the existing conversion tail, then decide whether a new bounded period is justified.
Optimise toward the deepest reliable outcome you can measure and import. Start with leads if that is all the account can currently record, but do not call lead volume booked work. Where the setup supports it, offline conversion imports can connect later outcomes to the original ad interaction.
Stop when the evidence does not justify more spend, the defined outcome is not economically viable, the service area or offer cannot be fulfilled, capacity is unavailable, or tracking cannot support an honest verdict. A stop can be the correct result of a bounded test.
Scale only after the outcome is mature enough to judge, the tracking is trustworthy, the business can fulfil more work, and marginal demand remains acceptable. Do not use a fixed percentage increase as a universal rule. Write the next cap and the next review date instead.
Report the lead result and the booking result separately. Review service fit, geography, answer rate, follow-up, price, capacity, and the booking definition. Do not convert an unconfirmed lead into a booked job to make the campaign look healthier.
Separate the first booking or plan signup from later visits, renewals, cancellations, and retained revenue. The initial period may be enough to judge acquisition, but not enough to claim lifetime value or retention without later evidence.
No. Google says an automated bid strategy may take up to three weeks or one to two conversion cycles to calibrate, depending on conversion data, conversion-cycle duration, and bid strategy. That is platform calibration guidance, not a promise that your business will have enough booked-job evidence by the same date.
The form sends your details to me by email. I reply personally.