One person, 28 days, one Google Ads launch. That is the constraint, and the conversion count—not the calendar—decides when I change anything. A campaign with two conversions on day 14 has not earned the same decisions as one with 40, however neatly both fit into a week-by-week schedule.

I wrote The Google Ads Learning Phase Isn’t a Timer: 4 Beliefs That Kept Resetting Mine about the beliefs that kept resetting mine. This is the second look. Knowing which edits cause trouble is half the job; knowing what one person should actually do while a launch is learning is the other half. The weeks below tell me when to check in. Conversion-volume gates tell me whether to act.

The constraint cuts the A/B testing roadmap, the landing-page rebuild, the second campaign and the retargeting layer. None belongs in a one-person launch that also needs a clean first read. What remains is narrower: set one campaign up properly, keep it stable, fix genuine faults and make the first performance change only when the evidence can carry it. Google’s learning-period guidance ties calibration to conversion events and conversion cycles, not a date circled on my calendar. A long click-to-conversion delay can make 28 days a short window. I plan for that rather than pretend a Friday review creates data.

1. Before day 0: buy a launch you can hold steady

Cost against the constraint: I spend the preparation time on measurement and decisions I cannot cheaply reverse. I do not spend it building variations I will be tempted to judge on day three.

This playbook fits a new campaign, a substantial restructure or a bid-strategy switch. In each case, the strategy needs room to adjust. If I stay on Manual CPC throughout, Google’s Smart Bidding learning status is not the issue; tracking, search terms and budget still are.

Before launch, I need three things: a conversion action tied to a real business event, a budget I can hold through noisy results and one owner who will record changes. A qualified lead, purchase or booked call gives bidding a business signal. A page view gives it a conveniently large number. Those are not interchangeable. I have made the case for conversion-signal quality elsewhere; for this launch, the practical rule is simple: do not buy volume by calling weak intent a win.

I also settle the shape of the campaign now. If eight thin campaigns are split by match type or geography, I consolidate as far as the actual themes allow before the new launch. Doing it later changes the traffic the strategy is trying to understand. The work I cut is optional complexity, not the measurement or structure that makes the next four weeks readable.

What this buys: one conversion definition, one campaign structure and a budget I do not have to renegotiate because day four looks ugly.

2. Day 0: make the expensive decisions once

Cost against the constraint: Day 0 takes the time I might otherwise spend drafting more ads or planning an early bid tweak. Good. An unverified conversion is more expensive than either.

  1. Verify tracking. I complete the conversion path myself and check that the action records in the account, allowing for reporting delay. If it does not record, I fix it before I treat this as a live Smart Bidding launch. A dead tag is not a slow learning period. It is a blindfold.
  2. Choose the primary conversion. I pick the event I want bidding to pursue and the business to judge. If purchases matter, a pricing-page visit does not become a purchase because it fires more often. A sparse honest signal may force a longer runway; a wrong signal can teach the strategy the wrong job.
  3. Set structure, strategy and budget. I settle the campaign’s traffic scope and select the bid strategy that fits the objective and available history. Target CPA needs a target I can defend from what I know; Maximize Conversions gives a new account a way to gather signal under a daily budget without inventing a CPA target. I set a budget I can live with for the first four weeks.
  4. Write down the starting state. I record the conversion goal, bid strategy, target if there is one, budget and launch date. This is my control. Without it, change history becomes an alibi rather than a way to learn.

Google’s Target ROAS setup notes favor giving a strategy time and reviewing weekly rather than daily when traffic is light. If my budget cannot survive even two noisy weeks, I reduce it before launch. At Day 0, that is a plan. In week two, it looks a lot like a reaction.

What this buys: a campaign whose first results refer to a setup I can still identify.

3. Days 1–7: fix faults, not discomfort

Cost against the constraint: I give up the satisfying daily routine of nudging targets, moving keywords and declaring victory over a single expensive lead. I still inspect the account. Sitting on my hands is not the same as closing the laptop.

Week one’s rule is fix what is broken or clearly irrelevant; leave the bidding problem intact. On a launch, I know the urge: open Ads Editor, mine a few search terms, move a keyword, swap a headline, come back tomorrow. By day four, CPA looks ugly and doing nothing feels like charging someone to watch money burn. But a change made to ease that feeling is not evidence that the campaign needed it.

I check search terms every two or three days and add negatives for unmistakably off-target queries. This is not a license for broad negative-keyword surgery. Negatives do change the traffic pool, so I keep each one narrow and defensible. A discussion on r/PPC captures the disagreement: one practitioner would leave the campaign alone for a week; another would check search terms daily. I take the useful part of each. I inspect early, cut obvious waste and do not mistake a small sample for a new targeting strategy.

I fix broken URLs, disapproved ads and an ad that points to the wrong landing page as soon as I find them. Those are faults, not optimization experiments. Clicks sent to a broken page cannot produce the conversion I launched to get.

What gets cut is longer: no target tweaks, no budget swings, no match-type overhaul, no campaign or ad-group restructure and no midweek change to what counts as a primary conversion. Those edits can change what the strategy bids for or the traffic it sees. The earlier learning-phase piece is about the temptation to keep intervening; the operational answer here is to make the exception small and write it down.

What this buys: seven days in which the campaign’s performance is not a composite of five different versions of my own impatience.

4. Days 8–14: let volume choose the next track

Cost against the constraint: I spend the second week collecting and checking the right evidence, not delivering a dramatic week-two verdict. One person cannot manufacture a conversion history by staring harder at a CPA column.

At the end of week one, and again at the end of week two, I ask: how many conversions has this strategy actually had since launch, and how long do they take to arrive? I check the conversion action used for bidding, not an all-time campaign total or a column padded with events the strategy is not optimizing toward. I also leave room for conversions that have not reported yet. Three recorded conversions with a long sales cycle do not turn into a trend because Tuesday became Friday.

For this playbook, I use 15 conversions in a rolling 30-day window as a planning gate, not as a universal rule that Google requires for every bid strategy. Google’s Target ROAS requirements provide context for why conversion history matters; they are not permission to treat 15 events as statistical certainty for every account. The gate makes one decision: which track gets my attention next.

  • Gate A: volume is arriving. If I have at least 15 relevant conversions, or the campaign is plainly heading there soon, I keep the setup steady through week two. I review search terms, check for faults and log what I see. I do not celebrate by changing the target and budget together.
  • Gate B: volume is thin. If I have fewer than 15 and the pace is flat, I take the low-volume track in step 6. This is not a failed launch. It means CPA is especially easy to overinterpret and the first useful adjustment may need to wait beyond day 28.

The status column helps me diagnose, but it does not replace the gate. Learning means the strategy is adjusting; Active means it is running, not that it is profitable. Limited is a prompt to inspect a constraint or setup problem, not an instruction to wait for a badge to disappear. I check the reason shown in the account before deciding whether it calls for a fix. The distinction matters most on slow-converting campaigns: a strategy can be active while the conversions I need to judge it have barely arrived. Conversion cycles, not badge-watching, tell me when a result deserves weight.

What this buys: a branch based on feedback, rather than an edit scheduled for day 15 whether the campaign earned it or not.

5. Days 15–28, Gate A: make the first change you can explain

Cost against the constraint: I get one measured adjustment at a time, not a full round of optimization. I give up speed in exchange for knowing which change might have caused the next result.

Gate A is permission to consider a performance edit, not an order to make one. First I check whether reported conversions have had time to fill in and whether CPA is moving in a direction that holds beyond a few events. If the account is too noisy to answer either question, I keep watching. A date does not strengthen a weak sample.

If I do have a defensible reason to adjust a Target CPA, I move in a small step, such as 10%, then give the strategy roughly five to seven days before considering another. A target that sits above observed CPA is not, by itself, a reason to lower it: a tighter target can restrict volume. I need the business goal, conversion pace and current results in the same conversation before I touch the setting. Google’s Target ROAS guidance also supports a weekly, rather than daily, review rhythm when traffic is light. I use that rhythm to make a decision I can later evaluate.

Budget gets its own week if it needs to change. I do not change budget and target in the same week. A budget change affects which auctions the campaign can afford to enter; a target change affects how it bids. If I move both, I have made the next CPA harder to explain. Before each edit, I log the date, the setting, the reason and what I expect to see. Then I make the change. The order is deliberate: the explanation should exist before the result does.

If Gate A arrived late, this step may consist of no performance edit at all within 28 days. That still follows the plan. The constraint buys a first justifiable change, not a compulsory one.

What this buys: an adjustment I can connect to a stated goal, followed by enough quiet time to see what happened.

6. Days 15–28, Gate B: keep the signal honest

Cost against the constraint: I give up the promise of a tidy day-28 CPA verdict. High-ticket B2B, long sales cycles and small local budgets may not produce enough conversions in four weeks for one. I spent two years on an account where three demo requests a week felt like a drought after ecommerce work at 35 orders a day. My instinct was to intervene faster. It was wrong.

On Gate B, I take three actions in order:

  1. Check for a real fault. I revisit the tracking test, the conversion action, landing pages, disapprovals, search terms and budget delivery. If something is broken, I fix it and log the change. If nothing is broken, I do not call ordinary low volume a technical emergency.
  2. Keep the primary outcome visible. I can observe a more frequent action, such as a qualified form start, to learn whether traffic is showing intent. I do not assume that setting an event as secondary makes Smart Bidding learn from it. If I later decide to bid toward a proxy, that is an explicit change of optimization goal with a real trade-off: more feedback may come at the cost of pursuing an event further from pipeline. It starts a new evaluation, not a free shortcut through this one.
  3. Tell the stakeholder what the volume allows. Four conversions a week do not become a confident performance story on day 28. I explain that I need more conversion cycles and keep logging the real outcome. I would rather extend the read than fill a report with page views and call them leads.

I also cut the portfolio-strategy detour from this four-week plan. Google’s Smart Bidding documentation and portfolio-strategy overview describe ways to apply a strategy across campaigns. That can be worth examining when there are multiple campaigns. Here I have one person, one launch and one campaign to keep readable. Spinning up or reorganizing campaigns to pool data would spend the very constraint this playbook is built around.

What this buys: an honest low-volume diagnosis and a launch I can continue, rather than a misleading conversion count I have to unlearn later.

7. Day 28: follow the gate, then decide what to add

Cost against the constraint: Day 28 is a decision point, not a finish line that entitles me to scale. I review the change log, conversion pace, conversion lag, CPA and the business value of the conversions before I make the next move.

  • If Gate A held and results support more spend: I can raise budget in a measured step, such as 10–15%, provided I am not changing the target in the same week. Then I watch the next conversion cycle rather than treating the higher budget as a completed experiment.
  • If Gate A held but the picture is mixed: I hold the setup and wait for a clearer read. More volume does not make every result good.
  • If Gate B still holds: I keep the real conversion goal in view, extend the runway and decide whether the next cycle warrants an explicit proxy-goal test. I do not backdate that decision into a successful first 28 days.

When the constraint lifts—when the budget outgrows one pair of hands or volume arrives faster than I can inspect and log it—the question changes. It is no longer whether I can squeeze another edit into Tuesday. It is who does the work between decisions. That is where I handed execution to groas: specialized models work around the clock inside agreed guardrails, actions are logged with reasoning, and a named strategist owns the direction. I would still run this first launch by hand. It is what made me stop wanting to run every day after it by hand.