KDP Amazon Ads Automation: IF/THEN Rules for Pausing Keywords That Get Clicks but No Orders
InteliAds Team
KDP Ads
You open the Sponsored Products keyword list and see a dozen keywords with plenty of clicks and not a single order. Pausing them by hand every week is tedious, and pausing them too early can kill keywords that were about to convert. That tension is why kdp kdp ads automation matters: a written IF/THEN rule applies the same threshold to every keyword, every time, instead of relying on your mood that day.
This guide covers the first half of building that rule set: how to separate a bad keyword from an unlucky one, how to set the click threshold from your own numbers, and how to write the core pause rule with guardrails. For wider context on campaign structure, see the KDP ads guide.
Short answer: A good pause rule says: IF a keyword has reached a click threshold based on your conversion rate and royalty, AND it has zero orders in a fixed lookback window, THEN pause it or flag it for review. Set the threshold from your own data, not a round number copied from a forum. Add guardrails so new keywords, seasonal books, and series entry points are not cut off before they have a fair test. Run every rule in a dry run first so you can see what it would have paused.
Why a click-heavy, order-free keyword isn't automatically a bad keyword
Clicks with no orders can mean the keyword attracts the wrong shopper. They can also mean the keyword is fine and the sample is small. With a book that converts at 12 percent, a keyword still has about a 4 percent chance of showing zero orders after 25 clicks. That is rare, but across a campaign with 80 keywords, a few will land there by chance.
Automation has to respect that statistical reality. A rule that pauses at 8 clicks will cut good keywords constantly. A rule that waits for 200 clicks will bleed budget. The goal is a threshold where a zero-order result is unlikely enough to act on, yet cheap enough that you have not overspent finding out.
Three situations make zero orders misleading:
- Delayed purchases: shoppers click, read the sample, and buy days later, so recent clicks may not show orders yet.
- Read-through value: a keyword may drive a first-book click that leads to sales of later books in a series, which a single-book view hides.
- Page-level weakness: if the book page has few reviews or a weak description, every keyword underperforms, and pausing keywords will not fix it.
Before you automate anything, read your KDP royalties vs Amazon Ads sales comparison so you know which orders the ad console actually credits to your campaigns.
Setting the click threshold from your own conversion rate and royalty
The threshold has two ceilings. The first is statistical: how many clicks until zero orders is unlikely by chance. The second is financial: how much you are willing to spend on one keyword before it has earned something back. Use the lower of the two.
Here is a fresh worked example, a labeled hypothetical for a $14.99 paperback. The royalty is $4.20 per sale, the average CPC is $0.38, and the book converts at about 12 percent over the last 60 days. Break-even ACOS is $4.20 divided by $14.99, roughly 28 percent.
| Rule input | How to calculate it | Hypothetical value | How the rule uses it |
|---|---|---|---|
| Royalty per order | List price minus print cost, after Amazon's share | $4.20 | Sets the maximum spend before a keyword is a clear loss |
| Break-even ACOS | Royalty divided by price | 28% | Separates unprofitable keywords from merely slow ones |
| Average CPC | Spend divided by clicks | $0.38 | Converts a spend cap into a click cap |
| Conversion rate | Orders divided by clicks | 12% | Sets expected clicks per order, about 8 |
| Spend cap in clicks | Royalty divided by CPC | 11 clicks | Financial ceiling for one order's worth of testing |
| Statistical click threshold | Clicks where zero orders has about 4% chance | 25 clicks | Statistical ceiling before acting |
| Spend at threshold | Threshold clicks times CPC | $9.50 | Maximum loss per keyword, about 2.3 royalties |
| Lookback window | Days of data the rule reads | 30 days | Keeps old clicks from triggering a pause on a changed page |
In this example the financial ceiling is 11 clicks and the statistical ceiling is 25. A cautious author sets the rule at 25 clicks because it protects good keywords, accepting up to $9.50 of loss per keyword. A tighter budget might pick 18 to 20 clicks. Bid-desk tip: if you cannot justify your threshold with a royalty and a conversion rate, it is a guess, and the rule will encode that guess at scale.
If your book sells at a very low conversion rate, the math shifts quickly. At 5 percent conversion and a $0.38 CPC, one order costs about $7.60, which is more than the $4.20 royalty, so the problem is the page or the targeting, not just the keywords. InteliAds shows royalty-aware profit when KDP Sync is linked, which makes this calculation visible per campaign in one Amazon book ads dashboard.
Rule 1: Pause when clicks pass the threshold with zero orders in the lookback window
This is the core rule of kdp kdp ads automation. Write it as plain conditions so you can read it back in six months and know why it exists.
- IF keyword clicks in the last 30 days are 25 or more.
- AND keyword orders in the last 30 days equal 0.
- AND the keyword has been live for at least 14 days.
- THEN pause the keyword and add a note with the date and the click count.
Walk through a labeled hypothetical. A keyword such as "cozy mystery series" has 27 clicks, $10.26 in spend, and zero orders over 30 days, on the paperback above. It passes the 25 click threshold, has been live for 6 weeks, and loses the review. The rule pauses it, and you have capped the damage at roughly 2.4 royalties.
Now apply the same rule to a neighboring keyword with 19 clicks, $7.22 in spend, and zero orders. The rule does nothing yet. That is correct: it has not reached the threshold, and acting early would repeat the small-sample mistake.
Run a dry run before the rule goes live
A dry run shows which keywords the rule would have paused, without changing anything in the account. Review that list against your own judgment. If the rule would pause a keyword you know is a series entry point, tighten the conditions before switching it on. InteliAds includes IF/THEN rules with a dry run for this purpose, and you can compare tiers on the InteliAds pricing page.
Use targeting filters so the rule only touches what it should
Apply the rule by campaign, match type, or targeting type rather than across the whole account. A rule written for exact match keywords with a 25 click threshold is too strict or too loose for auto campaigns, which collect broader and noisier traffic. Targeting filters let you run different thresholds on different campaign groups from one place. If you want to test this on your own data, you can create an InteliAds account and connect your ad account.
Rule 2: Add guardrails for new keywords, seasonal books, and series read-through
A bare pause rule is dangerous because it treats every book and keyword the same. Guardrails are extra conditions that stop the rule firing when zero orders is expected or misleading. Write each one as an AND NOT condition on the core rule.
- Minimum age: skip keywords live for fewer than 14 days, so delayed orders can arrive.
- Seasonal exception: for holiday or seasonal books, extend the lookback window or exclude the campaign outside peak weeks.
- Series tag: exclude campaigns promoting book one of a series, or raise their threshold by 50 percent.
- Recent edits: skip keywords whose bid or page changed in the last 7 days.
Once guardrails exist, different keyword situations call for different rule actions. Pausing is not always the right first move.
| Keyword situation | Rule action to choose | Console step to take |
|---|---|---|
| 25+ clicks, 0 orders, live 14+ days, standalone book | Pause | Set the keyword status to paused in the ad group and log the date |
| 25+ clicks, 0 orders, but click-through rate is high and spend is low | Lower bid by 25 to 30 percent | Edit the keyword bid, then re-check after another 15 clicks |
| Search term from an auto campaign keeps clicking with no orders | Add as negative exact | Open the search term report and add the term as a negative exact in that campaign |
| Keyword under 14 days old with 30 clicks and no orders | Flag for review, no pause | Leave active, set a calendar check for day 15, and compare against the guardrail |
| Keyword in a book one campaign, 0 orders but later series orders rising | Exclude from rule | Tag the campaign as series entry and apply the higher threshold |
| Seasonal book outside its peak weeks | Pause campaign, not keywords | Pause at campaign level so keyword history stays intact for next season |
The pattern behind the table is simple: pause when the keyword is the problem, lower the bid when the keyword might be fine at a cheaper price, and use negatives when the search term is the problem. For details on when a bid cut beats a pause, see when to pause or lower a KDP keyword. Bid-desk tip: write the reason for every guardrail next to the rule, so a future you does not delete it as clutter.
Automation earns its place when the same decision repeats weekly across many keywords. A rule that says "pause after enough clicks and no orders" removes the slow bleed from Sponsored Products targets. It also removes your judgment on edge cases, so the rule has to be written with those edge cases in mind.
Where KDP Amazon Ads automation helps and where it misfires
Rules work best on high-click, zero-order targets in the 30 day window, especially in auto and broad campaigns where search terms multiply. They work poorly on new targets, seasonal keywords, and books whose value comes from Kindle Unlimited page reads rather than direct sales. Treat every rule as a filter that flags candidates, not a verdict.
Here is a fresh hypothetical, for illustration only. A $9.99 paperback earns a $3.40 royalty per sale, so break-even ACOS is about 34%. The keyword "cozy mystery series" has 44 clicks at an average CPC of $0.48, which is $21.12 spend, and 0 orders in 30 days. That spend equals more than six royalties, so a pause rule is reasonable here.
| IF condition (30 day window) | THEN action | Guardrail to add | Risk if missing |
|---|---|---|---|
| Clicks at or above 40 and orders equal 0 | Pause the keyword | Target must be older than 21 days | Pauses targets that never had a fair test |
| Spend above 5x royalty and orders equal 0 | Lower bid by 25% | Skip targets with recent bid changes | Stacked cuts that choke impressions |
| Search term has 15 or more clicks and 0 orders | Add as negative exact | Review against the source campaign first | Blocks a term that converts elsewhere |
| Clicks at or above 40, 0 orders, KENP reads present | Flag for manual review | Exclude from auto pause | Kills a keyword that feeds page reads |
Three situations commonly cause a misfire:
- Late attribution: orders can land days after the click, so a 7 day window under-counts conversions.
- Thin data: a low-volume book may never reach the click threshold, so the rule stays silent.
- Mixed match types: one threshold applied to auto, broad, and exact targets treats very different traffic as equal.
Bid-desk tip: write the rule in plain words first. If you cannot say what each condition protects you from, remove it.
Testing a pause rule on a past report before you switch it on
Before any rule touches live campaigns, run it against a report you already know. Export a 30 or 60 day targeting report and mark which keywords the rule would have paused. Then compare that list with what you would have decided by hand.
- Download the Sponsored Products targeting report for the last 30 days in the Amazon Ads console.
- Filter to clicks at or above your threshold and orders equal to zero.
- Remove targets created in the last 21 days.
- Check each remaining keyword for orders that appeared in a later report.
- Note any keyword you would never pause, then add a guardrail that excludes it.
- Only then enable the rule, starting with a lower-risk action such as a bid reduction.
If more than one in five flagged keywords is one you would keep, the rule is too blunt. Tighten the click threshold or lengthen the window and test again. See KDP royalties vs Amazon Ads sales for why spend should be judged against royalty, not ad sales alone.
What the InteliAds Sponsored Products manager does
The Sponsored Products manager in the Amazon book ads dashboard supports IF/THEN rules with a dry run, so you can see which keywords would match before anything changes. Targeting filters let you scope a rule to specific campaigns, match types, or targets. When KDP Sync is linked, profit views become royalty-aware instead of relying only on ad-attributed sales. Live changes are approved by the author, and nothing here guarantees a particular result. For wider context, read the KDP ads guide.
FAQ
Q: How many clicks with no orders should trigger a pause on a book that sells for $9.99? A: A common starting point is 40 clicks, or spend of about five to six times your royalty, whichever comes later. At a $3.40 royalty and $0.48 CPC, that is roughly $17 to $20. Adjust upward if your book page converts slowly.
Q: Should the lookback window be 14, 30, or 60 days for a low-volume book? A: Use 30 days as the default and 60 days when clicks are scarce. A 14 day window rarely gathers enough clicks and misses delayed orders. Pair the longer window with a click threshold so old data does not hide a recent decline.
Q: How do I stop a rule from pausing a keyword that drives Kindle Unlimited page reads but no direct sales? A: Exclude those targets from auto pause and set the rule to flag them instead. Check KENP reads in your KDP reports against the same dates. Judge them on combined page read value, not on orders alone.
Q: Should an IF/THEN rule pause a keyword, lower its bid, or move it to negative match first? A: Lower the bid first when the keyword has shown any promise, and pause when the evidence is clear. Use negative exact for search terms, not for targets you manage directly. Escalating in steps keeps mistakes reversible.
Q: What should I do if orders are attributed days after the click and the rule has already paused the keyword? A: Re-enable the keyword if the late orders change its profit picture. Then add a waiting period of several days after the window closes before the rule can act. Reviewing the paused list after a week catches these cases.
Q: How do I handle keywords with no orders when the book page itself has few reviews? A: Fewer reviews can suppress conversion across every keyword, so pausing may remove traffic that is fine. Raise the click threshold and compare against other keywords on the same book. If all targets underperform together, look at the page before blaming keywords.
Q: Can I apply the same pause rule to auto, broad, and exact match campaigns? A: It is better to use separate thresholds. Auto and broad campaigns produce looser traffic, so they can tolerate a rule with a lower click count and a negative step. Exact targets are deliberate choices, so give them a higher threshold and a bid cut before a pause.
Q: How often should I review keywords that a rule has paused? A: Review them weekly for the first month, then every two to four weeks. Look for late orders, seasonal shifts, and keywords you paused during a weak period. Restore any that now meet your profit target.
KDP Amazon Ads automation works when each rule has a clear threshold, a staged action, and a test against past data, which is the discipline behind kdp kdp ads automation done safely. Review the InteliAds pricing or See InteliAds plans, then Create an account to try rules with a dry run. Starter has no trial, and you approve live changes before they apply.
Browse more KDP ads guides on InteliAds.
See InteliAds plans: compare Essential, Pro, and Publisher (Essential has no trial; Pro and Publisher include a 7-day trial). InteliAds is a Sponsored Products manager for KDP authors: royalty-aware profit when KDP Sync is linked, user-written IF/THEN rules with dry run, and targeting filters for keywords, product targets, and search terms. Create an account.
Tools and guides: KDP ads automation with Rules and Dry Run · break-even ACOS calculator