PPC Search Term Review: Explain the Review Queue
A deterministic review aid for search-term rows. Set your own economic boundaries and confirm the reporting window. A flag is a reason to inspect a term, not a command to add a negative keyword.
Inputs stay in this tab. No fetch, account connection, telemetry or persistent storage is used. Start with the fictional example; avoid customer data. Reload to clear the tab. Downloads happen only when you choose Export.
1. Understand the rules and limits
Required headers: term, spend, sales, clicks, orders, protected. Use decimal numbers in one currency, whole clicks/orders, and yes/no for protected. Do not mix attribution windows, products with different margins, currencies or campaign purposes. The example uses spend limit 25, minimum clicks 15 and target ACoS 30%. These are fictional teaching inputs, not Amazon defaults or recommended universal thresholds.
Download the synthetic example CSV3. Compare the expected example result
With mature window checked and default controls: one protected, one review zero sales, one review efficiency, one within target, one insufficient data and one invalid. The 45 spend / 90 sales row has 50% ACoS. With maturity unchecked, nonprotected valid rows remain insufficient data.
Inspect the exact fictional inputs
term,spend,sales,clicks,orders,protected brandname,40,0,20,0,yes relevant no sales,36,0,18,0,no high acos,45,90,30,3,no good term,15,100,25,5,no sparse,12,0,5,0,no credit,-3,0,10,0,no
The same functions are used by the published tool and automated regression tests. You can inspect the calculation source. No result is represented as a customer outcome.
4. Decide what to do next
Check query intent, attribution delay, stock, listing quality, target match type, product margin and campaign purpose. Protected status prevents this tool from proposing a negative action; it does not mean spending must continue unchanged. Document a human decision and observe it over a comparable window.