Why does saving the pipeline fail with an error about dimensions and metrics?

Display & Video 360 does not publish a compatibility matrix for its report fields, so Renta checks your selection against the API itself when you save. The message you see is the answer from Display & Video 360, and it names the field that does not fit. Clear that field and save again.

Why are Date and Advertiser Currency already ticked and greyed out?

Both are required for Custom Report . Date is the column the destination table is partitioned by, and it makes incremental loading possible. Advertiser Currency is demanded by the API as soon as any cost or revenue metric is in the report.

Does the date range affect the entity report types?

No. Partners , Advertisers , Campaigns , Insertion Orders , Line Items and Creatives return the objects as they look at the moment of the run. Only Custom Report reads the date range.

Can one pipeline cover several advertisers?

Yes. **Advertisers** is a multi-select, and every advertiser you tick lands in the same table. Add the Advertiser ID dimension to Custom Report so the rows can be told apart.

The run failed because the report took too long. What should I change?

Display & Video 360 builds the report on its own side, and Renta waits up to an hour for it. Wide date ranges combined with many dimensions push a report past that. Shorten the date range or drop a few dimensions, and the report comes back faster.

Why does Google ask for permission to edit and delete my Display & Video 360 data?

Google offers one combined scope for entities and reports, without a read-only variant. Renta uses the write half of it for a single purpose: it creates a temporary reporting query, downloads the result, and deletes the query. Your campaigns, line items and creatives are only ever read.

Display & Video 360

Renta exports Display & Video 360 statistics to your data warehouse, together with the campaigns, insertion orders, line items, creatives, and other objects behind them.

You assemble the statistics report yourself from Bid Manager dimensions and metrics, so one row covers one combination of the dimensions you grouped by.

The object report types describe the account as it looks right now: identifiers, names, statuses, budgets, flight dates, and bid strategies.

Authentication

Renta uses OAuth to authenticate with Google. You will be redirected to Google to grant Renta access to your Display & Video 360 account.

Google offers a single combined permission for entities and reports, so the consent screen mentions editing and deleting. Renta writes nothing to your campaign structure. It creates a temporary reporting query, downloads the result, and deletes the query afterwards.

Your credentials are encrypted in transit and at rest, and never stored in Renta's application database. You stay in control and can revoke access from your Google account settings at any time.

Connect Display & Video 360 as a source

Go to the CatalogStep 1

In the Renta console, open Connections > Catalog in the left sidebar.
Open the Advertising category and click the Display & Video 360 card.

Display & Video 360 card in the Advertising category of the Renta connection catalog

Start the authorizationStep 2

Click Log in to your Display & Video 360 account. Renta hands you over to Google, where you pick the account that has access to the partners and advertisers you need.

Authorize connection page with the login button for Display & Video 360

Grant accessStep 3

Google lists the two permissions Renta asks for: your Display & Video 360 entities and reports, and your reports in DoubleClick Bid Manager. Click Allow to return to Renta.

Google consent screen listing the Display & Video 360 and Bid Manager permissions

Name the connection and saveStep 4

Finish the setup:

Source name.
A label for this connection, used only inside the Renta console.
Access granted.
The email of the Google account the authorization came from.

Click Save to finish.

If the authorization later stops working, for example after the Google password changed or the app was removed from the account, click Re-authorize on this connection. It refreshes in place and the pipelines built on it keep running.

Source name field and the granted Google account on the Display & Video 360 connection form

Verify the connectionStep 5

The connection appears in the Sources list with the Active status and is ready for pipelines.

Sources list with the new Display & Video 360 connection in the Active status

Create a pipeline

A pipeline links the Display & Video 360 connection to the destination that receives the data.

Create a Display & Video 360 pipeline

Select Display & Video 360 as the sourceStep 1

In the left sidebar, click New pipeline. Keep the ETL tab selected, find Display & Video 360 under Already connected, and click Next step.

Select a source step of the pipeline wizard with Display & Video 360 under Already connected

Select the connectionStep 2

Choose the Display & Video 360 connection you created and click Next step. The card shows the Google account behind it, which matters when several people connected different accounts.

Select your Display & Video 360 connection step with the authorized account on the card

Select a destinationStep 3

On the Destination step, pick the warehouse that receives the data and click Next step.

Select a destination step with the connected warehouses

Select the destination connectionStep 4

Choose the destination connection and click Next step.

Pipeline configuration

The last step of the wizard holds every setting in one scrolling form.

Partners

Partners scope the pipeline to a part of your Display & Video 360 account.

The list holds the partners your authorized Google account can reach, each with its numeric identifier below the name. Pick at least one for every report type except Partners, which covers the whole account on its own.

Advertisers

Advertisers decide whose campaigns, entities and statistics the pipeline loads.

Tick as many as you need. They all land in one table. The Partners and Advertisers report types ignore this setting, every other report type requires it.

Report type

The report type decides what the pipeline extracts.

Report type	Description
`Custom Report`	Performance statistics for the selected advertisers, grouped by the dimensions you choose. Built through Bid Manager, so it covers the same fields as a report you would build in the Display & Video 360 interface.
`Partners`	Partner accounts available to the authorized Google account, with time zone, currency, billing profile, ad server and data access settings, and the enabled exchanges.
`Advertisers`	Advertisers of the selected partners, with domain, time zone, currency, billing profile, and creative and serving configuration.
`Campaigns`	Campaigns of the selected advertisers, with goal type, performance goal, planned spend, flight dates, and frequency cap.
`Insertion Orders`	Insertion orders with their budget segments, pacing, KPI, partner costs, bid strategy, and flight dates.
`Line Items`	Line items with type, flight dates, budget allocation, pacing, frequency cap, partner revenue model, attached creatives, and bid strategy.
`Creatives`	Creatives with type, hosting source, dimensions in pixels, approval status, and the review results of each exchange.

Parameters

Tick the Display & Video 360 fields that become columns of the destination table.

For Custom Report the picker holds the whole Bid Manager reference: dimensions to group the report by, then metrics to aggregate. The list runs into hundreds of entries, so the search field is the fastest way to a field you already know by name. A report needs at least one metric.

Date and Advertiser Currency arrive pre-selected and cannot be cleared. Date is what the destination table is partitioned by. Advertiser Currency is required by the API for every report that carries a cost or revenue metric.

Display & Video 360 accepts only certain combinations of dimensions and metrics, and it publishes no matrix of what fits what. Renta sends your selection to the API when you save the pipeline. An unsupported combination comes back as the API's own message, which names the field at fault. Clear that field and save again.

Money metrics of the custom report arrive in the advertiser currency. Percentage metrics lose the percent sign on the way, so a click-through rate of 0.601% is stored as the number 0.601.

The entity report types keep the shape of the Display & Video 360 API. Money fields there come in micros, one millionth of the currency unit, so a daily pacing cap of 25 arrives as 25000000. Settings that the API returns as one of several possible objects, such as Bid Strategy and Integration Details, are stored as JSON, and repeating blocks such as Budget Segments and Partner Costs become arrays of records.

Integration and table name

Name the pipeline in Renta and the table in your destination.

Integration name and Table name fields in the pipeline settings

Integration name.
The display name of the pipeline in the Renta console.
Table name.
The table in your destination. Keep the generated name or type your own.

Date range

The date range sets the history the pipeline loads on its first run.

Date start.
The first day of statistics to load.
Date end.
The last one, either a fixed date or a moving boundary such as Today.

Only Custom Report reads these dates. The six entity report types describe the current state of your account, so they return the same objects whichever range you set.

Overwrite period

The overwrite period defines how far back each scheduled run reloads days it has already loaded.

Display & Video 360 keeps restating recent days while conversions get attributed and costs settle. The overwrite window is what carries those corrections into the table, so choose a window that covers your attribution lag. Without overwrite data loads only the days that appeared since the previous run.

Schedule

The schedule decides how often the pipeline runs. Renta reads the times you set here in UTC.

Schedule type	Description
Manual	The pipeline runs only when triggered from the Renta console or through the API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time (the exact time each run starts), then click Create pipeline.

Update time dropdown and the Create pipeline button

Renta also supports API triggers and orchestrators such as Apache Airflow, Dagster, and Prefect. See the scheduling documentation for details.

Saving the pipeline takes a few seconds longer than usual, because Renta uses that moment to check your field selection against Display & Video 360. Once it passes, the pipeline appears in the Pipelines section under the ETL tab, together with the destination table name, run progress, and the number of extracted rows.

Pipelines list with the new Display & Video 360 integration

Sync strategy

The table below describes how Renta synchronizes each Display & Video 360 report type.

Strategy	Supported report types	Description
Incremental	`Custom Report`	The destination table is partitioned by `Date`. Each run covers the days that appeared since the previous run plus the overwrite window, deletes those day partitions, and writes them again with the figures Display & Video 360 reports now.
Full reload	`Partners`, `Advertisers`, `Campaigns`, `Insertion Orders`, `Line Items`, `Creatives`	These report types carry the current attributes of objects and have no date column to partition by, so every run replaces the whole table with the state of the account at that moment.

A full reload keeps no history of its own. If you need to see how a line item budget or a creative status changed over time, snapshot the table in your warehouse after each run.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.