My Ad Data Had the Answer for Months. I Never Looked.
I’ve been running Amazon book ads for a few months. Tweaking bids, checking dashboards, the usual. I asked my AI assistant to pull the actual search-term data and tell me what was going on underneath.
194 search terms over 30 days. The AI pulled them through the Amazon Ads API, ranked every term by impressions, clicks, and conversions, and found something I’d never have caught scrolling the dashboard.
One of my books teaches you how to fix structural problems in manuscripts. Pacing, second-act collapse, that kind of thing. Almost all its ad impressions were going to people searching “writer’s block.” Wrong audience entirely. Someone with writer’s block wants a pep talk, not a lesson on narrative structure. They saw the ad, ignored it, and tanked the click rate.
The terms that matched the book had great engagement but almost no impressions. Buried under the junk.
A second campaign had the opposite problem: barely any visibility, but the people who did see it clicked at six times the normal rate. Good book, right readers, starved of budget.
The fix: negative keywords to block the junk, a modest shift toward what was converting. Ten minutes of my time. The analysis was waiting when I sat down.
That data had been sitting in Amazon’s ad console for months. I was never going to pull 194 rows and cross-reference them myself.
OpenClaw is a self-hosted AI assistant that runs on your own server with access to your tools, files, and APIs. I teach two classes on setting up and getting the most from OpenClaw on Udemy: Easy OpenClaw and Get Real Work Done With an AI Assistant.
