Skip to main content

Google Ads Feeds

Google Ads is Google's online advertising platform, and the Google Ads API is its programmatic interface for managing accounts and retrieving campaign and performance data. The Google Ads Feeds connector is a source-only ELT connector that extracts Google Ads reporting data through the Google Ads API search endpoint. Select from 15 reporting objects — including customers, campaigns, ad groups, ads, criteria, audiences, budgets, keyword views, videos, account performance reports, bidding strategies, change status, and click views — and Nexla ingests each selected object as its own feed on a schedule.

Google Ads Feeds icon

Power end-to-end data operations for your Google Ads Feeds API with Nexla. Our bi-directional Google Ads Feeds connector is purpose-built for Google Ads Feeds, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Google Ads Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Google Ads Feeds workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

The Google Ads Feeds connector authenticates with OAuth 2.0. Nexla manages the OAuth application and the Google Ads API developer token, so you do not need to register your own Google Cloud project or apply for a developer token. You will sign in with a Google account and grant Nexla the Google Ads access scope (https://www.googleapis.com/auth/adwords).

Before creating a credential in Nexla, gather the following:

  1. A Google account with access to your Google Ads accounts. Use a Google account that can sign in to the Google Ads manager (MCC) account that manages the client accounts you want to extract data from. The OAuth consent flow grants Nexla the same Google Ads access as this account.

  2. Your Google Ads manager account customer ID. The Google Ads API requires the customer ID of the manager account making the call (sent as the login-customer-id header). To find it, sign in to Google Ads and look for the 10-digit customer ID displayed near your account name in the top corner of the interface. Google Ads displays customer IDs with hyphens (for example, 123-456-7890), but the API requires the ID without hyphens — enter 1234567890 in Nexla.

  3. The Google Ads API version you want to use. Nexla defaults to v21. Only change this if you need a specific Google Ads API version and know it is supported for your account.

For more information about Google Ads customer IDs, see Find your Google Ads customer ID in the Google Ads Help Center. For details about the API itself, see the Google Ads API documentation.

Authenticate​

Credentials required​

This connector uses Google's OAuth 2.0 consent flow. The following fields are entered in Nexla before authorizing with Google:

FieldRequiredSecretDescription
Ads Manager IDYesNoThe Google Ads customer ID of the manager making the API call. Be sure to remove any hyphens, so 1234567890 instead of 123-456-7890.
API VersionYesNoGoogle Ads API Version that your wish to use.

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter your Google Ads manager account customer ID in the Ads Manager ID field. Enter the 10-digit ID without hyphens (for example, 1234567890), as described in Prerequisites.

  4. Enter the Google Ads API version in the API Version field, or keep the default value (v21).

  5. Complete the Google OAuth authorization by signing in with the Google account that has access to your Google Ads manager account and approving the requested Google Ads access. Google returns a refresh token to Nexla, which Nexla uses to obtain access tokens for ongoing feed ingestion.

  6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with Google Ads Feeds flows.

Use as a data source​

How This Connector Works​

The Google Ads Feeds connector is a source-only, multi-feed ELT connector. Rather than configuring one endpoint at a time, you select the Google Ads reporting objects you want from a catalog of feeds, and Nexla ingests each selected object as its own feed.

  • Discovery: When you create the source, Nexla discovers the Google Ads objects (feeds) available through the Google Ads Discovery API and presents them for selection.

  • Ingestion: For each selected feed, Nexla queries the Google Ads API search endpoint for your manager account and paginates through all result pages automatically. Each feed uses a defined set of primary key fields (for example, the customer ID and segment date) to uniquely identify records.

  • Sync strategies: The connector supports an auto-increment strategy (the default), which fetches records for segment dates between the last successful run and the previous day, and a full ingest strategy, which reads the complete current set of records on every run. Which strategy applies depends on the feed — see the object list below.

  • Parallel ingestion: Selected feeds are ingested on the same schedule from a single source.

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

  2. Select the Google Ads Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to Google Ads and click Next; or, create a new Google Ads Feeds credential for use in this flow. The credential determines the manager account (login-customer-id) and API version used for all feeds in the source.

Select the Objects to Ingest​

After authenticating, Nexla lists the Google Ads objects available from the connector. Select one or more of the following 15 objects to ingest. Each selected object becomes its own feed.

The following objects use the auto-increment strategy by default, fetching records incrementally by segment date:

  • Customer — Customer (account) records and metrics.
  • Ad Group — Ad groups and their metrics.
  • Ad Group Ad — Ads within ad groups.
  • Campaign — Campaigns and their metrics.
  • Campaign Budget — Campaign budgets and their campaign associations.
  • Keyword View — Keyword-level performance data.
  • Video — Video ad performance data.
  • Account Performance Report — Account-level performance segmented by date, ad network type, and device.
  • Bidding Strategy — Portfolio bidding strategies and their metrics.

The following objects use the full ingest strategy, reading the complete current set of records on each run:

  • Ad Group Criterion — Targeting criteria attached to ad groups.
  • Audience — Audience definitions in the account.
  • Campaign Criterion — Targeting criteria attached to campaigns.
  • User Interest — The Google Ads user interest taxonomy.

The following objects use dedicated incremental behaviors:

  • Change Status — Recent changes to resources in the account, fetched incrementally by change date-time.
  • Click View — Click-level records, fetched for the previous day on each run.

The Google Ads Change Status API is limited to fetching at most 10,000 records from the last 3 months, so the Change Status feed can only look back within that window.

Configure Lookback Times​

Two source settings control how far back Nexla fetches historical data on the first run:

  • Lookback Time (Except Change Status) — The earliest segment date from which incremental feeds fetch historical data. This must be in YYYY-MM-dd format.

  • Change Status Lookback Time — The earliest date from which the Change Status feed fetches changes, in YYYY-MM-dd format. Because of the Google Ads Change Status API limit described above, this date must be within the last 3 months.

Schedule and Activate​

  • Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, auto-increment feeds fetch records from the last successful run through the previous day, and full-ingest feeds are fully refreshed.

Reference​

For details about the reporting objects, field definitions, and the query interface used by this connector, see the Google Ads API documentation and the Google Ads API reporting overview.