Update
DV360 brought to Google Ads parity — targeting, deals, audiences and reach forecasting
TL;DR
DV360 went from a read integration to something you can actually operate. The agent handles the campaign → insertion order → line item hierarchy, resolves targeting options by name, works with deals and first-party audiences, and runs native reach forecasts before a line item exists.
What shipped
- The full entity hierarchy — campaigns, insertion orders, line items — with the ENTITY_STATUS lifecycle handled correctly.
- Targeting coverage: keyword, device, geo and placement assigned-targeting-options, plus name-to-ID lookup so you can say "United States" instead of hunting for a numeric ID.
- Deals and first-party audiences made writable, reaching parity with the Google Ads surface.
- Native reach and frequency forecasting — plannable products plus forecast simulation, before any spend commits.
- Partner-hierarchy support and manual advertiser-ID connect for advertiser-scoped seats.
Frequently asked questions
- Can the agent create DV360 line items?
- Yes — campaigns, insertion orders and line items, with new entities created as drafts and every write pausing for approval.
- Does it support DV360 reach forecasting?
- Yes, natively — it lists plannable products and runs a reach-forecast simulation for a proposed budget and targeting combination, so the budget question is answered before anything is created.