PPC & Ads · from a Blog post, Aug 26, 2026 · Added
Weekly Amazon Ads and Organic Dashboard with Claude Code
Turn weekly Business Report and ads downloads into dashboards and an AI-written recap, and catch wrong numbers
While extending the dashboard he found that some of the numbers were wrong, and some of the reporting logic had already passed two live reporting cycles: Budget Amount was being summed as actual ad spend, a join created a phantom blank-date row that distorted spend, and a blend compared campaign names across platforms that don't share them.
Per source Reported by an agency about its own client work, not independently verified.
Copy-paste prompt
I'll give you this week's Business Report (by child ASIN) and Sponsored Products, Brands and Display reports. Clean them, check for duplicate rows and dates already in my sheet, and append one row per ASIN and per campaign for the week. Calculate sessions, CVR, units, sales, ad spend, ad sales, ACOS, ROAS, TACOS and organic sales (total minus ad sales). Use actual spend, never budget. Then write a 5-line recap and list any total that doesn't match the report totals.
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
Toshiki Gealone built a weekly reporting system for a real seller account he works with. He downloads the Business Report and Ads reports from Seller Central, runs two saved prompts in Claude Code, and it cleans the data, calculates the week, checks for duplicates, appends it to Google Sheets and writes a weekly recap. Looker Studio dashboards show sessions, sales, CVR, ASP, units, ad spend and sales, ACOS/ROAS, TACOS, organic vs ad-driven sales, SKU, campaign and placement performance, and Subscribe & Save subscriber trends. He left Buy Box % out because the brand is the only seller on its ASINs.
How it went
While extending the dashboard he found that some of the numbers were wrong, and some of the reporting logic had already passed two live reporting cycles: Budget Amount was being summed as actual ad spend, a join created a phantom blank-date row that distorted spend, and a blend compared campaign names across platforms that don't share them. He cross-checked every corrected figure against Amazon's Ads Console before finalizing.
We only report what the source says. Results are self-reported unless noted.
Worth knowing
Work for a client, with a video of the workflow and dashboards. His point: "nothing looked obviously broken. The totals were simply slightly wrong," so check AI-built reports against the Ads Console before you trust them.