PPC & Ads · from a Blog post, The case study page shows no date. · Added
Adjacent Auto Terms with Claude and Intentwise
Catch budget leaking into adjacent-category search terms in auto campaigns
Scott Kennedy, VP Digital Strategy & Analytics, says: 'You go from I learned something to I did something about it very fast.'
Per source From the tool's vendor, not independently tested.
Copy-paste prompt
Using my connected Amazon ads data, list search terms in auto campaigns from the last 30 days that belong to an adjacent category rather than our core category. For each, show spend, sales, ROAS and share of that campaign's spend. Flag terms where spend share is high and ROAS is below [target], and draft a short note to our product manager summarizing the ones worth keeping vs pausing. Don't change anything.
The source didn't publish its exact prompt. We wrote this starter so you can try the same workflow. Replace anything in [brackets].
What they did
Franklin Sports, a sports-equipment brand, used to hunt performance anomalies by digging through Excel files and bouncing between teams. With Intentwise's AI Gateway MCP feeding trusted Amazon (and other channel) data into Claude, entry-level analysts ask deep product-performance questions and bring findings to the rest of the team. Claude isolates search terms from an adjacent category that slipped into auto campaigns, shows what share of budget they take and what ROAS they return, and can draft an email to a product manager or turn off an external campaign.
How it went
Scott Kennedy, VP Digital Strategy & Analytics, says: 'You go from I learned something to I did something about it very fast.' Intentwise reports five employees upskilled as MCP users. No ACoS or dollar figures are given.
We only report what the source says. Results are self-reported unless noted.
Worth knowing
A vendor case study with no date on the page. The useful idea is measuring adjacent-category auto terms as a share of budget and ROAS before cutting them.