🛠 Overview
The DV360 SDF connector retrieves YouTube-specific structural data from Google’s DV360 platform using the Structured Data Files (SDF) API. This includes YouTube ad entities for programmatic video campaigns and creative setups.
Granularity: YouTube Ad level
Purpose: Enrich campaign data with configuration and setup metadata for YouTube ads managed in DV360, such as settings not available via standard reporting.
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
✅ Summary
The DV360 SDF connector offers a granular lookup into YouTube ad entity configuration across DV360 advertisers via the dv360_sdf_youtubead table. Fully refreshed daily, it is ideal for creative validation, auditing, and configuration-driven insights. Although it does not include delivery metrics, it aligns with fact tables via shared keys for richer analysis.