Migrate a Display & Video 360 API integration's audience and targeting calls from v3 to v4

domain: developers.google.com/display-video/api · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Update client endpoint URLs and client library version to target the v4 Display & Video 360 API surface
  2. Replace all FirstAndThirdPartyAudience resource references with the new FirstPartyAndPartnerAudience resource, including its service methods, default page size, and field names
  3. Update assignedTargetingOptions calls that reference audience group details to the renamed v4 fields (e.g. excludedFirstAndThirdPartyAudienceGroup to excludedFirstPartyAndPartnerAudienceGroup)
  4. Rename calls to advertisers.adGroups.bulkListAdGroupAssignedTargetingOptions to the v4 name advertisers.adGroups.bulkListAssignedTargetingOptions
  5. Set optimizationObjective on insertion order creation, which is now a required field in v4

Known gotchas

Related routes

Build a first-party audience segment in DV360 using the Audience API
developers.google.com · 6 steps · unrated
Create a DV360 (Display and Video 360) insertion order and flight via the Display & Video 360 API
developers.google.com/display-video · 6 steps · unrated
Migrate an integration off Envoy's deprecated Visitors API v3 endpoints onto the current Protect API equivalents for flows, employees, and invites.
developers.envoy.com · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans