Amazon Marketing Mix Modeling (MMM) API Exits Beta — Goes Generally Available Across 14 Markets (May 3, 2026)
On May 3, 2026, Amazon Ads' Marketing Mix Modeling (MMM) API moved from beta to general availability, opening programmatic access to Amazon's MMM data feed to all advertisers and their measurement partners — no invitation required. The API uniquely combines advertising signals with retail signals from Amazon's marketplace, so brands modeling media performance can now ingest both ad metrics and actual sales data through one feed. GA coverage spans 14 markets across four continents: the United States, Canada, Italy, Spain, France, Germany, the United Kingdom, Mexico, Brazil, Japan, Australia, the United Arab Emirates, India, and Saudi Arabia. The release adds six new endpoints around brand group override management, product and campaign retrieval within brand groups, and report status listing, and the API operates asynchronously so report requests are processed in the background and replicate console-generated reports without manual download steps. API calls must be routed through the NA region endpoint, but a single API relationship can request data across any of the 14 supported marketplaces.
Real-World Impact
Before GA, MMM data was beta-gated and pulled per-market through the console. Under GA, a brand selling across all 14 supported marketplaces can request MMM reports programmatically through one API relationship rather than running 14 separate console export workflows per reporting cycle.
Key Points
- Announced May 3, 2026: Amazon's Marketing Mix Modeling (MMM) API moves from beta to general availability — no more invitation gating or beta breaking-change risk
- Unique data scope: combines advertising signals with retail signals from Amazon's marketplace, so brands get both media performance metrics and actual sales data through one feed
- GA coverage: 14 markets across four continents — United States, Canada, Italy, Spain, France, Germany, United Kingdom, Mexico, Brazil, Japan, Australia, United Arab Emirates, India, and Saudi Arabia
- Six new endpoints added: brand group override management (create, delete, list), product and campaign retrieval within specific brand groups, and report status listing for tracking generation progress
- Asynchronous design — advertisers submit report requests that are processed in the background; output replicates console-generated reports in programmatic format, eliminating manual download steps
- API calls must be routed through the NA region endpoint, though a single API relationship can request data across any of the 14 supported marketplaces
What You Should Do Now
- 1If you run an in-house or vendor-built MMM, ask your measurement team or partner whether they are migrating their Amazon ingestion from console exports to the GA MMM API — beta breaking-change risk is no longer a blocker
- 2If you operate the API directly, confirm your client routes calls through the NA region endpoint and update any region-routing logic that assumed multi-region access
- 3Audit which of the 14 supported marketplaces your brand actually advertises in (US, CA, IT, ES, FR, DE, UK, MX, BR, JP, AU, AE, IN, SA) and consolidate market-level MMM reporting under one programmatic pipeline rather than market-by-market exports
- 4Use the new brand group override endpoints to align MMM brand groupings with your internal product hierarchy before kicking off long-running modeling cycles