The first optimization cycle is not touching everything
First confirm what the system bought, then decide the one variable this cycle may change. Seven days is a review cadence, not fixed proof. The first-cycle goal is fewer changes, explainable changes, and reversible changes. The output is a first optimization decision log.
First optimization decision log
Proof
Tracking / sample / terms / page
Variable
One change only
Window
Review date + rollback
Google Ads Basics 05 → 06
Bring the previous article's metric readout into this lesson: find the break, then keep one action
The previous article connected Google Ads, GA4, Shopify, and profit fields in one 7-day window: verify tracking, then read impressions, clicks, page, orders, and counter-evidence such as refunds, discounts, and margin. This lesson keeps the same 20oz leak-proof travel mug case. It does not reteach CTR, CPC, CVR, CPA, or ROAS; it turns the readout into one state: observe, pause, modify, or rollback, plus one primary variable. Day 7 is a review date, not automatic proof. If sample or tracking is still weak, wait or repair the evidence.
Bring from the previous article
The same 7-day window, Search traffic and page-path evidence, Conversion actions / GA4 purchase / Shopify Orders reconciliation, metric layers, and profit counter-evidence.
This lesson completes
Write the first-cycle decision log for the 20oz tumbler account, change one primary variable, freeze the rest, and record Change history, review date, and rollback trigger.
Next route
If the break is query quality, continue to Google Search Terms: Observe, Negate, or Split. If it is measurement, page, or budget, follow that evidence route instead of calling every anomaly optimization.
Turn a readout into one reversible action
The first optimization output is not many edits; it is a decision log you can review
Keep the 20oz leak-proof travel mug from the previous article. Suppose the 7-day readout shows 80 clicks from relevant queries, six page add-to-carts, three Google Ads Purchases, but only one Shopify order; two clicks came from “free tumbler” and “used insulated bottle.” “CVR got worse” is not yet an optimization conclusion. You do not know whether the break is duplicate tracking, wrong query intent, page handoff, or a thin sample. The first cycle turns the symptom into a falsifiable question before changing the account.
Use this model: observe → layer the evidence → choose an action state → change one primary variable → review → continue, pause, or roll back. Observe is not procrastination; it protects causality when tracking or sample is weak. Pause blocks a demonstrated risk, such as clearly irrelevant queries or duplicate Purchases. Modify changes one setting that could explain the break. Rollback restores the prior setting when the written trigger appears. Day 7 is a review time, not permission for a permanent edit.
For the tumbler case, write four rows in one log: did tracking pass; is the sample comparable; do queries and match types express the intended buyer; and where does the page path drop between click, add-to-cart, and checkout? If Purchases do not reconcile with Shopify, pause CPA/ROAS conclusions and fix deduplication. If only “free” and “used” queries pollute traffic, scoped negatives may be the primary variable. If query quality and tracking pass but clicks do not become add-to-carts, test the above-the-fold promise or offer as the one variable. Save Change history, old value, new value, start date, and rollback trigger.
The pass line is being able to explain what happened next week, not collecting more green arrows in the interface. Do not change budget, bids, keywords, ad copy, and page together. Do not call the first order a page win or a platform recommendation proof. After the change, keep one review window and record same-definition movement in CTR, CPC, CVR, accepted Purchases, query quality, checkout errors, and contribution profit. If the stop line is breached, roll back and write why. If the issue is traffic shape, Google Search Terms: Observe, Negate, or Split handles search-term governance; only after a repeatable sample should you discuss scaling.
Write the symptom as a falsifiable question, then choose observe, pause, modify, or rollback; change one primary variable and write review and rollback conditions first.
Plain terms first
Four optimization-discipline terms prevent account churn
These are not management buzzwords. They decide when to wait, pause, change, or roll back.
observation window
Observation window is the time and sample range you wait after launch or a change before judging performance.
Where: It lives in review sheets, change logs, and team calendars rather than a single Google Ads button.
What breaks: Without it, teams read learning noise, daily luck, or low sample as trend.
Example: If a new Search campaign has only 18 clicks after 3 days, mark low sample instead of rebuilding.
primary variable
Primary variable is the one main factor allowed to change in this cycle, such as negatives, budget, copy, or hero section.
Where: It belongs in the one allowed change field of the first optimization decision log.
What breaks: Changing too many variables makes next week’s review unable to identify the cause.
Example: If this cycle only adds negatives, do not also change budget, copy, and page.
rollback condition
Rollback condition is the standard for pausing, restoring the previous version, or reducing risk if the change fails.
Where: It should be written with the change record: how long to watch, which metric decides, and who acts.
What breaks: Without it, teams explain bad results after the fact instead of acting by rule.
Example: If a new negative reduces high-intent impressions sharply, revert it and review match type.
change log
Change log records who changed what, when, based on which proof, and when it will be reviewed.
Where: It can be a spreadsheet, Notion page, or task, but next week’s review must see it.
What breaks: Without it, neither wins nor losses become reusable account knowledge.
Example: Record: May 20 add free/jobs negatives; review search terms and CPA on May 27.
Main asset
First optimization decision log: proof before action
This log turns optimize it into reviewable fields. Without proof, window, and rollback, do not change the account. Day 7 means it is time to check, not that every account has enough sample for a final conclusion.
Tracking status
Whether Purchase, value, currency, and transaction ID are trusted.
Untrusted tracking means CPA / ROAS should not guide optimization.
Sample status
Spend, clicks, conversions, and days observed.
Low sample turns many conclusions into noise.
Search term evidence
Which terms are high-intent, suspicious, or irrelevant.
The first cycle starts with what the system actually bought.
Page path evidence
Browse, cart, checkout, payment failure, quick bounce.
If terms are right but page fails, budget is not the cause.
Primary variable
Pick only one: negatives, budget, copy, page, or bidding.
Next week must be able to read whether this action worked.
Frozen items and rollback
What stays unchanged and what triggers rollback or pause.
Prevents optimization from becoming unreviewable churn.
Review sequence
First cycle follows sequence; account changes come last
Tracking, sample, search terms, page path, then one primary variable across budget, terms, copy, page, or bidding. This lesson handles first-cycle action discipline; full negative-keyword governance and scaling readiness stay in the next lessons.
1. Verify tracking
Conversion action, value, currency, test order, and backend order reconcile.
Do not move budget first.
2. Judge sample
Spend, clicks, conversions, and days are enough for a conclusion.
Do not read two no-conversion days as structural failure.
3. Read search terms
Spend went to high-intent, suspicious, or clearly irrelevant queries.
Do not only read the keyword list.
4. Read page path
After click: browse, cart, checkout, or quick bounce.
Do not blame page problems only on ads.
5. Pick one action
Change one of budget, keywords, negatives, copy, page, or bidding.
Do not change all on one day.
Action states
Do not call every problem optimization
The first review has four states: observe, pause, modify, rollback. Clear state means clear next step.
Observe
Low sample, tracking just fixed, no obvious direction drift.
Write the observation window and next review date.
Pause
Clearly irrelevant terms, wrong location/language, or page promise mismatch.
Pause the waste source and record why.
Modify
The problem is clear and can be handled by one variable.
Change one main variable and freeze the rest.
Rollback
After change, traffic worsens, cost breaches, or conversion quality falls.
Restore the previous version and write the trigger.
No-conversion router
No conversions in week one does not always mean rebuild
Answer these five questions before choosing observe, pause, modify, or rollback.
Are there impressions and clicks?
Move into search-term and page-path checks.
Check approval, budget, location, bidding, keyword coverage, and conversion settings.
Single-variable rule
Change one primary variable and write frozen items
One variable is not about being timid; it lets next week judge whether the action worked.
Negative keywords
Clearly irrelevant, free, jobs, repair, wrong location.
Freeze: Freeze budget, page, and bid strategy.
Budget
Trusted tracking, healthy terms, page path has valid signals.
Freeze: Do not also change keywords, copy, page, or bidding.
Ad copy
Low CTR with correct intent and unclear ad promise.
Freeze: Do not also change page and keywords in the same cycle.
Page
Terms are right but CVR, carts, or checkout path is weak.
Freeze: Keep ad structure and budget unchanged.
First-cycle move simulator
Translate optimization impulse into state, variable, and frozen items
The common first-cycle mistake is not doing nothing. It is treating low evidence, tracking problems, page friction, and budget impulse as the same optimization. Choose the closest account state and write it back into the decision log.
Current evidence state
Tracking not trusted
Evidence
Ads reports conversions, but Shopify orders, value, currency, or transaction ID do not reconcile.
Wrong move
Using CPA / ROAS to change budget or bidding strategy.
State
Pause optimization conclusion
Allowed move
This cycle only fixes measurement and adds test-order proof plus reconciliation notes.
Frozen items
Freeze budget, bidding, keywords, and page.
Rollback
If the fix changes historical readout, restart the observation window and do not mix old data.
Log line: Cycle state: tracking fix; primary variable: conversion measurement; review: read CPA only after test order and Shopify / Ads reconciliation pass.
Separate urgent repair from a normal experiment
First decide whether the condition needs containment, then choose evidence by campaign surface
“One variable” applies to normal experiments that can wait and compare. When duplicate measurement, approval/eligibility, price or availability, landing-page, or checkout promises conflict, protect the customer and readout before optimization.
Duplicate Purchases, approval or item-eligibility problems, price/availability mismatch, or a failed payment or checkout promise are not reasons to wait for a fixed seven days.Preserve the current scope, affected item or Market, time, and Change history, then have an authorized account lead address that fault. Read repaired data in a new observation window instead of mixing it with the pre-fix period.
A normal experiment does not copy a fixed three-, four-, or seven-day rule either. Write spend, clicks, conversion lag, account changes already made, and customer-visible risk in one record before deciding whether to keep observing, change one variable, or escalate.Choose the actual campaign surface below to generate the evidence, urgent route, normal-experiment route, and boundary for the decision log.
Choose the surface currently carrying the traffic
Current surface route
Search: separate query, match, and promise first
- Read first
- Write Search terms, matched keyword, match type, location/language, ad approval, and Final URL. When low-volume or privacy-limited queries are not shown row by row, record “not visible” as a gap rather than proof of no demand or no waste.
- Urgent or eligibility route
- When approval, location/language, duplicate Purchases, or a checkout promise is clearly wrong, this is not a seven-day experiment. Preserve the current readout and Change history, have the authorized account lead contain or repair that fault, then start a fresh observation window from the repair date.
- Normal-experiment route
- When tracking and page path are readable and a clearly irrelevant query is spending, this cycle may add one scoped negative set; budget, RSA, page, and bidding remain frozen.
- Write into the decision log
- Write campaign_surface=Search, query/keyword/match, approval status, one action, old/new value, observation window, rollback trigger, and next readout.
- It still cannot prove
- This is not full negative-keyword governance and does not prove an unseen query is absent, a keyword has no value, or the account is ready to scale.
The selector creates only a classroom record and copied note. It does not read real Ads, Merchant Center, Shopify, GA4, product, order, inventory, authority, or publishing state.
Change control board
Choose one current pressure, then write change history, observation window, and rollback trigger
This block is interactive. Click the pressure closest to the account, then review the generated variable, co-change bans, and rollback trigger. If not, do not touch account buttons yet.
Current change control
Waste query is spending
Choose when
Choose this when tracking is trusted, page path has no obvious break, and the waste term does not overlap real product demand.
Only primary variable
Add one negative keyword set only, scoped to ad group or campaign first; do not touch budget or page.
Change history line
Change history: 2026-__-__, added negative ____, level ____, reason: Search terms spent ____ with no purchase intent.
Observation window
Watch 3-7 days or one comparable spend window; check whether high-intent impressions, clicks, and CPA are preserved.
Rollback trigger
If high-intent queries or core keyword impressions drop sharply, revert the negative and narrow match type or level.
Do not co-change
Do not also change budget, RSA, Final URL, bid strategy, or page hero.
Bring next review: Next review brings Search terms, Change history, keyword impression change, and Shopify order quality.
Causality check
Change one thing this cycle so next week can tell what worked
Many accounts do not fail from too few changes; they fail from too many same-day changes. Pick a mixed-change scenario to see what causality breaks and which single variable should remain.
Click the option closest to your current impulse
Current causality read
Budget raised and negatives added same day
What becomes unclear
If CPA drops next week, you cannot tell whether budget found better traffic or negatives removed waste. If orders drop, you cannot tell whether budget learning moved or negatives blocked real demand.
Keep only
This cycle only adds one clearly irrelevant negative set. Keep budget at $30 and discuss budget next cycle.
Frozen items
Freeze budget, RSA, Final URL, landing page, and bid strategy.
Next week asks only
Next week asks only: did high-intent impressions, clicks, CPA, and purchase quality improve because negatives cleaned traffic?
Official evidence boundaries
First-cycle optimization starts with what the evidence can and cannot prove
Google Ads gives you search terms, conversion columns, change records, and budget status. They are evidence inputs, not automatic optimization conclusions. Separate the boundaries before choosing the one primary variable.
Search terms report
The search terms report shows actual queries, keyword, and match type; low-volume or privacy-limited queries may not appear as individual rows.
In the first cycle, use it to confirm visible waste terms, promotable terms, and page-content needs, not as the complete list of long-tail demand.
Do not assume missing queries mean no waste, and do not rebuild a campaign from match type alone.
Conversion tracking data
Conversion, conversion value, conversion rate, and related columns are useful only when actions, value, currency, dedupe, and attribution logic are trusted.
The first cycle starts with tracking status: when tracking is not trusted, the allowed move is QA or reconciliation, not budget, bid, or copy changes.
Do not read zero conversions as no demand, or a few conversions as proof that the structure is correct.
Change history
Change history can show account edits, timing, user, and change type, but it records the edit, not the business reason.
The decision log adds what change history does not: why you changed, the primary variable, frozen items, and rollback timing.
Do not treat change history as the review itself; seeing a budget or negative edit does not mean the edit had evidence.
Budget changes
Budget changes affect serving pace and spend limits; Google Ads may spend more than the average daily budget on a day while monthly limits still apply.
In the first cycle, test budget in small steps only after tracking, search terms, and page path pass, with a written check window.
Do not cut budget just because one day spends fast, and do not raise budget repeatedly because one day ROAS looks good.
Negative keywords
Negative keywords can keep ads away from irrelevant queries, but overly broad scope or the wrong level can block real demand.
In the first cycle, handle only clearly irrelevant terms and record negative level, match type, reason, and check window.
Do not treat every non-converting search term as waste; a short window can simply mean low sample or conversion delay.
Conversion windows
Conversion windows decide how long after an ad interaction conversions can be counted, so short-window reviews are affected by conversion lag.
First-cycle review should write the observation window and conversion lag before deciding whether to extend, fix tracking, or change one variable.
Do not rebuild the campaign just because ordinary conversion columns look weak on day 3 or day 7.
Short-window readout
A 7-day review separates normal conversion columns from by-conversion-time columns
This is not a full metrics lesson, but short windows are easy to misread because of conversion lag. Normal columns help read optimization input, while by-conversion-time columns explain what actually happened this week; both need Search terms, Change history, and Shopify Orders beside them.
Conversions
Check whether attributed learning signals have started to accumulate; useful for tracking status and optimization input.
Do not read it as this week’s Shopify order calendar; it may be written back by click time.
Conversions by conv. time
Read when conversions actually happened to explain why Ads conversions and the order calendar differ in week one.
It is short-window readout evidence, not a replacement bidding basis.
Conversion value
Check whether value signal is passing order value, currency, and transaction_id correctly.
Do not treat platform value as profit; reconcile it with Shopify refund, discount, and net sales.
Conversion value by conv. time
Read value in the actual current conversion window to explain short-term ROAS versus Shopify sales gaps.
Do not use it alone to release budget; still write break-even ROAS, Max CPA, and contribution profit.
Cost / conv.
After tracking is trusted, compare CPA to Max CPA; if tracking is not trusted, fix conversion action first.
Low CPA does not prove order quality, post-refund profit, or scale readiness.
Search terms / Change history
Keep waste terms, negative level, change time, and next review in one record.
Do not turn this into full negative governance; this lesson only decides whether terms are the one first-cycle variable.
Where to verify it
Admin fields and tool guardrails decide what changes in cycle one
Do not bring one dashboard view into the meeting or chase account buttons. The first cycle needs one record with paths, fields, proof, limits, allowed action, and frozen items.
Tracking and order reconciliation
Google Ads > Goals > Conversion actions; GA4 purchase; Shopify Orders.
Required fields
- conversion action, primary / secondary, status
- transaction_id, value, currency
- order id, net sales, discount, refund
Whether CPA / ROAS can be used to judge first-cycle action.
It does not prove budget, structure, or bidding should change now.
If it does not reconcile, only fix tracking and reconciliation; pause optimization conclusions.
Freeze budget, bidding, keywords, page, and copy.
Search terms and waste control
Google Ads > Insights and reports > Search terms; Keywords; Negative keywords; Change history.
Required fields
- search term, matched keyword, match type
- clicks, cost, conversions, Conv. value / cost
- negative level, reason, change time
Whether spend went to clear waste terms or promotable high-intent queries.
It does not prove every non-converting term should be negated.
Add only obvious negatives, with negative level and reason written.
Freeze budget, page, bidding, and ad copy.
Page path and checkout friction
GA4 Landing page / events; Shopify checkout / orders; CRO page evidence.
Required fields
- landing page, source / medium, Final URL
- view_item, add_to_cart, begin_checkout, purchase
- checkout error, mobile device, page version
Whether traffic promise, page fit, or checkout path has clear friction.
It does not prove campaign structure has failed.
Fix one page or checkout variable, such as shipping promise, price explanation, or payment error.
Freeze search terms, budget, bidding, and account structure.
Budget and profit guardrail
Google Ads Budget / Change history; ROAS calculator; Pricing calculator; Shopify order economics.
Required fields
- current average daily budget, previous budget, change time, spend pace
- CPA, ROAS, break-even ROAS, Max CPA
- contribution profit, refund reserve, inventory cover, rollback trigger
Whether this small budget test has profit room and a stop line.
It does not prove scale readiness or stable cost at higher budget.
After tracking, terms, and page pass, make only a small budget change and write the rollback trigger.
Freeze bid strategy, page, keywords, and copy.
Review cases
Bad week-one data can come from different layers
Optimization is not acting the moment something looks wrong. Translate the week signal into a cause layer, then limit the cycle to one variable.
Low impressions, low clicks, no conversions.
Bad first impulse: Rebuild the campaign or double the budget.
Correct frame: This is not yet a conversion problem; check search volume, rank, and ad approval first.
Allowed this cycle: This cycle may only add high-intent terms or fix approval/rank problems; page and bidding stay frozen.
Clicks are present, terms are relevant, but the page does not convert.
Bad first impulse: Immediately negate all non-converting terms.
Correct frame: High-intent non-conversion is not always a keyword problem; price, trust, shipping, mobile, or payment may be the blocker.
Allowed this cycle: This cycle changes only first-screen proof or shipping/return promise; keyword structure stays frozen.
First orders arrived, but CPA is above the affordable line.
Bad first impulse: Cut budget hard or switch to a tight tCPA immediately.
Correct frame: First decide whether high CPA comes from low sample, poor terms, weak CVR, or insufficient AOV/margin.
Allowed this cycle: Choose one variable only: control waste terms, fix page, adjust budget lightly, or wait for more sample.
20oz tumbler day-7 drill
Split day-7 data into tracking, sample, search terms, and page path
The same data can point to different actions. Split evidence layers before choosing one primary variable.
Scenario: a $29 20oz leak-proof tumbler, 7 days, $180 spend, 96 clicks, 2 Ads purchases, 3 Shopify orders; terms include leak proof tumbler, 20 oz travel mug, custom tumbler bulk, free coffee cup, with 8 carts and 1 payment failure.
Ads reports 2 purchases, Shopify shows 3 orders.
Wrong reaction: Change budget from platform ROAS.
Better read: Reconcile transaction ID, value, currency, and source first.
This cycle allows: Fix tracking or mark the readout; do not move budget.
Search terms include free coffee cup.
Wrong reaction: Negate every term with no conversion.
Better read: Handle clearly irrelevant terms only; keep high-intent low-sample terms.
This cycle allows: Add clear negatives, freeze budget and page.
8 carts, 4 checkouts, 1 payment failure.
Wrong reaction: Expand terms and budget.
Better read: The page and checkout already show friction.
This cycle allows: Fix one of shipping, returns, or payment path.
CPA is above the affordable line.
Wrong reaction: Switch to tCPA or cut budget hard.
Better read: Split sample, term quality, page CVR, and AOV / margin.
This cycle allows: Choose one primary variable and write rollback conditions.
30-minute meeting script
The review meeting has one job: agree on one variable and frozen items
Long meetings often muddy the account. Thirty minutes is enough to confirm evidence, choose the variable, and write review and rollback conditions.
0-5 min
Confirm tracking and order reconciliation.
Required output: Pass / fail / direction-only.
Do not drift into: Do not discuss budget first.
5-10 min
Confirm sample and observation window.
Required output: Spend, clicks, conversions, days, affordable CPA comparison.
Do not drift into: Do not decide from one day.
10-17 min
Read search terms and obvious waste.
Required output: High-intent, suspicious, irrelevant terms.
Do not drift into: Do not negate every non-converting term.
17-23 min
Read page path and checkout signals.
Required output: Browse, cart, checkout, payment failure, quick bounce.
Do not drift into: Do not blame all page friction on traffic.
23-28 min
Choose the only primary variable.
Required output: Allowed move, frozen items, responsible lead, review date.
Do not drift into: Do not change budget, terms, copy, page, and bidding together.
28-30 min
Write rollback conditions.
Required output: Continue / pause / rollback trigger metric.
Do not drift into: Do not close with we will see next week.
Stop / Go
The goal is making the next decision clearer
This is not proving activity. It turns every account action into reusable evidence.
Changing budget before tracking QA.
Conversion, value, currency, and order reconciliation pass.
Proof needed: Conversion acceptance sheet and test order are complete.
Rebuilding campaign after two no-conversion days.
Judge impressions, clicks, terms, page path, and sample first.
Proof needed: No-conversion first-week router is complete.
Changing budget, bidding, keywords, copy, and page on one day.
One primary variable, frozen items written.
Proof needed: Decision log has one allowed change and frozen items.
Negating every non-converting term at once.
Classify high-intent, suspicious, and irrelevant before acting.
Proof needed: Search-term evidence explains each negative.
Copyable lesson notes
Turn the current choices into a reviewable optimization note
Click the no-conversion router and first-cycle move simulator first, then copy this note. It carries your selected evidence layer, allowed action, stop action, frozen items, and next route.
Current copyable note
This is not a generic template. It is generated from your current selections. Copy it, then fill the blanks with your account data.
Current pressure: Google Ads has early data, but budget, search terms, page, and bidding should not change together. First proof: the no-conversion router is checking "Are there impressions and clicks?"; the first-cycle move simulator is on "Tracking not trusted". This week's action: change one primary variable only. Allowed move: "This cycle only fixes measurement and adds test-order proof plus reconciliation notes.". Stop action: do not do "Using CPA / ROAS to change budget or bidding strategy.". Frozen items: Freeze budget, bidding, keywords, and page. Change control: current selection "Waste query is spending"; primary variable: Add one negative keyword set only, scoped to ad group or campaign first; do not touch budget or page.; change history line: Change history: 2026-__-__, added negative ____, level ____, reason: Search terms spent ____ with no purchase intent. Observation window: Watch 3-7 days or one comparable spend window; check whether high-intent impressions, clicks, and CPA are preserved. Rollback trigger: If high-intent queries or core keyword impressions drop sharply, revert the negative and narrow match type or level. Do not co-change: Do not also change budget, RSA, Final URL, bid strategy, or page hero. Causality check: Budget raised and negatives added same day; mixed changes would make this unclear: If CPA drops next week, you cannot tell whether budget found better traffic or negatives removed waste. If orders drop, you cannot tell whether budget learning moved or negatives blocked real demand. Keep only this variable: This cycle only adds one clearly irrelevant negative set. Keep budget at $30 and discuss budget next cycle. Campaign surface: Search: separate query, match, and promise first. Read first: Write Search terms, matched keyword, match type, location/language, ad approval, and Final URL. When low-volume or privacy-limited queries are not shown row by row, record “not visible” as a gap rather than proof of no demand or no waste.. Urgent or eligibility route: When approval, location/language, duplicate Purchases, or a checkout promise is clearly wrong, this is not a seven-day experiment. Preserve the current readout and Change history, have the authorized account lead contain or repair that fault, then start a fresh observation window from the repair date.. Normal-experiment route: When tracking and page path are readable and a clearly irrelevant query is spending, this cycle may add one scoped negative set; budget, RSA, page, and bidding remain frozen.. Surface record: Write campaign_surface=Search, query/keyword/match, approval status, one action, old/new value, observation window, rollback trigger, and next readout.. Surface boundary: This is not full negative-keyword governance and does not prove an unseen query is absent, a keyword has no value, or the account is ready to scale.. Admin fields: write Conversion actions, GA4 purchase, Shopify Orders, Search terms, Negative keywords, Landing page events, Change history, and ROAS calculator / Pricing calculator into one record; include at least transaction_id, value, currency, search term, match type, Final URL, add_to_cart, begin_checkout, checkout error, average daily budget, break-even ROAS, Max CPA, and rollback trigger. Check window: write the review date and use CPA, ROAS, CVR, search-term quality, or checkout-path signal to continue / pause / roll back. Next route: if the problem is search terms, continue to search terms, negatives, and match types; if it is budget pacing, return to budget and bidding; if it is page friction, go into CRO page evidence review.
Closeout: write one reviewable optimization conclusion
State which proof supports the move, which variable changes in the first optimization log, when to review, and which metric decides continue or rollback. If you cannot write it, do not change the account yet.
Series navigation
Back to Google Ads Basics; the next lesson reviews search terms, negatives, and restructuring.