About this video
Write down a weekly keyword decision before automating it, then build a cleanup rule draft and inspect its conditions, action and timing so every change is explainable. Chapters 0:00 Turn a repeated decision into a rule 0:19 Use three conditions together 0:41 Understand AND before saving 1:10 Choose a bounded action 1:28 Separate lookback, delay and cooldown 1:54 Review the saved draft ScaleSKUs connects your Amazon Seller Central and Amazon Ads account to the AI you already use, such as Claude, ChatGPT or Gemini, over MCP. Ask in plain language, review the evidence, and approve every change. ▶ Start your 30-day free trial: https://scaleskus.com/mcp ▶ Hinglish mein dekhein: https://youtu.be/4jCnrDIr8GM ▶ Full playlist: https://www.youtube.com/playlist?list=PLKDH05txqnqI
Transcript
If you make the same keyword decision every week, write down the logic before automating it. In this lesson, we will create a keyword-cleanup draft and inspect the conditions, action and timing. The goal is a repeatable decision you can explain, not a rule that changes as many bids as possible. Start by describing the manual check in your own words.
Our example needs at least twenty clicks, at least five hundred rupees of spend, and zero orders across a fourteen-day lookback. Clicks give a minimum sample. Spend makes the issue meaningful. Zero orders identifies the behaviour we want to review. These thresholds are starting examples for this account; choose thresholds that fit your own prices, margins and usual cost per click.
All three conditions use AND. Look at these illustrative examples. Twenty-five clicks, six hundred and fifty rupees of spend, and zero orders passes all three checks. Twelve clicks fails the click threshold even if spend is high. Thirty clicks with one order fails the zero-order condition. With OR, one condition could be enough to trigger a change, producing a very different rule.
Always read the combined logic as a complete sentence. The draft reduces the bid by ten percent and stores a five-rupee minimum. A thirty-rupee bid would become twenty-seven rupees after one reduction. The floor limits how low the action can push a bid, but it does not decide how often the action should happen. Give the rule a descriptive name, such as Weekly keyword cleanup, so someone reviewing the account can understand its purpose.
Three timing concepts deserve separate checks. Lookback is the period used to calculate performance. An attribution delay excludes recent data that may still receive orders. Cooldown controls how soon another action can happen. The saved draft has a fourteen-day lookback and a twenty-four-hour cooldown; it does not store an explicit attribution delay or a seven-day cooldown. A weekly name does not create a weekly schedule.
Check the actual execution settings and reporting treatment before enabling the rule. Retrieve the rule after saving and compare its values with your intended logic. This lesson ends with a reviewable draft: three AND conditions, a ten-percent reduction, a five-rupee floor, and the saved timing settings. Your practice task is to test three example keywords on paper, explain which ones qualify, and choose a review cadence.
When a rule is enabled, inspect its action log and the affected keywords. Automation is most useful when the decision stays understandable and the results are checked.
More videos
2:53
Create Scoped Automation (Hinglish) · ScaleSKUs MCP Academy #08
1 Oct 2026
4:48
Action Forensics · ScaleSKUs MCP Academy #20
1 Oct 2026
4:41
Rule Coordination · ScaleSKUs MCP Academy #19
1 Oct 2026
4:42
Scope Validation · ScaleSKUs MCP Academy #18
1 Oct 2026
4:44
SP SB Intent · ScaleSKUs MCP Academy #17
1 Oct 2026
4:48
Competitor Fit · ScaleSKUs MCP Academy #16
1 Oct 2026