.png)
Display & Video 360 Integration Guide
Connect Display & Video 360 with enterprise systems through its REST APIs, Structured Data Files, Bid Manager reporting workflows, and Google OAuth 2.0.
Display & Video 360 integration options at a glance
Display & Video 360 provides a Google REST API for managing Advertisers, Campaigns, Insertion Orders, Line Items, Creatives, targeting, and related resources. Structured Data Files support controlled bulk campaign configuration, while the Bid Manager API provides asynchronous reporting workflows. Google OAuth 2.0 secures API access, subject to both token scopes and Google Marketing Platform resource permissions. No general-purpose DV360 webhook mechanism was confirmed, so scheduled polling, report generation, SDF processing, and reconciliation are the safer synchronization approaches. Martini can authenticate securely, orchestrate these workflows, transform JSON and tabular data, apply validation and business rules, and load results into APIs, databases, files, or analytics platforms.
| Integration point | Supported by Display & Video 360? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Manage Advertisers, Campaigns, Insertion Orders, Line Items, Creatives, targeting, and related DV360 resources. APIs support resource retrieval and supported create or update operations. | Martini can consume the DV360 REST API from workflows, map JSON payloads, apply validation and business rules, and expose controlled internal APIs for downstream applications. |
| Bulk and asynchronous operations | Yes | Structured Data Files support bulk campaign configuration and management. Bid Manager uses asynchronous report-generation workflows. | Martini can validate files, coordinate dependent operations, poll asynchronous status, retrieve results, and persist operation state and audit information. |
| File and attachment exchange | Limited | Structured Data Files provide tabular exchange for supported campaign resources; they are not a general-purpose arbitrary attachment API. | Martini can retrieve or receive supported files, validate schemas, transform rows, retain audit copies, and coordinate import or update operations. |
| Reporting and analytics API | Yes | The Bid Manager API supports query management, asynchronous report generation, status polling, and report retrieval for performance data. | Martini can schedule report workflows, poll until completion, transform report rows, and load results into databases, warehouses, files, or analytics applications. |
| Webhooks and outbound callbacks | Not confirmed | No general-purpose DV360 webhook or outbound callback mechanism was confirmed for campaign, line-item, creative, or performance changes. | Martini can expose its own REST endpoint for other systems, but DV360 synchronization should use scheduled polling, SDF processes, or Bid Manager workflows instead. |
| GraphQL APIs | Not confirmed | No official Display & Video 360 GraphQL API was identified in the supplied research. | Martini can consume the confirmed REST interfaces; a GraphQL integration should not be assumed for DV360. |
| SOAP APIs | No | The current documented DV360 interface is REST-based and no current SOAP API was identified. | Martini should use REST API consumption rather than a SOAP integration for DV360. |
| Authentication | Yes | Google OAuth 2.0 access tokens authorize API requests, while partner and advertiser permissions control resource access. | Martini can store OAuth client credentials, refresh tokens, or permitted service-account credentials in environment-specific secrets and use them in API workflows. |
How Display & Video 360 exposes data and business events
Display & Video 360 REST APIs
The Display & Video 360 API is the primary interface for managing Advertisers, Campaigns, Insertion Orders, Line Items, Creatives, targeting, and related resources. It is resource-oriented and returns JSON through Google REST endpoints.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates with Google OAuth 2.0, retrieves or receives source data, calls the required DV360 endpoints, handles pagination and dependencies, maps responses to canonical models, and persists synchronization state and resource identifiers.
Implementation sequence
Structured Data Files
Structured Data Files provide tabular bulk campaign configuration and management for supported resource types such as Campaigns, Insertion Orders, Line Items, Creatives, and targeting. Availability and schemas vary by resource and API version.
Martini implementation pattern
Martini implementation pattern: a workflow receives or obtains a reviewed SDF, validates the file version and required columns, transforms approved source data, stores an audit copy, coordinates the supported Google file process, and records validation and import outcomes.
Implementation sequence
Bid Manager reporting
The Bid Manager API supports asynchronous reporting workflows distinct from transactional DV360 resource management. A query is created or managed, report generation is initiated or awaited, and completed report data is retrieved.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow creates or updates a query, polls report status with bounded retries, retrieves the completed file, transforms rows into the target analytics model, and loads or publishes the results.
Implementation sequence
Scheduled synchronization
No universal DV360 change feed or general-purpose webhook mechanism was confirmed. Scheduled polling, resource timestamps or hashes where available, SDF reconciliation, and report date windows are practical alternatives.
Martini implementation pattern
Martini implementation pattern: a scheduler partitions work by partner, Advertiser, resource, or date range, resumes from durable checkpoints, compares selected state, and runs reconciliation jobs to repair missed or inconsistent changes.
Implementation sequence
Common Display & Video 360 integration patterns
Pattern 1: Synchronize campaign and line-item metadata
When to use this pattern
Use this pattern when campaign metadata, budgets, flight dates, statuses, and buying-unit information must be available in a CRM, finance platform, campaign-management application, or data warehouse. Because no universal DV360 change feed was confirmed, scheduled polling and durable synchronization state are central to the design.
Integration direction
Example Mapping
| Display & Video 360 Field | Canonical Field | Target Field |
|---|---|---|
| advertiserId | advertiser_id | advertiser_id |
| campaign.name | campaign_name | campaign_name |
| insertionOrder.budget | planned_budget | planned_budget |
| lineItem.entityStatus | line_item_status | status |
Martini implementation pattern
A scheduled workflow authenticates, partitions Advertisers, retrieves Campaigns and dependent Insertion Orders and Line Items, follows page tokens, maps resources into a canonical model, and applies status and ownership rules. It stores resource identifiers, checkpoints, correlation data, and retry state so a failed partition can resume without repeating the entire portfolio.
Martini capabilities used
- workflows
- scheduling
- API consumption
- pagination handling
- data mapping
- business rules
- error handling
Pattern 2: Publish approved campaign configuration
When to use this pattern
Use this pattern when an internal application or approval process should control the creation or update of Campaigns, Insertion Orders, Line Items, and Creatives in DV360. It is appropriate when changes require validation, deterministic references, dependency ordering, and an auditable approval trail.
Integration direction
Example Mapping
| Display & Video 360 Field | Canonical Field | Target Field |
|---|---|---|
| request.campaignName | campaign_name | Campaign.displayName |
| request.budget | planned_budget | InsertionOrder.budget |
| request.flightStart | flight_start | InsertionOrder.flight.startDate |
| request.lineItems | buying_units | LineItem |
Martini implementation pattern
Martini exposes or consumes an approval interface, validates the request, checks parent references and required permissions, then calls DV360 in dependency order. A deterministic external reference and stored DV360 resource name prevent duplicate creation during retries. The workflow writes success or failure details back to the approval system and isolates invalid child operations.
Martini capabilities used
- API exposure
- workflows
- data validation
- data mapping
- business rules
- idempotency
- error handling
Pattern 3: Apply bulk campaign changes with Structured Data Files
When to use this pattern
Use this pattern when many related campaign resources must be reviewed and updated together, or when an organization requires file-based approval before changes are applied. It reduces the need for large numbers of individual resource mutations where the relevant SDF resource types are supported.
Integration direction
Example Mapping
| Display & Video 360 Field | Canonical Field | Target Field |
|---|---|---|
| Campaign Name | campaign_name | Campaign SDF campaign name |
| IO Budget | planned_budget | Insertion Order SDF budget |
| Line Item Status | line_item_status | Line Item SDF status |
| Creative Name | creative_name | Creative SDF name |
Martini implementation pattern
A workflow receives a reviewed file, validates the SDF version, advertiser, columns, data types, and parent-child relationships, then transforms approved rows and stores an immutable audit copy. Martini coordinates the supported bulk process, records validation and import results, and routes invalid rows or failed operations for review rather than silently applying partial changes.
Martini capabilities used
- workflows
- file processing
- data validation
- mapping and transformation
- audit persistence
- business rules
- error handling
Pattern 4: Extract and publish performance reports
When to use this pattern
Use this pattern when performance, cost, impression, conversion, or campaign data must be delivered to BigQuery, Snowflake, PostgreSQL, SQL Server, a file store, or an internal reporting API. It accounts for asynchronous Bid Manager report generation and late-arriving data.
Integration direction
Example Mapping
| Display & Video 360 Field | Canonical Field | Target Field |
|---|---|---|
| reportDate | report_date | report_date |
| campaignId | campaign_id | campaign_id |
| impressions | impressions | impressions |
| conversions | conversions | conversions |
Martini implementation pattern
A scheduler creates or manages a Bid Manager query for a defined date range, polls status with bounded retries, retrieves the completed report, preserves the original output, and transforms rows into a warehouse schema. A lookback window and stable reporting key allow late data to be merged or reconciled without duplicating prior results.
Martini capabilities used
- scheduling
- workflow orchestration
- API consumption
- asynchronous polling
- data mapping
- database connectivity
- retry handling
Applications commonly integrated with Display & Video 360
Display & Video 360 can be integrated with adjacent advertising, analytics, operational, and enterprise applications through shared reporting, approval, campaign-management, and data-governance workflows. The exact object-level relationship depends on the APIs and permissions available in each application.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Campaign Manager 360 | Coordinate campaign trafficking, creatives, Floodlight measurement, and reporting across Google Marketing Platform. | Campaign Manager 360 → Martini → Display & Video 360 | Use API-led workflows to retrieve or receive approved campaign and creative information, map identifiers and measurement metadata, validate dependencies, and synchronize supported resources while recording correlation IDs and failures. |
| Google Ads | Consolidate paid-media planning and performance data across Google advertising products. | Display & Video 360 → Martini → Google Ads | Use scheduled workflows to retrieve DV360 and Google Ads data through their respective APIs, normalize campaign and performance models, apply account-level rules, and load the result into a shared reporting or planning layer. |
| BigQuery | Centralize DV360 performance, cost, impression, conversion, and campaign data for analytics and modeling. | Display & Video 360 → Martini → BigQuery | Create or manage Bid Manager queries, poll asynchronous report status, retrieve completed reports, transform rows into an analytics schema, and load partitioned results with lookback-based reconciliation. |
| Google Sheets | Provide an operational review, approval, or campaign-input surface for nontechnical users. | Google Sheets → Martini → Display & Video 360 | Receive approved tabular configuration, validate required columns and parent-child dependencies, transform rows into SDF-compatible structures or DV360 API payloads, and retain an audit copy before applying changes. |
| Salesforce | Align advertising activity and conversion outcomes with accounts, leads, opportunities, or campaign members. | Salesforce → Martini → Display & Video 360 | Expose or consume APIs for approved campaign and conversion data, map identifiers into a canonical marketing model, apply consent and ownership rules, and synchronize selected data with retry and duplicate controls. |
| ServiceNow | Manage operational approvals, incidents, and change records for campaign launches, failures, and reporting exceptions. | ServiceNow → Martini → Display & Video 360 | Receive an approval or change request, validate it in a Martini workflow, publish approved campaign changes through the DV360 REST API, and write status, resource identifiers, and errors back to ServiceNow. |
| Snowflake | Consolidate advertising performance data with enterprise customer, sales, and finance data. | Display & Video 360 → Martini → Snowflake | Run scheduled Bid Manager extraction workflows, preserve original report files, normalize dimensions and measures, load staged data into Snowflake, and merge using stable reporting keys. |
| The Trade Desk | Compare media-buying performance or consolidate multi-platform advertising reporting. | Display & Video 360 → Martini → The Trade Desk | Retrieve data from both platforms through their available interfaces, normalize campaign, spend, impression, and conversion dimensions, and publish a cross-platform dataset without assuming a direct vendor-to-vendor API relationship. |
How to build a Display & Video 360 integration in Martini
Objective
Establish Google OAuth 2.0 access with the least privilege required for the relevant DV360 partner, Advertiser, or reporting workflow.
Instructions in Martini
- Configure the DV360 OAuth scope and permitted principal
- Store client credentials, refresh tokens, or permitted service-account credentials in environment-specific secrets
- Validate access to the intended partner and Advertiser resources
- Keep read-only and campaign-management credentials separated where practical
Objective
Select a trigger that reflects the confirmed DV360 integration mechanism rather than assuming webhook delivery.
Instructions in Martini
- Use a scheduler for polling, reconciliation, and Bid Manager reporting
- Use an internal Martini API for approved configuration requests
- Use a file-driven workflow for reviewed Structured Data Files
- Partition schedules by Advertiser, resource type, or reporting date range
Objective
Read DV360 resources or reports reliably while preserving progress and respecting API quotas.
Instructions in Martini
- Call the Display & Video 360 REST API or Bid Manager API
- Follow page tokens until the collection is complete
- Poll asynchronous report status with bounded retries
- Persist checkpoints, report identifiers, file identifiers, and resource scope
Objective
Coordinate parent-child resource dependencies, asynchronous operations, and controlled processing across the integration.
Instructions in Martini
- Process Campaigns before Insertion Orders and Line Items
- Validate parent identifiers before child mutations
- Use bounded concurrency and exponential backoff for transient failures
- Route invalid files, permission failures, and report failures to explicit error handling
Objective
Transform DV360 JSON or tabular report and SDF data into the canonical and target models.
Instructions in Martini
- Map Advertisers, Campaigns, Insertion Orders, Line Items, Creatives, and reporting fields
- Validate required fields, dates, identifiers, resource relationships, and file schemas
- Apply organization-specific naming, ownership, approval, and status rules
- Retain API and mapping versions with synchronization metadata
Objective
Persist normalized data or publish approved changes to DV360 and downstream systems without creating duplicates.
Instructions in Martini
- Create or update supported DV360 resources in dependency order
- Load reports into a database, warehouse, file, or internal API
- Store returned DV360 resource names and deterministic source references
- Merge reporting results using stable keys and a lookback window
Common Display & Video 360 data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Advertisers | Represent advertising accounts that own campaigns, insertion orders, line items, creatives, and targeting configuration. | Campaign Manager 360, Salesforce, BigQuery, Snowflake, internal campaign platforms | Martini retrieves Advertisers, validates partner and advertiser access, maps identifiers to a canonical account model, and stores synchronization state. |
| Campaigns | Group advertising activity under an Advertiser and provide campaign-level metadata and status. | Campaign Manager 360, Google Ads, Salesforce, data warehouses | Martini synchronizes Campaigns through paginated REST calls or approved bulk processes, applies ownership and status rules, and records returned resource identifiers. |
| Insertion Orders | Define budget, schedule, bidding, and optimization structures within a Campaign. | Finance platforms, campaign-management applications, BigQuery, Snowflake | Martini validates the parent Campaign, maps budgets and flight dates, sequences dependent writes, and retries transient failures without creating duplicates. |
| Line Items | Define granular buying units, including inventory, targeting, bidding, pacing, and creative associations. | Campaign-management applications, reporting warehouses, approval systems | Martini processes Line Items after validating their Insertion Order, transforms targeting and pacing data, and maintains deterministic source-to-DV360 keys. |
| Creatives | Represent advertising assets and serving configurations assigned to Line Items. | Campaign Manager 360, content repositories, campaign platforms, data warehouses | Martini validates creative dependencies, maps asset and serving metadata, coordinates create or update operations, and captures API responses and errors. |
| Floodlight activities | Define conversion and activity-tracking configurations used in Google Marketing Platform measurement workflows. | Campaign Manager 360, Salesforce, BigQuery, Snowflake | Martini can synchronize supported metadata and reporting-related mappings, enforce tenant and permission boundaries, and preserve versioned transformation rules. |
Authentication and security considerations
Google OAuth 2.0
Display & Video 360 API requests require Google OAuth 2.0 access tokens. The commonly used scope is the Display & Video 360 scope, while the authenticated principal must also have access to the relevant partner, Advertiser, campaign, insertion order, or line item resources.
Secrets and permissions
- Store OAuth client credentials, refresh tokens, and permitted service-account keys in Martini environment-specific secrets.
- Use least-privilege permissions and separate read-only synchronization from campaign-management workflows where practical.
- Treat token validity and DV360 resource authorization as separate checks.
- Do not log OAuth credentials or sensitive configuration.
Operational considerations for Display & Video 360 integrations
Quotas and pagination
Google API quotas and method limits require bounded concurrency, exponential backoff, and handling for transient 429 and 5xx responses. Collection workflows should follow page tokens and persist progress so failed partitions can resume.
Dependencies and idempotency
Insertion Orders belong to Campaigns, Line Items belong to Insertion Orders, and Creatives may need to exist before assignment. Validate parent identifiers and retain deterministic source references or DV360 resource names to prevent duplicates during retries.
Reporting and schema changes
Bid Manager reports are asynchronous and may contain late-arriving performance data. Use report identifiers, polling limits, lookback windows, and stable merge keys. Version SDF schemas, API mappings, and workflow configurations, and tolerate additive JSON fields where appropriate.
Monitoring and testing
- Log correlation IDs, Advertiser identifiers, resource names, request types, retry counts, and report or file identifiers.
- Test permissions, pagination, dependency ordering, quota behavior, invalid rows, asynchronous failures, and reconciliation.
- Keep partner and Advertiser data isolated in workflow configuration and persistence.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond point-to-point calls
Martini coordinates REST API calls, scheduled polling, asynchronous Bid Manager reporting, Structured Data File processing, database loads, and internal APIs in a single maintainable workflow.
Reusable transformation and rules
Instead of embedding mappings in scripts or duplicating logic across point-to-point integrations, Martini centralizes data transformation, validation, parent-child dependency checks, approval rules, and canonical models.
Operational reliability
Workflows can persist checkpoints, apply retries and backoff, handle pagination, prevent duplicates, preserve audit files, and separate transient failures from permission or validation errors.
Controlled APIs
Martini can expose an internal REST API for approved campaign changes or normalized performance data while keeping DV360 credentials, vendor-specific mappings, and resource permissions behind controlled integration workflows.
Frequently asked questions
Display & Video 360 can be integrated through its REST API for campaign and resource management, Structured Data Files for supported bulk operations, and the Bid Manager API for asynchronous reporting. Google OAuth 2.0 authorizes requests, while scheduled polling and reconciliation are practical alternatives because no general-purpose DV360 webhook mechanism was confirmed.
Yes. Martini can consume the Display & Video 360 REST API and Bid Manager API, orchestrate scheduled synchronization and asynchronous reporting workflows, process Structured Data Files, map and transform data, and load results into APIs, databases, files, and analytics platforms.
No. A dedicated Display & Video 360 connector is not required. Martini can integrate using DV360’s documented REST APIs, Google OAuth 2.0, Structured Data Files, and Bid Manager reporting mechanisms. A native Martini connector is not documented in the supplied sources.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Display & Video 360. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Google, cloud infrastructure, storage, advertising services, or other third-party systems.
Use the Display & Video 360 REST API for resource-level management, Structured Data Files for supported reviewed bulk changes, and the Bid Manager API for reporting and performance extraction. No current official GraphQL or SOAP interface was confirmed, and arbitrary file attachments should not be assumed.
No general-purpose DV360 webhook or outbound callback mechanism was confirmed for campaign, line-item, creative, or performance changes. Use scheduled API polling, SDF processes, resource-specific timestamps or hashes where available, and Bid Manager reporting workflows. Martini can expose its own API for other systems, but that does not mean DV360 sends webhook events.
Martini can schedule resource or report retrieval, follow pagination, map DV360 objects into a canonical model, apply business rules, and write to target systems. Since no universal change feed was confirmed, implementations should maintain checkpoints, use resource-specific comparison where available, retain full reconciliation capability, and use lookback windows for reporting data.
Martini workflows can distinguish authentication, permission, validation, quota, transient API, asynchronous report, and SDF errors. They can use bounded retries and exponential backoff for transient failures, store correlation and resource identifiers, validate parent-child dependencies, and use deterministic external references or idempotency controls to reduce duplicate Campaigns, Insertion Orders, Line Items, and Creatives.
Related Martini documentation
API Workflows
Data Processing
Security Operations
Connect Display & Video 360 with Martini
Use Martini to build governed Display & Video 360 integrations for campaign operations, bulk configuration, reporting, and enterprise data synchronization.