Skip to main content

DV360 SDF (Structured Data File) Connector Documentation

Updated this week
DV360-logo - Thunder Experience Cloud

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

dv360_advertisers

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

dv360_sdf

1 day

06:00 UTC

24h

dv360_sdf_youtubead

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

displayName

YouTube ad name

youtubeAdId

Unique YouTube Ad ID

lineItemId

Associated Line Item ID

insertionOrderId

Associated Insertion Order ID

campaignId

Associated Campaign ID

advertiserId

Associated Advertiser ID

status

Ad status (e.g. ACTIVE, PAUSED)

entityStatus

Entity-level status

videoId

YouTube-hosted video ID used in the ad

finalUrls

Destination URLs

companionBannerIds

Linked companion banners (if any)

skippable

Whether the ad is skippable (TRUE/FALSE)

bumper

Indicates bumper ad format

adLength

Length in seconds

adFormat

Format type (e.g., in-stream, in-feed, bumper)

bidStrategyType

Bidding strategy (e.g., CPV, CPC)

bidAmountMicros

Bid amount in micros (µ)

activeViewEnabled

Whether ActiveView tracking is enabled

conversionTrackingEnabled

Whether conversion tracking is applied

inventorySourceIds

List of inventory sources

targeting.*

Embedded targeting details (geo, devices, languages, etc.)

videoLengthBucket

Bucketed video duration classification

videoAspectRatio

Aspect ratio (e.g., 16:9, 4:3)

videoPositioning

Placement strategy (e.g., pre-roll, mid-roll)

audienceTargeting

Structured audience segment settings

youtubeChannelId

Channel tied to the ad (if owned)

creativeSource

How the video was uploaded (manual, linked, etc.)

createdTime, lastModifiedTime

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

Did this answer your question?