Programmatic

How to Bulk Edit DV360 Line Items: UI, SDF & API Guide

September 22, 2026

Bulk editing Display & Video 360 (DV360) line items is executed either directly through the DV360 user interface mass-action toolbar for simple parameter updates, or via Structured Data Files (SDF v6/v7) and the DV360 API for complex, large-scale targeting and bid adjustments. SDF bulk updates allow ad-ops teams to download CSV manifests, modify thousands of line item parameters—such as bid strategies, flight dates, budget allocations, and inventory assignments—and re-upload them to update campaigns instantly. Mastering these tools eliminates manual data entry, prevents operational errors, and ensures consistent campaign governance across enterprise accounts.

Key Takeaways

  • Native UI bulk editing handles up to 100 line items simultaneously for swift updates to status, fixed bids, frequency caps, and budget pacing.
  • Structured Data Files (SDF v7) process adjustments for thousands of line items across advertisers, requiring bid values formatted in micros ($1.00 CPM equals 1,000,000 micros).
  • SDF uploads evaluate line items independently, meaning valid rows successfully commit even if specific rows trigger formatting errors.
  • The DV360 REST API advertisers.lineItems.bulkUpdate endpoint enables custom programmatic scripts to automate dynamic bidding and flight management directly from external DSP management tools.

Native UI Bulk Editing: Operations and Boundaries

The DV360 native interface provides direct bulk edit capability for minor operational pivots across campaign line items. Within the Campaign or Insertion Order view, selecting check boxes alongside targeted line items reveals the primary Action menu. From this context menu, traders can perform synchronized changes across up to 100 line items at once.

Supported UI mass updates include toggling line item statuses between Active, Paused, or Draft, modifying start and end dates, updating flight budgets, adjusting fixed CPM bidding strategies, and appending or replacing frequency caps. Traders can also batch-assign targeting options such as inventory source groups, geography lists, and device types.

However, UI bulk editing has strict operational boundaries. Modifying granular parameters—such as swapping custom bidding script associations, reconfiguring complex deal lists, or updating multi-layered audience targeting across disparate line item types—is unsuited for UI mass editing. Additionally, when troubleshooting delivery issues like troubleshooting DV360 PMP deals not spending, adjusting inventory assignment across hundreds of individual lines via the UI introduces high risks of accidental targeting exclusion. For large-scale changes involving dynamic variations across distinct line items, Structured Data Files are required.

Structured Data Files (SDF): The Ad-Ops Standard for Mass Changes

Structured Data Files (SDF) represent Google's structured CSV format designed specifically for offline campaign management. SDF v7 supports comprehensive read-and-write operations across Advertisers, Campaigns, Insertion Orders, Line Items, Media Products, and Ad Groups. Executing line item edits via SDF follows a standard four-step workflow: export, modify, validate, and upload.

1. Exporting Targeted Line Items

To export SDFs, navigate to the DV360 Advertiser level and select SDF Management or use the inline export function within the Line Items view. Filter the export scope precisely by selecting the target Insertion Orders or Line Item IDs to keep file sizes manageable. Ensure you select the appropriate file type: Line Items contains core parameters (bids, pacing, status), while specialized targeting files (e.g., Line Item - Targeted Inventory, Line Item - Geography) contain specific targeting matrices.

2. SDF Structure and Critical Syntax Rules

A Line Item SDF contains exact column headers mapped to line item settings. Understanding key column definitions prevents syntax corruption during bulk manipulation:

  • Line Item Id: The unique system identifier generated by DV360. Leave this integer intact for updates. Changing or clearing this ID forces DV360 to attempt creating a brand-new line item upon re-upload.
  • Io Id: The parent Insertion Order ID. Must match an existing, accessible IO within the same advertiser entity.
  • Action: Defines the system execution path. Values must strictly be Update, No Change, or Delete. Leaving this as Update forces DV360 to process changes made to that specific row.
  • Status: Standardized text strings defining state: ENTITY_STATUS_ACTIVE, ENTITY_STATUS_PAUSED, or ENTITY_STATUS_ARCHIVED. Using plain text like "Active" or "Pause" will trigger an immediate upload error.
  • Bid Strategy Value: Monetary amounts in SDF must always be specified in micros (local currency multiplied by 1,000,000). A $2.50 base bid must be represented as 2500000. Entering floating-point decimals like 2.50 sets the bid to $0.0000025, completely collapsing bid participation.
  • Bid Strategy Type: Must map to valid enums such as BID_STRATEGY_TYPE_FIXED, BID_STRATEGY_TYPE_OPTIMIZED, or BID_STRATEGY_TYPE_CUSTOM_BIDDING.

When configuring custom bid modifiers or scaling campaign parameters for Connected TV inventory, combining SDF modifications with DV360 bid multipliers for CTV audience extension allows ad-ops teams to rapidly adjust multiplier tables across hundreds of active lines without breaking campaign structure.

3. Modifying and Saving the CSV

Open the exported CSV using a standard text editor or spreadsheet software like Microsoft Excel or Google Sheets. When using spreadsheet software, exercise extreme caution with automatic formatting features. Spreadsheet tools frequently strip leading zeros from IDs or convert long numeric strings (such as 19-digit Google entity IDs) into scientific notation (e.g., 1.23E+11). If saved in scientific notation, the file will fail parsing upon re-upload.

Always format entity ID columns explicitly as text or raw numbers without decimal precision before saving. Ensure the file preserves UTF-8 encoding and standard comma separation.

4. Uploading and Processing Validation

Return to the DV360 UI, select SDF Management > Upload, select file type Line Items, and upload the saved file. DV360 processes uploads in asynchronous background tasks. Smaller files (under 500 rows) complete within 30 seconds; larger bulk sheets spanning thousands of items can take several minutes.

Once processing finishes, DV360 displays a detailed upload status dashboard. If any row fails validation, the system generates a downloadable error log specifying the exact line number, column, and error reason (e.g., "Invalid Enum Value" or "Budget Amount Outside Bounds"). Valid rows within the same upload file commit successfully, preventing single-line errors from blocking an entire campaign deployment.

API-Driven Bulk Updates for Advanced Operations

For engineering-driven ad-ops teams managing custom operational dashboards or proprietary bid-management tools, the DV360 API v2 offers programmatic bulk modification via RESTful HTTP calls. The primary endpoint for bulk line item updates is:

PATCH https://displayvideo.googleapis.com/v2/advertisers/{advertiserId}/lineItems/{lineItemId}

To execute mass edits efficiently without triggering rate limits (HTTP 429), developers utilize the batch processing pattern using advertisers.lineItems.bulkUpdate. This allows up to 100 individual line item modifications to be sent within a single HTTP payload.

When applying structural updates via API, field masks (specified in the updateMask query parameter) must explicitly list every field being updated (e.g., updateMask=bidProperties,entityStatus). If a field is present in the JSON body but omitted from the updateMask, the API silently ignores the field change, leaving original values unchanged on the server.

Safety Protocols and Audit Control

Executing programmatic