Docs / Data sources / Google Search Ads 360

Google Search Ads 360

Business software

Built when you ask for it

Sync Google Search Ads 360 campaign, ad group, keyword, and report data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Google Search Ads 360 connector syncs your enterprise search-ads management data into analytics-ready tables in your data warehouse. Pull campaigns, ad groups, keywords, and reports from the Search Ads 360 Reporting API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Campaigns
  • Ad groups
  • Keywords
  • Reports

How it gets built

  1. Choose Google Search Ads 360 when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Google Search Ads 360's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Google Search Ads 360 itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

OAuth 2.0. Create a Google Cloud project, enable the Search Ads 360 Reporting API, and generate an OAuth 2.0 client ID; apps requesting broader access also need Google's OAuth app verification.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Google Search Ads 360 connector?
Not as a finished connector yet. Ingest builds it from Google Search Ads 360's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Google Search Ads 360 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.
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 Search Ads 360 API documentation: https://developers.google.com/search-ads/reporting

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.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Google Search Ads 360