Overview
The Display & Video 360 (DV360) SDF API allows programmatic access to DV360’s full trafficking structure, enabling bulk extraction of partners, advertisers, campaigns, insertion orders, line items, creatives, and assigned targeting configuration. The SDF Connector is designed for platforms that need accurate, up-to-date trafficking and configuration information for analytics, auditing, optimisation workflows, and data synchronisation.
SDF provides structural and targeting information rather than performance metrics, making it essential for verifying campaign setup, analysing programme structures, and integrating DV360 configuration into external systems.
SDF does not include impressions, clicks, conversions, or cost data - that comes from the DV360 Reporting API.
SDF exposes the master trafficking configuration across DV360, including:
Trafficking Structure
Partners
Advertisers
Campaigns
Insertion orders (IOs)
Line items
Ad groups (where relevant)
Creative assignments
Budget segments
Pacing and bidding configuration
Targeting Configuration
For each line item:
Demographic targeting
Geography
Device & OS
Browsers
App/URL lists
Audiences (first-party, third-party, Google audiences)
Brand safety & verification settings
Content categories & inventory types
Environment (web, app, CTV, video, audio)
Frequency caps
Creative Data
Creative metadata
File details
Rendering information
Approval & compliance status
Click-tags / tracking settings
Granularity:
Each SDF File corresponds to one specific DV360 entity which can be broken done by Partner, Advertiser, Campaign, Insertion Order, Line Item, Creative and Targeting Layer.
Purpose:
Synchronise DV360 trafficking structures with external systems
Audit campaign configuration including budgets, pacing, and targeting
Validate creative assignments and approval status
Support troubleshooting and QA on activation teams
Enable automated workflows (create/update consistency checks)
Map performance data back to the trafficking hierarchy (when combined with DV360 Reporting data)
Refresh Cadence:
Daily
Update Modes:
Refresh (for metadata only)
Connection Setup
Key | Description | Required | Type |
| List of advertiser IDs | ✅ | Text |
(secret, username) | Not used | ❌ |
|
This connector does not require user credentials beyond advertiser scope, and uses service-side authentication.
Jobs & Scheduling
Job Label | Feed | Look - back | First Run | Poll | Targets | Update Mode |
DV360 - SDF Import |
| 1 day | 06:00 UTC | 24h |
| Refresh |
Job Type: Lookup-only (no facts)
Mode: Daily full refresh
Lookback Window: 0 days (non-temporal)
Table Schema
dv360_sdf_youtubead
A direct reflection of YouTube-specific ad structures retrieved from the SDF API. Each row represents a YouTube Ad entity with full configuration and targeting detail.
Field Name | Description |
| YouTube ad name |
| Unique YouTube Ad ID |
| Associated Line Item ID |
| Associated Insertion Order ID |
| Associated Campaign ID |
| Associated Advertiser ID |
| Ad status (e.g. |
| Entity-level status |
| YouTube-hosted video ID used in the ad |
| Destination URLs |
| Linked companion banners (if any) |
| Whether the ad is skippable ( |
| Indicates bumper ad format |
| Length in seconds |
| Format type (e.g., in-stream, in-feed, bumper) |
| Bidding strategy (e.g., |
| Bid amount in micros (µ) |
| Whether ActiveView tracking is enabled |
| Whether conversion tracking is applied |
| List of inventory sources |
| Embedded targeting details (geo, devices, languages, etc.) |
| Bucketed video duration classification |
| Aspect ratio (e.g., 16:9, 4:3) |
| Placement strategy (e.g., pre-roll, mid-roll) |
| Structured audience segment settings |
| Channel tied to the ad (if owned) |
| How the video was uploaded (manual, linked, etc.) |
| Timestamps for data lifecycle |
⚠ Some fields may contain nested JSON or arrays depending on DV360’s internal modeling via SDF v5.5+.
Update Mode
Table is marked with
"update_mode": "refresh"meaning all records are reloaded once daily.No history is preserved — each run replaces the previous content.
Relationships & Joins
Although this connector does not explicitly join with fact tables, the youtubeAdId and associated foreign keys (advertiserId, campaignId, etc.) can be joined to other DV360 datasets (such as dv360_data_trueview) using manual model-level mapping.
Use Cases
Validate YouTube ad configurations within DV360 accounts
Extract targeting and format breakdown for ad ops QA
Build creative audit dashboards showing ad status, bidding, and structure
Pair with performance tables (
dv360_data_trueview) to evaluate performance vs. configuration

