Google Display & Video 360
Google Display & Video 360 is an integrated solution for end-to-end advertising campaigns.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ||
| History mode | ||
| Custom data | ||
| Data blocking | ||
| Column hashing | ||
| Re-sync | ||
| Row filtering | ||
| API configurable | API configuration | |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
Supported deployment models
We support the SaaS and Hybrid deployment models for the connector.
You must have an Enterprise or Business Critical plan to use the Hybrid Deployment model.
Setup guide
Follow our step-by-step Google Display & Video 360 setup guide to connect Google Display & Video 360 with your destination using Fivetran connectors.
Sync overview
The Google Display & Video 360 connector syncs your reporting data using the Google Display & Video 360 API and DoubleClick Bid Manager API.
On each sync, the connection creates a ONE_TIME Query in your Google Display & Video 360 account. Immediately after creation, the query starts to generate a report. The connection waits for the query to complete, and then downloads the resulting CSV report file using the link provided by the API. The created query is deleted upon completion or in case of any errors.
The connector allows you to configure a new report manually or to reuse the configuration of a query that already exists in your Google Display & Video 360 account. When reusing an existing configuration, you can choose whether the configuration will be updated when you save the connection settings or immediately before each sync. The latter option may be useful if you want the changes you make to your query in your Google Display & Video 360 account to be applied on the Fivetran side automatically.
All the reporting data is in the America/New_York timezone.
Advertiser and partner sync scope
You control which advertisers a connection syncs with the connection-level Advertisers sync mode setting. Choose one of the following modes:
- Sync all advertisers (default): Syncs every advertiser in your account and automatically picks up new advertisers as they are added.
- Sync specific partners: Syncs all advertisers that belong to the partners you select, including advertisers added to those partners later. New advertisers are added automatically with a free historical backfill.
- Sync specific advertisers: Syncs only the individual advertisers you select. Advertisers added later aren't synced until you add them to the list.
When a report uses the Reuse existing configuration method, its advertiser and partner scope comes from the reused query and isn't affected by the Advertisers sync mode setting.
Migration for existing connections
The Advertisers sync mode setting applies to all reports in the connection and replaces the per-report Partners and Advertisers selection. Fivetran migrates your existing per-report partner and advertiser selections to the connection-level Advertisers sync mode as follows:
- If any report syncs all advertisers, Fivetran sets the connection to Sync all advertisers.
- If your reports select only specific advertisers, Fivetran sets the connection to Sync specific advertisers.
- If your reports select specific partners (with or without specific advertisers), Fivetran sets the connection to Sync specific partners and syncs all advertisers under those partners.
Migration can broaden the set of advertisers your connection syncs:
- If your reports previously filtered by specific partners, the migrated connection uses Sync specific partners and syncs every advertiser under those partners—including advertisers that weren't included in your reports before.
- If your reports were scoped to different advertisers, migration combines those advertisers into a single connection-level list and applies it to every report. For example, if one report synced advertiser A and another synced advertiser B, both reports sync advertisers A and B after migration.
Review your Advertisers sync mode after migration to confirm the scope matches what you expect.
Reports that use the Reuse existing configuration method aren't affected by this migration.
Incremental sync
An incremental sync is a regular sync that starts according to the sync frequency that you chose in the Fivetran dashboard. Each incremental sync captures changes for the past three days.
Rollback sync
A rollback sync is a sync that automatically runs once a day. Rollback syncs capture the changes that happen outside the incremental sync time frame. The rollback window for our Google Display & Video 360 connector is 31 days.
Metadata sync
For metadata tables, we request and update all accessible data during each sync.
We support the following metadata:
- ad_group
- ad_group_ad
- ad_group_assigned_targeting_option
- assigned_first_party_and_partner_audience
- advertiser
- ad_url
- ad_url
- campaign_budget
- contact_info
- creative
- first_party_and_partner_audience
- hashed_email
- hashed_phone_number
- insertion_order
- insertion_order_budget_segment
- insertion_order_partner_cost
- channel
- custom_list
- combined_audience
- google_audience
- inventory_source_group
- line_item
- line_item_brand_lift_vendor_config
- line_item_brand_safety_vendor_config
- line_item_creative
- line_item_floodlight_activity_config
- line_item_partner_cost
- line_item_reach_vendor_config
- line_item_related_video
- line_item_video_ad_sequence_step
- line_item_viewability_vendor_config
- line_item_warning_message
- line_item_assigned_targeting_option
- line_item_assigned_combined_audience
- line_item_assigned_custom_list
- line_item_assigned_first_party_and_partner_audience
- line_item_assigned_google_audience
- inventory_source
- inventory_source_creative_config
- inventory_source_accessors_advertiser
- inventory_source_read_advertiser
- inventory_source_read_partner
- zip_code
- partner
Schema information
This schema applies to connections created after June 30, 2025.
See the Google Display & Video 360 ERD in table format | Google Display & Video 360 ERD as Markdown
Connections created before June 30, 2025 don't use a fixed report schema. These connections do not support multi-reporting.
UTC conversion
We don't convert source timestamps to Universal Time Coordinated (UTC) but use Eastern Standard Time (EST) to store the data in your destination.