Ad platform
Integrate Amazon Ads
Amazon Ads is coming soon. The integration will connect over the Amazon Ads API, read-first, and follow the same draft-before-live model as Google Ads and Meta. This guide describes the planned Sponsored Products, Sponsored Brands, Sponsored Display, and ACOS-control surface.
Status: coming soon
Amazon Ads is not live yet. Google Ads and Meta are the two platforms you can connect today. This page documents the planned Amazon Ads integration so the read-first, draft-before-live model is clear before it ships.
When it lands, SpendSignoff will link through the Amazon Ads API, starting read-only. The operator will read Sponsored Products, Sponsored Brands, Sponsored Display, ASIN-level performance, ACOS, and search-term data, then draft changes you approve.
Planned read-and-draft surface
Amazon Ads is planned around retail-media work: margin, ACOS, search-term harvesting, and SKU-level budget decisions. The operator will draft via propose_change:
- Sponsored Products campaigns — status, budgets, bids, keywords, product targets, and ASIN performance.
- Sponsored Brands campaigns — budget, pacing, and campaign status.
- Sponsored Display campaigns — budget and pacing where the account uses display retargeting.
- Budgets and bids — daily budgets, keyword bids, product-target bids, and placement multipliers where supported.
- Search terms — converting terms for exact-match harvests and waste terms for negatives.
- Performance — spend, sales, ACOS, TACOS context where supplied, clicks, impressions, and conversion rate.
How a change will happen
Link the account read-only
Authorize SpendSignoff through the Amazon Ads API. The grant will be read-first, issued mcp.read and mcp.draft only.
The operator reads ACOS and search terms
It will pull Sponsored Products, Brands, Display, search terms, ASIN performance, and recent spend to find ACOS drift, wasted terms, and budget sitting on the wrong SKU.
It drafts a change
A proposed bid change, search-term harvest, negative keyword, placement adjustment, or ASIN budget shift will land as a draft with the before -> after diff. Nothing live.
You approve and push live
You will review the draft and run the two-step Approve & push live -> Confirm control before any write reaches Amazon Ads. The approved change is written to the audit report.
Write access stays dormant until you approve
mcp.approve scope issued to the AI.Audit report and governance
Amazon Ads support will write ACOS controls, bid changes, search-term harvests, negative keywords, placement edits, ASIN budget shifts, and approvals into the same client-ready audit report used across the other ad platforms. The report explains retail-media changes in client language: what changed, who approved it, when, and why it mattered to margin.
That gives Amazon the same governance posture as Google, Meta, Microsoft, LinkedIn, and TikTok. The operator can draft retail-media work quickly, but a human still approves every spend change before it reaches the account.
Not yet supported
Amazon Ads is not connectable today — there is no OAuth link for it yet. New campaign creation, retail catalog/feed setup, creative editing, inventory management, attribution setup, and Seller Central operations are out of scope for the planned V1 surface. Until Amazon Ads ships, connect Google Ads or Meta to put the operator to work now.
Next
Google Ads
Live today — connect Google Ads read-first while Amazon Ads is in progress.