Authenticate with LWA OAuth 2.0 and specify your profileId (marketplace + advertiser combination) in the Amazon-Advertising-API-Scope header on every request.
Create a Sponsored Display campaign via POST /sd/campaigns with campaignType set to SD (Sponsored Display), tactic set to T00030 for audience targeting, and budget and bidding fields populated.
Create an ad group under the campaign via POST /sd/adGroups; set the default bid and assign it to the campaign.
Add audience targets via POST /sd/targets, specifying expressionType as auto or manual and the targeting expression — for audience targeting, use the AUDIENCE expression with a specific Amazon audience segment ID (e.g., in-market, lifestyle, or remarketing segments).
Create product ads linking the ad group to specific ASINs or auto-assign from the product catalog; Sponsored Display ads require at least one active product ad to serve.
Monitor performance via the Sponsored Display reporting endpoint; audience-targeted campaigns may have lower CTR than product-targeted ones but are intended for upper-funnel awareness and retargeting goals.
Known gotchas
Sponsored Display uses a different API path (/sd/) and a separate tactic system compared to Sponsored Products and Sponsored Brands; do not attempt to use Sponsored Products endpoints for SD campaigns as the schemas are incompatible.
Audience segment IDs for Amazon audiences (in-market, lifestyle) are not self-service discoverable via the open API; you must retrieve available audience IDs from the targeting recommendations endpoint or via your Amazon Ads account team.
The profileId (Amazon-Advertising-API-Scope header) is marketplace-specific and does not transfer across regions; campaigns in the US and EU require separate profileIds even for the same advertiser.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp