The objects we sync from your DV360 account, the exact fields we read for each, and how they map into Medialake.
Medialake reads your DV360 structure (partners and their advertisers) to let you choose what to sync, and syncs the creatives and media assets behind your campaigns — all read-only, via Google's Display & Video 360 API (v4). We only read the fields listed on this page, nothing else. DV360 is a creative and asset integration: no performance metrics are captured.
Objects at a glance
DV360 object | What it is | Why we sync it |
The top level of DV360 — typically your agency or seat | Captures the hierarchy your advertisers and creatives sit within | |
A brand or business within a partner | Captures the hierarchy — the level you select for syncing | |
The visual content specification of an ad | Links each creative to its actual Medialake media file | |
An advertiser's ad-level media assets | Medialake ingests YouTube video assets as files — collecting the metadata and thumbnail |
Partners & Advertisers
The DV360 hierarchy runs Partner → Advertiser → Campaign → Insertion Order → Line Item. Medialake reads the top two levels live from the API so you can browse and select what to sync — they aren't stored as records themselves. We keep only your selections and, on each ingested file, the partner and advertiser IDs it belongs to.
Fields we read:partnerId / advertiserId and displayName — identifiers and names only.
Creatives
For each synced advertiser we read its creatives and the assets inside them, so every creative can be matched to the media behind it.
Fields we read: the creative's identifiers and metadata (creativeId, display name, type) and its asset list, which tells us where each piece of media lives.
Media assets
>Currently, only YouTube-hosted videos are ingested. DV360 video campaigns predominantly run on YouTube-hosted creative, which is what Medialake captures today — other asset types are not yet synced.
For each YouTube video found in your creatives and ad assets, Medialake creates a file carrying the relevant metadata (video ID, creative context, advertiser/partner) and the video's thumbnail.
How it maps into Medialake
Partner└─ Advertiser├─ Creative│ └─ File (YouTube video: metadata + thumbnail)└─ Ad Asset└─ File (YouTube video: metadata + thumbnail)
Everything on this page is read-only — see Authentication for the permissions behind it.
Further reading (Google documentation)
Questions about a specific field? Contact [email protected].