Discover available DV360 targeting criteria with the Targeting Options API (v4)
domain: developers.google.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with OAuth2 using the display-video scope.
Confirm you're calling API v4 (displayvideo.googleapis.com/v4/...); v3 has been fully sunset and will fail.
Call GET targetingTypes/{targetingType}/targetingOptions with advertiserId and the targetingType enum (e.g. TARGETING_TYPE_APP_CATEGORY, GEO_REGION, VIDEO_PLAYER_SIZE) to list available options.
Use the filter param (EQUALS/OR only, capped at 500 characters) and pageSize/pageToken to narrow and paginate results.
Alternatively use the newer search method to look up targeting options by ID or keyword rather than listing the full set.
Assign a discovered option to a line item or insertion order via the separate assignedTargetingOptions resources — listing options does not itself apply targeting.
Known gotchas
Any integration still pointed at v3 URLs will break outright since v3 has fully sunset in favor of v4.
The filter syntax only supports EQUALS with OR combinators and a 500-character cap — complex AND logic across fields isn't supported this way.
This endpoint is discovery-only; assigning a returned targeting option ID to a line item requires a separate mutate call against assignedTargetingOptions.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?