Amazon DSP's Geographic Insights and Activation (GIA) API Reaches General Availability — Postal-Code Targeting Simplified (May 4, 2026)
Amazon's Geographic Insights and Activation (GIA) API for Amazon DSP moved out of beta and into general availability on May 4, 2026. GIA lets DSP advertisers find regional growth opportunities by combining Amazon's retail insights with an advertiser's own geographic signals, so they can target customers in areas where their brand has low penetration. The GA release simplifies the workflow that complicated adoption during the beta: previously, creating a location index required a separate step to establish a version containing postal-code data, but location indexes now accept postal-code information inline at creation time. Smart locations attach to ad groups through the Campaign Management Targets API and apply postal-code-level bid adjustments automatically. This is a programmatic/API capability aimed at DSP advertisers and agencies, not a Seller Central feature.
Real-World Impact
The GA release consolidates GIA to five endpoints and lets advertisers supply postal-code data inline when creating a location index, eliminating the separate version-creation step the beta required.
Key Points
- On May 4, 2026, Amazon's Geographic Insights and Activation (GIA) API for Amazon DSP moved from open beta to general availability
- GIA combines Amazon's retail insights with an advertiser's own geographic data so DSP advertisers can discover and target regions where their brand has low penetration
- The GA release lets advertisers pass postal-code data inline when creating a location index, removing the separate version-creation step that complicated the beta workflow
- Several beta endpoints were deprecated, including the separate location-index version creation step and the create/update smartLocations calls
- Smart locations attach to ad groups via the Campaign Management Targets API and apply postal-code-level bid adjustments automatically
- This is a programmatic Amazon Ads API change for DSP advertisers and agencies, not a Seller Central dashboard feature
What You Should Do Now
- 1If you run Amazon DSP campaigns programmatically, review the GIA GA endpoints and migrate off the deprecated beta calls (the separate location-index version step and the create/update smartLocations endpoints)
- 2Use GIA to identify postal-code regions where your brand has low penetration and layer in your own geographic signals to find growth areas
- 3Attach smart locations to ad groups through the Campaign Management Targets API to apply postal-code-level bid adjustments automatically
- 4If you do not run DSP via the API, no action is needed — this change does not affect Seller Central or standard Sponsored Ads