Do I need an account with Google Ads (sample data)?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

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 Ads (sample data)

Advertising

Ready to useNo account needed

Google Ads (sample data) data, published as Google Ads (sample data) publishes it. Ingest delivers this data to a data warehouse you own as 3 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What you get

Table	Each row is
ad_groups `ad_groups`	Ad groups (and Performance Max asset groups) with the campaign each belongs to.
campaign_daily `campaign_daily`	One row per campaign per day: impressions, clicks, cost, conversions and conversion value, with CTR, average CPC and search impression share.
campaigns `campaigns`	Every campaign in the account: type (Search, Shopping, Performance Max, Video, Display), status, bidding strategy and daily budget.

How it works

Choose Google Ads (sample data). The data is public, so there is nothing to sign in to.
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

Do I need an account with Google Ads (sample data)?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Google Ads (sample data) 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 sample_google_ads, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://2k247ci8d7.execute-api.us-east-1.amazonaws.com/docs

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`ad_groups` Ad groups (and Performance Max asset groups) with the campaign each belongs to.	beta	full	merge	`ad_group_id`	-
`campaign_daily` One row per campaign per day: impressions, clicks, cost, conversions and conversion value, with CTR, average CPC and search impression share.	beta	full	merge	`report_date, campaign_id`	-
`campaigns` Every campaign in the account: type (Search, Shopping, Performance Max, Video, Display), status, bidding strategy and daily budget.	beta	full	merge	`campaign_id`	-

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 Ads (sample data) data into your warehouse

Last updated 2026-09-30.