account | DynamicAccount | Yes | - | Select the DV360 advertiser that owns the insertion order. |
insertion_order_id | string or SelectItem | Yes | - | ID of the DV360 insertion order to update. Do not repeat it inside update_payload. |
update_payload | object or string | Yes | - | Insertion order fields to update as a JSON object using the official DV360 v4 camelCase field names, sent as-is with raw micros values. Only the fields named in the update mask are changed. Common editable fields: displayName, kpi, pacing (dailyMaxMicros raw), budget (budgetSegments with budgetAmountMicros raw), bidStrategy, optimizationObjective, frequencyCap, and entityStatus. Prefer the dedicated operations (dv360_update_insertion_order_status and dv360_update_insertion_order_budget) for simple changes. Example: {“pacing”: {“pacingPeriod”: “PACING_PERIOD_DAILY”, “pacingType”: “PACING_TYPE_EVEN”, “dailyMaxMicros”: “200000000”}} |
update_mask | string | No | - | Optional comma-separated DV360 update mask. When omitted, it is derived from the top-level keys of update_payload. Provide it explicitly for nested masks, for example campaignFlight.plannedDates or budget.budgetSegments. |
dry_run | boolean | No | False | When true, do not call DV360. Return the resolved update mask and payload for review. |