Text version of this lessonExpand
A single metric almost never tells the whole story. High CTR does not mean buyers. Low CPC does not mean efficient traffic. High ROAS does not mean the campaign can scale. This lesson does not reteach the whole advertising analytics system. It focuses on one Google Ads backend readout: verify tracking, then read traffic, page, conversion, and profit action in order. This lesson gives you a metric reading chain sheet and a metric contradiction practice: find the broken layer first, then choose the one action allowed this round.
Lesson output: metric reading chain sheet
Beginners often stare at one number: high CTR means the ad won, low CPC means traffic is cheap, high ROAS means raise budget. A real review asks a better question: which layer does this number describe, what conclusion does it support, and what counter evidence is missing?
| Decision layer | Main metrics | What it asks | First check | Allowed action |
|---|---|---|---|---|
| Impression to click | Impressions, CTR, CPC | Does the ad reach relevant searches at acceptable click cost? | Keyword intent, location, language, ad promise, competition | Adjust terms, match type, and copy before budget |
| Click to page | LPV, engagement, CVR | Does the page support the ad promise and user intent? | Hero, price, trust proof, shipping, mobile, speed | Fix page or narrow promise before blaming only ads |
| Page to order | Conversions, CPA, Purchase | Are conversions real, deduplicated, and business-relevant? | Checkout, payment, inventory, coupon, transaction ID, value | Reconcile conversion definitions before acting on CPA |
| Order to profit | ROAS, AOV, refunds, margin | Does revenue become contribution profit and workable payback? | Refunds, discounts, shipping, payment fees, SKU margin, new vs returning | Return to the profit sheet before scaling, slowing, or shifting SKU group |
Bring the previous article's budget guardrail into the readout: find the break in the same window
The previous article, Shopify Google Ads Budget Setup: Daily Budget, Smart Bidding, tCPA, and tROAS, already wrote the budget, bidding strategy, observation window, and stop line. This lesson does not decide whether to spend more again. It finds the break in the same Search sample. Keep the 20oz leak-proof travel mug case and place Google Ads, GA4, Shopify, and profit fields on one row for the same 7-day window: verify tracking, then read traffic, page, conversion, and profit action. When the numbers disagree, treat that as an evidence gap instead of choosing the best-looking metric to speak for the account.
From budget action to metric reading chain
- Bring from the previous article: this-cycle budget action, frozen variables, observation window, Search structure, accepted conversion boundary, and profit / cash stop line.
- This lesson completes: place CTR, CPC, CVR, CPA, and ROAS across impression, click, page, order, and profit layers, then add one counter-evidence field to every attractive metric.
- Next route: take the reading chain into Shopify Google Ads Optimization After Launch: 7-Day Review, Search Terms, Budget, and Rollback Lines and change one primary variable. Search terms, page, measurement/value, profit, and budget each need their own route.
Same-week data: separate surface metrics from profit actions
CTR, CPC, CVR, CPA, and ROAS can send different signals in the same week. The beginner mistake is choosing the best-looking number to justify the action you already want. A stronger read treats the metric as a symptom first, then finds the field that actually changes profit.
| What this week looks like | Same-week data | What it only proves | Profit fields that matter | This-cycle action | Do not misread it |
|---|---|---|---|---|---|
| High CTR, profit unchanged | 1,200 impressions, 70 clicks, 5.8% CTR, $1.20 CPC, 3 orders, Conv. value / cost 2.4, but Shopify shows one refund and one heavy discount | The ad promise attracted clicks and the platform revenue readout looks decent | Shopify net sales, refund, discount, SKU margin, shipping cost, payment fee, contribution profit | Do not raise budget this cycle. Add refund and post-discount profit next to ROAS; if profit is weak, adjust offer or product grouping first | Do not scale just because CTR is high and ROAS looks good |
| Low CPC, weak order quality | CPC drops from $1.80 to $0.72 and clicks rise, but add_to_cart is rare and search terms include tutorial, replacement, and free intent | Clicks are cheap; it does not prove the traffic has buying intent | Search terms, match type, add_to_cart, begin_checkout, purchase, no-conversion spend, Final URL | This cycle only tightens queries, adds negatives, or adjusts page promise | Do not keep broadening match just to preserve low CPC |
| Low CPA, high refunds | Cost / conv. is $18, better than the $32 Max CPA, but Shopify refunds and support tags rise | Conversions were cheap; it does not prove those conversions are worth keeping | Refund reason, support tag, discount code, replacement cost, real Max CPA, contribution profit | This cycle only fixes ad promise, page qualifiers, or low-quality queries; CPA must sit next to refund and support reasons | Do not raise budget or tighten tCPA just because CPA is low |
The point is not another template to memorize. It is a reading order: same week window, same order set, same profit line. Surface metrics tell you where to inspect; profit fields decide whether the action can enter the account.
Translate the five acronyms into plain business questions
CTR is click-through rate: how many people who see the ad choose to click. It signals whether the ad promise and search intent are attractive, but it does not prove buying intent.
CPC is cost per click. Read it with search-term quality, competition, and the post-click path. Cheap clicks without carts or orders are still waste.
CVR is conversion rate after the click. It often reveals page, price, trust, shipping, payment, or intent-fit problems.
CPA is average cost per conversion. The conversion must first be a real business action, not a low-quality event.
ROAS is revenue return on ad spend, often read through Conv. value / cost in Google Ads. It is not profit. Refunds, discounts, shipping, payment fees, and margin still matter.
Feed is the product data file, not the ad creative itself. Shopping and PMax read the Feed for title, price, stock, image, product category, and sale status. If Feed fields are wrong, the ad can still earn clicks while the page, price, or inventory path fails, which distorts CVR and ROAS.
Metric contradiction practice: good-looking numbers still need counter evidence
The risky moment is not one bad metric. It is one attractive metric while the business result does not follow. These five conflicts are common beginner traps.
| Conflict | False conclusion | First check | Allowed action | Do not do |
|---|---|---|---|---|
| High CTR, low CVR | The ad won, so raise budget | Sample search terms, ad headlines, and the landing first screen for promise match | Narrow the ad promise, add first-screen proof, or lower the priority of curiosity terms | Do not scale only because CTR is high |
| Low CPC, no carts | Traffic is cheap, so keep buying | Read intent strength, engagement, and carts by search term and ad group | Cut weak-intent terms and keep terms with page behavior under observation | Do not treat low CPC as efficiency |
| Low CPA, weak profit | Acquisition cost is healthy, so scale | Break orders into contribution profit, new/returning, SKU margin, and refunds | Update affordable CPA and split stronger-margin products or new-customer judgment | Do not use ad-platform CPA as the business profit line |
| High ROAS, tiny volume | ROAS is high, so scale now | Split brand/non-brand, new/returning, sample size, and recent conversion delay | Run only a small expansion test and observe non-brand or new-customer performance separately | Do not treat tiny-sample ROAS as repeatable scale |
| Ads conversions high, Shopify flat | The platform proves ads improved | Check conversion action, transaction ID, value, currency, timezone, attribution window, and duplicate counts | Fix measurement before discussing CPA, ROAS, or budget | Do not change budget before reconciliation passes |
Profit counter-evidence bridge: put Ads, GA4, Shopify, and profit fields on one row
This step blocks a common budget mistake: the Google Ads number improves, so the team immediately says to raise budget. A real review puts the attractive metric into one record. Ads explains the advertising basis, GA4 explains the page and event path, Shopify explains order facts, and the ROAS / Pricing tools explain profit boundaries. Until those four field groups line up, CTR, CPA, and ROAS are clues, not scale approval.
| Good-looking metric | Ads fields | GA4 fields | Shopify fields | Profit / tool fields | Freeze line |
|---|---|---|---|---|---|
| ROAS looks good, but contribution profit is weak | Cost, Conv. value, Conv. value / cost, brand / non-brand, new / returning | source / medium, landing page, purchase, transaction_id, items, refund events | order id, net sales, discount, shipping charged, refund, SKU / variant, customer type | break-even ROAS, product cost, shipping cost, payment fee, refund reserve, contribution profit | Do not replace the profit sheet with platform ROAS, and do not use brand ROAS to justify non-brand scaling. |
| CPA is low, but refunds and support cost are high | Cost / conv., Conversions, conversion action, search term, Final URL, campaign type | purchase, items, coupon, source / medium, landing page, return / refund events | refund reason, return request, support tag, discount code, shipping problem, product complaint | refund reserve, support handling cost, replacement cost, real Max CPA | CPA cannot be a scaling signal until refund and support reasons are in the review. |
| CVR is high, but AOV and margin are low | Landing page, Final URL, Conversions, Conv. value, AOV proxy, campaign / ad group | view_item, add_to_cart, begin_checkout, purchase, items, item revenue, coupon | AOV, net sales, discount, SKU margin tier, shipping subsidy, bundle attach rate | bundle margin, free-shipping threshold, gross margin, contribution profit, affordable CPA | When CVR is high but AOV / margin misses the line, do not translate the page win directly into ad scaling. |
Write the review in one sentence: which metric looked good, which business counter-signal sits next to it, which fields are aligned, which fields are still missing, and which single variable may change next. If the team can only say “ROAS looks good” or “CPA is low” without net sales, refund, SKU margin tier, and contribution profit, do not raise budget this round.
CPA and ROAS need trust checks before budget decisions
Google Ads Help definitions for Conversions, Cost/conv., Conv. rate, and Conv. value/cost all depend on the same condition: your conversion action, conversion value, and counting logic must represent a real business action. Otherwise CPA and ROAS are clues, not budget conclusions.
| Trust check | Question | Risk if missing |
|---|---|---|
| Conversion action | Does it represent a real purchase, lead, or valuable action? | Low-quality events make CPA / ROAS unusable |
| Value / currency | Can amount, currency, and refund basis be explained? | Wrong value misleads both system and team |
| Sample size | Are there enough clicks, orders, and window length? | Tiny-sample ROAS is not scale proof |
| Traffic mix | Are brand, remarketing, returning, and new customers split? | Blended ROAS inflates acquisition judgment |
| Profit truth | Are refunds, discounts, shipping, payment fees, and margin included? | Ad revenue can look good while profit fails |
Official metric boundaries: reporting columns calculate, they do not prove profit
Google Ads Help gives the calculation basis: CTR is clicks divided by impressions, Avg. CPC is total click cost divided by clicks, Conv. rate is conversions divided by trackable interactions, Cost / conv. is total cost divided by the conversions in the Conversions column, and Conv. value / cost is total conversion value divided by total ad interaction cost. These are calculation columns, not business conclusions.
Read them this way: CTR and CPC only start the impression-to-click check; CVR and CPA require conversion action, counting, and eligible interaction review; Conversions, All conversions, and by conv. time need a written click-time versus conversion-time basis; Conv. value / cost must return to refunds, discounts, shipping, payment fees, and SKU margin; Target ROAS is a bidding target, not proof that profit is healthy.
| Official metric | How this lesson reads it | What it cannot prove |
|---|---|---|
| CTR / Avg. CPC | Read query fit, ad promise, location/language, and competition | It cannot prove that the page converts or incremental clicks are profitable |
| Conv. rate / Cost per conversion | Confirm conversion action, counting, and eligible interactions first | If the action is shallow, duplicated, or unreconciled with Shopify, CPA should not drive budget |
| Conversions / All conversions / by conv. time | Use one 7-day Ads, GA4, and Shopify window, and write click-time or conversion-time basis | Column differences, attribution windows, and 24-48 hour processing delay do not prove ad quality by themselves |
| Conv. value / cost | Read it with refunds, discounts, shipping, payment fees, and SKU margin | It is not a profit statement and cannot prove new-customer value, cash timing, or scale readiness |
| Target ROAS | Read Avg. target ROAS, Actual ROAS, recent conversion delay, and profit basis first | Hitting Target ROAS does not prove business profit; a target set too high may limit traffic |
By-conversion-time columns: separate click time from conversion time
Normal Google Ads columns are useful for optimization learning, while by-conversion-time columns explain what happened in the current sales window. The review sheet must state whether it is reading click time or conversion time before Ads, GA4, and Shopify are compared.
| Column | How to read | Use when | Misread risk |
|---|---|---|---|
| Conversions | Read conversions on the normal Google Ads attribution basis, usually for optimization and bidding learning. | Judge whether the campaign has enough conversion signal for the next learning cycle. | Do not treat it as same-day Shopify orders; it may enter reports on click time. |
| Conversions by conv. time | Read by the actual conversion time so GA4 purchase and Shopify Orders can be reconciled in the same window. | Use it when Ads shows many conversions but current-window orders look flat, separating click time from conversion time. | It is for current-window readout, not a replacement for optimization columns in bidding judgment. |
| Conversion value | Read attributed value on the normal basis to inspect the value signal given to Smart Bidding. | Check whether value, currency, transaction_id, and pre/post-refund revenue belong to one record. | It is still not profit; read it with refunds, discounts, shipping, payment fees, and SKU margin. |
| Conversion value by conv. time | Read value by conversion time to explain value changes in the actual current sales window. | Use it when Ads ROAS and Shopify sales disagree this week, separating conversion delay from value quality. | If Shopify discounts, refunds, or tax basis are unclear, value by time still cannot prove profit. |
| Cost / conv. | Divide cost by conversions in the Conversions column to read cost for one valid conversion. | Before budget discussion, confirm the conversion action represents a real order or high-value action. | With shallow actions, duplicate counts, or Shopify mismatch, low CPA cannot release budget. |
| Conv. value / cost (ROAS) | Read platform ROAS as conversion value divided by ad cost; it is revenue efficiency, not a profit statement. | Use it with break-even ROAS, Max CPA, and contribution profit before scaling. | If ROAS passes but discount, refund, or margin fails, complete profit readout instead of raising budget. |
| Value / conversion | Read average value per conversion to inspect AOV, bundle mix, and low-value orders. | Use it when CVR is high but profit is flat, checking order quality instead of celebrating conversion rate. | Averages can hide SKU mix; return to Shopify SKU, refund reason, and margin. |
Metric admin evidence paths: five metrics must land in backend fields
Do not end a review by copying one dashboard view. A view only proves what you looked at that day. A useful review writes the fields into one record: where the number came from, what it proves, what it still cannot prove, and which evidence gap this round will close.
This turns CTR, CPC, CVR, CPA, and ROAS from definitions into an operating decision the team can check next week. If the fields are not written down, the next meeting restarts the same argument. If they are written down, the next meeting only checks whether the read was validated.
| Admin path | Fields to record | Proves | Still cannot prove | This cycle action |
|---|---|---|---|---|
| Google Ads Columns / Segments | Impressions, Clicks, CTR, Avg. CPC, Cost, Search impr. share, device, network, campaign, ad group, keyword, match type, search term. | Whether traffic entry is relevant, click cost is acceptable, and a device or network slice is distorting the read. | It cannot prove that the page converts or that incremental clicks are profitable. | Split by search term, match type, and device before changing copy, negatives, or match type. |
| Search terms / Landing pages + GA4 page behavior | Search term, Final URL, landing page, engagement rate, view_item, add_to_cart, begin_checkout, checkout error, mobile, first-screen proof. | Whether the ad promise, search intent, and landing page fit. | It cannot prove that orders are real or profit is healthy. | Sample 20 search terms and matching landing first screens, then mark promise match, mismatch, or price friction. |
| Conversions / GA4 purchase / Shopify Orders | Conversions, All conversions, Cost / conv., Conv. rate, by conv. time, conversion action, transaction_id, value, currency, order id, net sales, discount, refund. | Whether CPA and CVR come from real purchases or valid actions, and whether Ads, GA4, and Shopify reconcile. | It cannot prove post-refund profit, new-customer value, or cash payback. | Reconcile transaction_id, value, currency, and order id in one 7-day window before reading CPA or ROAS. |
| ROAS calculator / Pricing calculator + order profit | Conv. value / cost, AOV, break-even ROAS, Max CPA, product cost, shipping cost, payment fee, refund reserve, SKU margin, contribution profit. | Whether current CPA and ROAS survive margin, fees, and refund pressure. | It cannot prove that cost will stay stable at scale or that inventory and cash are enough. | Put order economics into the ROAS calculator and Pricing calculator, then write this round's affordable Max CPA and break-even ROAS. |
Add one Admin fields line to the copyable lesson notes: Google Ads Columns / Segments, Search terms / Landing pages, GA4 purchase, Shopify Orders, and ROAS calculator / Pricing calculator must live in one record; include at least CTR, Avg. CPC, Cost / conv., Conv. value / cost, transaction_id, value, currency, net sales, refund, break-even ROAS, and Max CPA.
Reading cases: translate metrics into the next diagnostic question
High CTR, low CVR: Do not call the creative a winner yet. Sample 20 search terms and matching landing first screens. Mark promise match, promise mismatch, or price friction. If the ad promises leak-proof performance, the first screen needs proof of that promise.
High ROAS, low order count: Split brand/non-brand, new/returning customers, SKU margin tier, and refund risk. A few high-AOV orders can lift the result without proving scale.
CPA looks good, margin is tight: Break order revenue into contribution profit, then update affordable CPA. The ad-level acceptable CPA may not match what the business can truly afford.
Do not ask "what is a good CTR" before defining the traffic job
Beginners often search for a universal "good Google Ads CTR" or "normal CPC." Benchmarks can be useful, but they cannot decide your next action by themselves. Country, category, query intent, brand share, device, and competition all change the number. A branded search campaign for a 20oz tumbler may have a strong CTR because people already know the brand; the same CTR in cold non-brand traffic means something different.
Before reading metrics, write the job of the campaign. A cold Search campaign finds people with clear demand. Shopping helps product facts and price enter comparison. Performance Max may find conversion opportunities across inventory. Different jobs create different safe ranges for CTR, CPC, CVR, CPA, and ROAS. Do not use branded ROAS as the target for non-brand acquisition. Do not use remarketing CPA to prove that a new product can acquire cold buyers.
| Traffic role | How to read metrics | Common false read |
|---|---|---|
| Brand / returning demand | CTR and ROAS are often stronger, but incremental value needs separate proof | Treating existing demand as new acquisition ability |
| Non-brand Search | Read search intent, CPC, CVR, and first-order contribution profit | Pausing only because CPC is high without checking order quality |
| Shopping / feed traffic | Read click cost, product price competitiveness, feed fields, and inventory fit | Blaming low CVR only on ads without checking product data and page consistency |
| PMax / mixed traffic | Split brand, remarketing, new customers, product groups, and landing pages | Using blended ROAS to prove every dollar is healthy |
20oz tumbler metric review: 30 minutes, one action
Imagine a Search campaign for a 20oz tumbler. In the last 7 days it has 1,200 impressions, 70 clicks, 5.8% CTR, $1.20 average CPC, $84 cost, 3 purchases, 4.3% CVR, $28 CPA, and 2.4 Conv. value / cost. CTR and ROAS look acceptable. But Shopify shows that one order used a heavy discount and one later refunded, leaving thin real contribution profit.
Do not raise budget first, and do not stop the campaign immediately. Step one: align the window. Read Google Ads, GA4, and Shopify over the same 7 days, without mixing time zones or attribution windows. Step two: mark the broken layer. Impression-to-click does not look broken, click-to-page may not be broken, but order-to-profit needs review. Step three: write counter evidence. Next to ROAS, write refunds, discounts, shipping, margin, and new-customer share. Step four: release one action only. This round does not change budget; it adds post-discount contribution profit and refund reason to the next review.
| Step | What to write | Output |
|---|---|---|
| Matching window | Same 7 days across Ads, GA4, and Shopify | No mix of yesterday, last week, and this month |
| Broken layer | Choose impression, click, page, order, or profit | This case marks order-to-profit first |
| Counter evidence | Write business counter signals next to attractive metrics | Refunds and post-discount profit sit next to ROAS |
| One action | Change one variable and observe 7 days | No budget change until profit readout is complete |
From metric to action: do not let five numbers run the meeting
Every review should turn metrics into one action, not copy dashboard screenshots into a meeting. Ask in this order: first, whether CTR and CPC show a relevant traffic entry; second, whether CVR and page behavior show a working landing path; third, whether CPA fits the affordable cost for one valid conversion; fourth, whether ROAS and order quality survive refunds, discounts, fulfillment, and margin; fifth, whether Shopify or finance facts support the ad-platform conclusion.
If more than one or two of these questions are unanswered, do not make a budget move. Budget changes belong after the reading, not in place of the reading. When CTR is low, inspect search terms and ad promise. When CVR is low, inspect the landing hero and checkout. When CPA is high, inspect CPC and affordable CPA. When ROAS is high but profit is weak, inspect product economics and refunds. Change one thing at a time so the next review can tell what actually worked.
30-minute review sheet: stop debating feelings
The real output is not a screenshot from the dashboard. It is a reviewable metric reading sheet. At minimum, include nine columns: date window, campaign / ad group, main traffic role, five core metrics, most likely broken layer, counter evidence, allowed action, forbidden action, and next check time. That keeps the next review from restarting the same argument about whether the problem is ads, page, or product economics.
Thirty minutes is enough. Use the first 5 minutes to align the window and data sources. Use minutes 6 to 12 to read CTR, CPC, CVR, CPA, and ROAS without deciding yet. Use minutes 13 to 20 to find counter evidence such as search terms, landing hero, Shopify net orders, refunds, and margin. Use minutes 21 to 26 to write one allowed action. Use the last 4 minutes to write the pause condition and next review date. Any opinion without evidence goes into the to-check list, not this round's action.
| Field | What to write | Why it matters |
|---|---|---|
| Date window | Same time range across Ads, GA4, and Shopify | Avoid timezone and attribution-window confusion |
| Main traffic role | Brand, non-brand, Shopping, PMax, remarketing, or new customer | Avoid using the wrong safe range |
| Most likely break | Impression, click, page, order, or profit | Focus action on one layer |
| Counter evidence | Every good metric needs one business counter signal | Prevent attractive numbers from pushing premature scale |
| Allowed action | Change one variable this round | The next review can identify the cause |
Copyable lesson notes: turn this metric read into a reviewable action
If this lesson only leaves you with definitions, the dashboard will still pull you around next time. The useful output is a reviewable note: current pressure, first proof, counter evidence, this week's action, stop action, and the next check window.
Google Ads metric reading copyable lesson notes
Current pressure: Do not move budget from one CTR, CPC, CVR, CPA, or ROAS number. First decide whether the break is in impressions, clicks, page, order, or profit.
First proof: In the same 7-day window, record Google Ads clicks, cost, CTR, CPC, conversions, CVR, cost / conv., Conv. value / cost, plus Shopify net orders, refunds, and post-discount profit.
Counter evidence: Every attractive metric needs one counter signal: CVR next to CTR, carts or orders next to CPC, contribution profit next to CPA, and refunds, new-customer share, and SKU margin next to ROAS.
This week's action: Change one variable only. For example, fix the landing hero, narrow search terms, reconcile conversion value, or complete the profit readout.
Stop action: Do not use CPA / ROAS for budget moves before conversion action, value, currency, transaction ID, refunds, and timezone are aligned.
Admin fields: Google Ads Columns / Segments, Search terms / Landing pages, GA4 purchase, Shopify Orders, and ROAS calculator / Pricing calculator must live in one record; include at least CTR, Avg. CPC, Cost / conv., Conv. value / cost, transaction ID, value, currency, net sales, refund, break-even ROAS, and Max CPA.
Check window: Use the same 7-day basis next time. Do not mix different Google Ads, GA4, and Shopify windows.
Next route: If the break is traffic intent, study search terms, negatives, and match types. If the break is page conversion, study CRO / landing-page message match. If the break is measurement and value, study enhanced conversions and value quality. If the break is the profit line, use the ROAS calculator / Pricing calculator. If the break is budget action, study the first optimization cycle.
Break route map: decide optimization only after reading the metrics
The review sheet should separate traffic intent, page conversion, measurement and value, profit line, and budget action. Each break has a different next route; mixing them turns the account into guesswork.
| Break | What you see | Next route | Output |
|---|---|---|---|
| Traffic intent | CTR, CPC, or search terms show the wrong traffic is entering. | Study search terms, negative keywords, and match types first. | Keep terms, negative terms, watch terms, and why budget stays unchanged. |
| Page conversion | CTR is acceptable, but CVR, carts, or checkout do not carry the click. | Study CRO / landing-page message match before changing audience or budget. | One page variable, one proof location, and a 7-day observation window. |
| Measurement and value | Ads, GA4, and Shopify do not reconcile, or value, currency, and transaction_id are untrusted. | Study enhanced conversions and value quality before CPA / ROAS decisions. | One-order Ads, GA4, Shopify proof and a paused budget move. |
| Profit line | ROAS or CPA looks acceptable, but refunds, discounts, shipping, and margin do not support it. | Use the ROAS calculator / Pricing calculator for break-even ROAS, Max CPA, and contribution profit. | Whether budget is released, frozen, or held for profit readout. |
| Budget action | Evidence is usable, but the next cycle does not know what to change. | Study the first optimization cycle, changing one main variable and preserving change history. | Allowed action, forbidden action, review time, and rollback line. |
Stop / Go rules: a metric must drive one clear action
Review sentence
The current break is in the ____ layer; the proof is ____; the counter evidence is ____; this round we only change ____; we observe until ____; if ____ happens we continue, and if ____ happens we pause or roll back.
- Stop: Moving budget from one metric. Go: Write the broken layer first: impression, click, page, order, or profit.
- Stop: Using ROAS as profit. Go: Return ROAS to refunds, discounts, shipping, margin, and cash timing.
- Stop: Calling creative winner from high CTR. Go: Read CVR, search terms, and the post-click path together.
- Stop: Reading CPA / ROAS before conversion QA. Go: Align transaction ID, value, currency, and duplicate counts first.
How this connects: decide optimization only after reading the metrics
Metrics are not report decoration. CTR, CPC, CVR, CPA, and ROAS should explain whether the problem is query fit, page fit, tight budget, or untrusted value / profit logic.
- If you need the full advertising metric system, use Advertising Analysis first; this lesson turns Google Ads backend fields into this-cycle action.
- Return to guardrails: budget and bidding basics to confirm the current sample is readable.
- Next lesson: first optimization cycle to change one main variable per cycle and keep change history.