Here is the dirty secret of managing Amazon PPC at scale. 90% of Amazon brands a

By Michael Erickson Facchin · June 4, 2026 · Curated by George's Blog

Here is the dirty secret of managing Amazon PPC at scale.

90% of Amazon brands are hemorrhaging ad spend right now on keywords they think they’ve already blocked.

You pull your Search Term Report (STR), you find a bleeding, irrelevant "close variant" generated by Amazon's algorithm, and you think, "Wait, didn't I already negate this last week?"

So you stop what you're doing. You open a second tab. You manually check your campaign-level negative lists. Then you check your ad group-level lists.

By the time you find out whether it’s blocked or not, you’ve wasted 15 minutes of your life on manual admin work. Multiply that by 50 campaigns, and your media buyers are spending half their week playing detective instead of driving strategy.

We got sick of this friction. So we built the solution directly into our software.

We just rolled out a major update to our All Search Terms infrastructure to give you instant, zero-click visibility over your negative targeting.

Here is what is live in your dashboard right now:

• No more manual double-checking. You can now see directly within your search terms table exactly if a query is already being blocked and whether that negative match lives at the Source Ad Group or Source Campaign level.

• Want to find the real bleeders? Filter your view to instantly isolate search terms that are 𝑛𝑜𝑡 currently blocked. In less than 3 clicks, you can spot every single unnegated algorithm-expanded term eating your margins and negate them in bulk.

Between Amazon forcing AI-driven "semantic matching" into your Exact Match campaigns and the need to scale external traffic flawlessly, you cannot afford to waste time on manual data hunting.

If you are already a user, log in and check the new columns in your All Search Terms view today.

If you're still manually cross-referencing your negative lists... how many hours a week are you losing to Amazon's interface?

View the original post on LinkedIn

More from Michael Erickson Facchin