What does the Google Ad Manager data include?

4 tables: ad units (one row per ad unit), companies (one row per company), line items (one row per line item) and orders (one row per order).

Do I need an account with Google Ad Manager?

Yes. You connect your own Google Ad Manager account once, from Ingest, and the data comes from what that account can see.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.

Will running it again create duplicate rows?

No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Google Ad Manager

Advertising

Ready to use

The advertising setup behind a Google Ad Manager account: its ad units, companies, orders and line items. Ingest delivers this data to a data warehouse you own as 4 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What people use it for

See your ad inventoryList every ad unit to see how your inventory is organized.
Track advertisers and agenciesSee the companies tied to your account, from advertisers to agencies.
Watch orders and line items togetherFollow orders and their line items to see what is running.

What you get

Table	Each row is
Ad units `ad_units`	One ad unit
Companies `companies`	One company
Line items `line_items`	One line item
Orders `orders`	One order

Good to know

Ad units: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.
Companies: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.
Line items: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.
Orders: Each run re-reads everything and updates rows that changed. Rows the source removes stay in your table.

How it works

Choose Google Ad Manager. Connect your Google Ad Manager account once, from Ingest.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

What does the Google Ad Manager data include?: 4 tables: ad units (one row per ad unit), companies (one row per company), line items (one row per line item) and orders (one row per order).
Do I need an account with Google Ad Manager?: Yes. You connect your own Google Ad Manager account once, from Ingest, and the data comes from what that account can see.
Which warehouses can Google Ad Manager data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?: No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector google_ad_manager, version 0.1.0, a REST source, status beta, authentication oauth2.

Vendor documentation: https://developers.google.com/ad-manager/api/beta/getting-started

Configuration

Key	Label	Type	Required
`network_code`	Ad Manager network code	string	yes

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`ad_units` Ad units in the network (the inventory hierarchy). A full snapshot metadata collection with merge: every run re-fetches the network's ad units and upserts them on `name`. It is not a delivery report, and deletions do not propagate: an ad unit removed in Ad Manager stops appearing in later snapshots, and the destination keeps the last row. Paging follows pageToken; the terminal page is an empty object, which closes the collection.	beta	full	merge	`name`	-
`companies` Companies in the network (advertisers, agencies and publishers). A full snapshot metadata collection with merge: every run re-fetches the network's companies and upserts them on `name`. It is not a delivery report, and deletions do not propagate: a company removed in Ad Manager stops appearing in later snapshots, and the destination keeps the last row. Paging follows pageToken; the terminal page is an empty object, which closes the collection.	beta	full	merge	`name`	-
`line_items` Line items in the network. A full snapshot metadata collection with merge: every run re-fetches the network's line items and upserts them on `name`. It is not a delivery report, and deletions do not propagate: a line item removed in Ad Manager stops appearing in later snapshots, and the destination keeps the last row. Paging follows pageToken; the terminal page is an empty object, which closes the collection.	beta	full	merge	`name`	-
`orders` Orders in the network. A full snapshot metadata collection with merge: every run re-fetches the network's orders and upserts them on `name`. It is not a delivery report, and deletions do not propagate: an order removed in Ad Manager stops appearing in later snapshots, and the destination keeps the last row. Paging follows pageToken; the terminal page is an empty object, which closes the collection.	beta	full	merge	`name`	-

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Get Google Ad Manager data into your warehouse

Last updated 2026-10-05.