Advanced Analytica Advanced Analytica: IBOM
← All connectors
Google Ads logo

Source connector

Google Ads

Set up Google Ads as a source and move its data into your chosen destination.

Version 6.1.11 certified generally available

Google Ads

Use this page to set up and reference the Google Ads source connector.

Prerequisites

  • For Airbyte Open Source:
    • Google Ads API access (Basic or Standard) for the Google Cloud project that owns your OAuth client (see Step 1)
    • OAuth credentials to authenticate your Google account

Setup

Set up Google Ads

Step 1: Get Google Ads API access for Airbyte Open Source

Google Ads API access belongs to the Google Cloud project that owns your OAuth client, not a developer token. Google sunset developer tokens on September 9, 2026. Existing tokens still work and remain valid Airbyte entries. However, Google ignores them and no longer issues new tokens through the Google Ads manager account API Center. See Google’s developer token sunset guide.

  1. Create or choose the Google Cloud project that will own the OAuth client you use in Step 2.
  2. Open the project’s Google Ads API Overview page in the Google Cloud Console and apply for API access. New Basic and Standard access applications require project brand verification. Basic access receives automatic approval within minutes after verification.
  3. Confirm that the project shows at least Basic access. Projects with only Test access can’t read production Google Ads accounts. They fail with ACTION_NOT_PERMITTED, or CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION on newer API versions.

:::note Google transferred approved developer-token access to every Google Cloud project that used the token before September 9, 2026. This transfer covered the preceding 90 days. If your OAuth client’s project didn’t inherit access, apply through that project’s Google Ads API Overview page. Airbyte still requires a value in the Developer Token field. Enter your existing token or any non-empty placeholder, such as placeholder, if you never had one. Google rejects an empty value with DEVELOPER_TOKEN_PARAMETER_MISSING. :::

Step 2: Get OAuth credentials for Airbyte Open Source

For Airbyte Open Source, get these OAuth credentials to authenticate your Google Ads account:

  • Client ID
  • Client Secret
  • Refresh Token

Follow Google’s documentation for detailed instructions on getting these credentials.

One access token can provide different access levels across multiple APIs. A variable parameter called scope controls which resources and operations the token permits. Your app sends one or more values in the scope parameter when requesting the access token.

Use this scope for the Google Ads API: https://www.googleapis.com/auth/adwords

Each Google Cloud project’s OAuth client has an access level and “permissible use”. The access level controls production-account access and the daily number of permitted operations and requests. Permissible use controls which Google Ads API features the project can use. Read Google’s access levels documentation for details and to apply for higher access.

Step 3: Set up the connector in Airbyte

Airbyte Cloud

  1. Log into your Airbyte Cloud account.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Google Ads from the Source type dropdown.
  4. Enter a name for the Google Ads connector.
  5. Click Sign in with Google to authenticate your Google Ads account. In the pop-up, select the appropriate Google account. Click Continue to continue.
Optional: Use your Google OAuth app

Airbyte Cloud normally uses Airbyte-managed OAuth client credentials for the Google Ads source. To use your own Google OAuth app, create OAuth override credentials.

Create the override first, then click Sign in with Google.

Use the Airbyte API to create OAuth override credentials for the workspace or organization. For the workspace endpoint, see Create OAuth override credentials for a workspace and source type. For the organization endpoint, see Create OAuth override credentials for an organization and source type.

For Google Ads, set actorType to source and name to google-ads. Include your Google OAuth app credentials and Google Ads developer token in configuration.credentials.

Google has ignored the developer_token value since September 9, 2026. See the developer token sunset guide. The connector still requires this field. Pass your existing token or any non-empty placeholder because Google rejects an empty string. API access belongs to the Google Cloud project that owns your OAuth app. Confirm that the project has at least Basic access on its Google Ads API Overview page.

{
  "actorType": "source",
  "name": "google-ads",
  "configuration": {
    "credentials": {
      "client_id": "<your-google-oauth-client-id>",
      "client_secret": "<your-google-oauth-client-secret>",
      "developer_token": "<your-google-ads-developer-token>"
    }
  }
}

After creating the override, click Sign in with Google and authorise the source. The authorisation server must issue the refresh token for the Google OAuth app credentials Airbyte uses to refresh it. If you change those credentials, authorise the source again.

6. (Optional) Enter a comma-separated list of your account's **Customer ID(s)**. These 10-digit numbers uniquely identify your account. Follow [Google's instructions](https://support.google.com/google-ads/answer/1704344) to find your Customer ID. Leave this field blank to replicate data from all connected accounts.

:::note If you access your account through a Google Ads Manager account, enter the Manager account’s Customer ID. :::

7. (Optional) Enter customer statuses to filter customers. Leave this field blank to replicate data from all accounts. See [Google Ads documentation](https://developers.google.com/google-ads/api/reference/rpc/v23/CustomerStatusEnum.CustomerStatus) for details. 8. (Optional) Enter a **Start Date** using the datepicker or programmatically in YYYY-MM-DD format. The connector replicates data added on or after this date. The default start date is two years ago.
  1. (Optional) Use the Custom GAQL Queries field to enter a custom Google Ads Query Language query. Click Add and enter your query. Also enter the destination table’s preferred name. You can provide multiple queries. See our guide below for guidance on writing them.
10. (Optional) Enter a **Conversion Window**. This value sets how many days after an ad interaction Google Ads records a conversion. See the [Google Ads Help Center](https://support.google.com/google-ads/answer/3123169?hl=en) for details. This field defaults to 14 days. 11. (Optional) Enter an **End Date** in YYYY-MM-DD format. The connector won't replicate data added after this date. Leave this field blank to replicate all data from the start date onwards.
  1. Click Set up source and wait for the tests to finish.

Airbyte Open Source

  1. Open the Airbyte Open Source dashboard.
  2. In the left navigation bar, click Sources. In the top-right corner, click + New source.
  3. Find and select Google Ads from the available sources.
  4. Enter your preferred Source name.
  5. Enter a Developer Token. Google has ignored this value since September 9, 2026. Use your existing token or any non-empty placeholder.
  6. Enter your Google application’s Client ID, Client Secret and Refresh Token to authenticate your Google account. You can also enter the optional Access Token.
  7. (Optional) Enter a comma-separated list of your account’s Customer ID(s). These 10-digit numbers uniquely identify your account. Follow Google’s instructions to find your Customer ID. Leave this field blank to replicate data from all connected accounts.
  8. (Optional) Enter customer statuses to filter customers. Leave this field blank to replicate data from all accounts. See Google Ads documentation for details.
  9. (Optional) Enter a Start Date using the datepicker or programmatically in YYYY-MM-DD format. The connector replicates data added on or after this date. The default start date is two years ago.
  10. (Optional) Use the Custom GAQL Queries field to enter a custom Google Ads Query Language query. Click Add and enter your query. Also enter the destination table’s preferred name. You can provide multiple queries. See our guide below for guidance on writing them.
  11. (Required for Manager accounts) When accessing your account through a Google Ads Manager account, enter the Manager account’s Customer ID.
  12. (Optional) Enter a Conversion Window. This value sets how many days after an ad interaction Google Ads records a conversion. See Conversion Windows below or the Google Ads Help Center for details. This field defaults to 14 days.
  13. (Optional) Enter an End Date in YYYY-MM-DD format. The connector won’t replicate data added after this date. Leave this field blank to replicate all data from the start date onwards.
  14. Click Set up source and wait for the tests to finish.

Supported sync modes

The Google Ads source connector supports these sync modes:

Incremental Events Streams:

Streams:

These streams support incremental updates and deletions through the Change Status stream. However, they capture updates from only the latest three months.

The initial sync runs as a full refresh. Later syncs first read updates from the Change Status stream. They then sync records by ID.

:::warning The Google Ads API resource ChangeStatus allows up to 10,000 records per request. You can’t sync a stream with more than 10,000 updates in one microsecond. In this case, use a full refresh sync to capture every update. :::

Supported streams

The Google Ads source connector can sync the following tables and custom GAQL queries.

Main tables

Shows a Google Ads account’s setup and configuration. It covers features such as call reporting and conversion tracking. Together, these provide a clear view of the account’s operational settings and features.

A campaign targeting option, such as a keyword, placement or audience.

Represents the campaign-level bidding strategy.

Represents labels attached to entities such as campaigns or ads.

Shows date-segmented ad attributes from ad groups.

Provides an ad-level performance report built on the ad_group_ad resource. It includes ad identity dimensions and performance metrics. These metrics cover clicks, impressions, cost, conversions, video and active-view metrics. Data is segmented by date, ad network and device. This report is available only for non-manager accounts.

Represents an ad group within a campaign. Ad groups contain one or more ads targeting a shared keyword set.

Represents the ad-group-level bidding strategy.

Represents criteria in an ad group, such as keywords or placements.

Represents criteria for listing group ads.

Represents advertiser-defined user lists for targeting specific users.

Represents a specific interest-based vertical for targeting.

Provides a click view with metrics aggregated at each click level, including valid and invalid clicks.

The ad_group, ad_group_ad and campaign streams contain a labels field. Join this field to each stream’s corresponding *_label stream to view the labels. For example, join the ad_group stream’s ad_group.labels field to the ad_group_label stream’s label.resource_name field.

Report tables

Provides detailed ad-interaction metrics, including viewability, click-through rates and conversions. It segments data by several factors, showing how ads perform across different contexts.

Represents a Google Ads campaign.

Represents a campaign’s budget settings.

Geographic View provides dimension fields aggregated at country level, including country, location type and ad group. It reports either the user’s physical location or an area of interest. This stream doesn’t include performance metrics. Use geographic_view_with_metrics for metrics such as clicks, impressions and conversions.

An enhanced version of geographic_view that adds performance metrics to dimension fields. Metrics include clicks, impressions, cost, conversions and CTR. Use this stream for geographic performance data.

Provides a geographic performance report built on the geographic_view resource. It adds detailed geo-target segments for region, metro, city and most specific location. It also includes device and ad network segments with performance metrics. This report is available only for non-manager accounts. Resolve the segments.geo_target_* resource names against the geo_target_constant resource for readable location names.

User Location View includes all metrics aggregated at country level. It reports metrics for the user’s physical location, split by targeted or untargeted location.

Provides metrics for display keywords targeted in display campaigns.

Provides a reporting view with metrics aggregated by topic. Topics are broad categories of user interests.

Provides Shopping campaign statistics aggregated across several product dimension levels. Merchant Center dimensions include brand, category, custom attributes, product condition and product type. Their values reflect each dimension’s state when the corresponding event was recorded.

Provides campaign keyword performance metrics.

Provides metrics and attributes for legacy ads from ad groups.

:::note Google Ads API constraints require the click_view stream to retrieve data one day at a time. It can retrieve only data from the past 90 days. You can’t request metrics for a Google Ads Manager account. Report streams are available only when retrieving data from a non-manager account. :::

:::warning Google Ads supports PERFORMANCE_MAX campaigns only at the campaign level. It doesn’t support them at the ad_group or ad stream level. Google removes this campaign type from ads report results. See info and Google Discussions. :::

:::note Streams with metric fields may return fewer rows than dimension-only streams for the same resource. Metric fields include clicks, impressions, cost and conversions. This happens because the Google Ads API omits rows where all metrics are zero when the query includes metrics. Omitted rows represent entity and segment combinations with no recorded activity. :::

Incremental streams sync data through the previous day, based on your Google Ads account time zone. Google Ads can filter data only by date without time. Some reports also can’t load data in real time because of Google Ads limitations.

From connector version 6.0.0, the Google Ads Data Retention Policy limits report streams and custom queries using segments.date to 37 months. The connector skips older data. If your configured start_date is older, the connector uses a date 37 months ago as the effective start. If start_date and end_date are both outside this window, the connector emits no records for that historical range. When upgrading from version 5.x or earlier, see the migration guide for guidance on preserving historical destination data.

Primary key selection

Primary keys uniquely identify records within streams. Selection considers the ID uniqueness scope described in the Google Ads API structure documentation. This approach keeps each record unique across different scopes and contexts. Segmentation is also essential for analysing performance data in the Google Ads API. As the Google Ads support documentation explains, segments provide detailed data by criteria such as device type or click interactions.

## Understand custom GAQL queries

Create additional Google Ads streams dynamically with custom queries.

Google Ads Query Language queries the Google Ads API. Review the Google Ads Query Language and query builder to validate your query. Then add the query when configuring the Google Ads source.

Example GAQL custom query:

SELECT
    campaign.name,
    metrics.conversions,
    metrics.conversions_by_conversion_date
FROM ad_group

The connector automatically adds segments.date to the WHERE clause when the SELECT clause includes it. Custom queries containing segments.date sync one day at a time. From connector version 6.0.0, these queries share the built-in report streams’ 37-month granular data retention window. The connector skips older report slices. See the migration guide for upgrade guidance.

Each configured custom query must work for every customer account ID. Otherwise, every query failing validation skips that customer ID. For example, queries with metric fields in the select clause won’t run against manager accounts.

Follow Google’s guidance on Selectability between segments and metrics when editing custom queries or default stream schemas. The connector also converts default stream schemas into GAQL queries. Fields such as segments.keyword.info.text, segments.keyword.info.match_type and segments.keyword.ad_group_criterion in the SELECT clause return only rows containing keywords. They remove any row without an associated keyword. This behaviour is often unclear and unwanted, and it can cause missing data records. If you need this field, add a new stream instead of editing an existing one.

:::info After updating or removing Custom GAQL Queries from an existing Google Ads source, refresh the source schema to retrieve your changes. :::

:::note Custom queries using click_view as the resource have the same limits as the built-in click_view stream. They retrieve only the past 90 days and sync one day at a time. :::

:::note Custom GAQL queries sync selected MESSAGE-type fields as JSON-encoded strings. Examples include change_event.old_resource and change_event.new_resource on the change_event resource. Parse these values downstream to read individual nested fields. :::

## Manager and client accounts

A manager account isn’t an “upgrade” of your Google Ads account. It’s a separate Google Ads account that you create. Think of it as an umbrella account linked to several individual Google Ads accounts. You can link new or existing Google Ads accounts and other manager accounts.

You can monitor ad performance, update campaigns and manage other tasks for those client accounts. Your manager account can also own a client account. This ownership lets you manage user access for the client account.

See Link for details about how it works and how to create one.

Manager Accounts (MCC) mainly focus on account management and oversight. They can access and manage multiple client accounts and view shared resources. They can also handle invitations to link client accounts.

Client Accounts focus more on operations. They cover campaign management, bidding, keywords, targeting, extensions, metrics, reporting, billing and other ad-specific functions.

Both account types can access many API resources, but their scope and purpose differ. Manager accounts provide broader oversight. Client accounts focus on specific advertising operations.

For details, see the official documentation..

Conversion windows

In digital advertising, a ‘conversion’ usually means a user completes a desired action after viewing or interacting with an ad. Examples include visiting the advertiser’s website, subscribing to a newsletter or making a purchase. The conversion window covers the period when an action can still receive credit for that ad.

For example, an online shoe shop runs an advert with a 30-day conversion window. If you click today, purchases made on its site within 30 days count as conversions from that advert. The conversion window’s length can vary with the advertiser’s goals and the product or service. A business might choose a shorter window for a limited-time offer. It might choose a longer window for a product that customers consider before buying.

The conversion window helps measure an advertising campaign’s effectiveness. Tracking actions after an ad view or interaction shows businesses how their ads perform. They can then adjust their strategies accordingly.

During each sync, the Google Ads source connector retrieves all conversions active within the specified conversion window. With a 30-day window, each sync retrieves all conversions active during the past 30 days. As a result, the same campaigns, ad groups or ads may appear to have different conversion numbers. Each record accurately shows that resource’s conversion count when the connector extracted data from the Google Ads API.

IP allow list

If you use Airbyte Cloud and your organization restricts access by IP, add the Airbyte Cloud IP addresses to your allow list.

Performance considerations

The Google Ads API limits constrains this source.

The Google Ads API can’t provide performance data at a level smaller than one day. Therefore, the Google Ads connector usually retrieves data through the previous day. For example, a sync at 5 PM on Wednesday retrieves data through Tuesday at midnight. It exports Wednesday’s data only during a later sync, such as one at 12:01 AM on Thursday. This approach avoids syncing partial performance data and resyncing it after Google records the full day. Without it, Wednesday’s 5 PM sync would retrieve Wednesday’s performance data from 12:01 AM to 5 PM. Another sync would then be needed after the day ends to retrieve all Wednesday data.

Changelog

Expand to review
VersionDatePull RequestSubject
6.1.112026-11-1091581Update dependencies
6.1.102026-11-0390953Raise the minimum supported Python version to 3.11
6.1.92026-11-0390594Update dependencies
6.1.82026-11-0288944Correct the suggested streams to the current stream names (13 of the 16 used names from before 2.0.0).
6.1.72026-10-2789917Update dependencies
6.1.62026-10-2078740Update dependencies
6.1.52026-10-1589011Upgrade to Python 3.13 and python-connector-base 4.1.1; upgrade pendulum to 3.x.
6.1.42026-10-0688123Report invalid custom GAQL queries as configuration errors that include the Google Ads error message.
6.1.32026-10-0587630Split interrupted reports with the CDK’s request window splitting (CDK 7.33.0); retry dropped criterion first syncs and mid-stream read timeouts instead of failing.
6.1.22026-09-2887026Fix state migration discarding mid-sync per-partition checkpoints, which caused retries to restart incremental streams from the start date.
6.1.12026-08-2585023Fixed multi-byte UTF-8 characters being corrupted at chunk boundaries in large streamed responses.
6.1.02026-07-0680952Add ad_performance and geo_performance streams.
6.0.02026-05-2978504Clamp incremental report dates to Google Ads’ 37-month granular data retention window.
5.0.22026-05-2978514Remove the Google Ads 400 response filter predicate to avoid buffering large streaming responses.
5.0.12026-05-2678419Classify unrecognized fields in custom GAQL queries as configuration errors.
5.0.02026-04-2073722Upgrade Google Ads API from v20 to v23 (field renames, removals, Performance Max ad network type support) and remove nullable bidding_strategy.id from primary keys of campaign_bidding_strategy and ad_group_bidding_strategy streams
4.2.62026-05-1378065Promoted release candidate to GA
4.2.6-rc.32026-05-0777835Update CDK to pre-release with runtime cap on concurrent partition generators to fix thread pool starvation deadlock
4.2.6-rc.22026-05-0177663Mount TimeoutHTTPAdapter on parent-stream sessions (customer_client, customer_client_non_manager, accessible_accounts) so the 5-minute HTTP socket timeout also covers parent-record fetches
4.2.6-rc.12026-04-2877514Update CDK to pre-release with stderr heartbeat diagnostics and concurrent-source deadlock fix
4.2.52026-04-2777037Promoted release candidate to GA
4.2.5-rc.12026-04-2776074Update CDK to pre-release with deadlock fix, add 5-minute HTTP socket timeout, and retry HTTP 500 (transient internal error) responses from the Google Ads API
4.2.42026-04-1676331Improve UNRECOGNIZED_FIELD error message for custom GAQL queries
4.2.32026-04-1675451Fix NULL values for MESSAGE-type fields (e.g., change_event.old_resource, change_event.new_resource) in custom GAQL queries
4.2.22026-04-1376276Rename “concurrent workers” to “concurrent threads” in connector spec
4.2.12026-03-2575458Set maxSecondsBetweenMessages to 4 hours
4.2.02026-03-1973321Add new geographic_view_with_metrics stream with metrics and dimension fields (geographic_view remains unchanged)
4.1.62026-02-1873636Promoting release candidate 4.1.6-rc.1 to a main version.
4.1.6-rc.12026-02-1672953Add HTTPAPIBudget and configurable concurrency level
4.1.52026-02-1673363Promoting release candidate 4.1.5-rc.2 to a main version.
4.1.5-rc.22026-02-1173269Fix decoder wiring to prevent OOM when using CustomRetriever
4.1.5-rc.12026-02-1072840Add retry for ChunkedEncodingError in response streaming
4.1.42026-01-2972453Promoting release candidate 4.1.4-rc.1 to a main version.
4.1.4-rc.12025-12-1770228Fix custom queries with tab characters and click_view custom queries
4.1.32025-11-2569844Fix custom queries regular expression to be case-insensitive
4.1.22025-11-2469837Fix schema loader for custom queries
4.1.12025-11-2469802Fix custom query regex conditions
4.1.02025-11-2069776Promoting release candidate 4.1.0-rc.8 to a main version.
4.1.0-rc.82025-10-2969084Fix criterion streams
4.1.0-rc.72025-10-1668030Fix schema loader for custom_queries streams
4.1.0-rc.62025-09-2566701Enables progressive rollouts
4.1.0-rc.52025-09-2566569Bumps to CDK v7, adds retry/backoff logic to custom schema loader
4.1.0-rc.42025-09-1866522Revert to CDK v6.60.12
4.1.0-rc.32025-09-1765535Update custom query dynamic streams to use regex for conditional incremental sync component mapping
4.1.0-rc.22025-08-2265149Update custom query URL to use Google Ads API v20
4.1.0-rc.12025-08-1963344Migrate custom_queries streams to low-code
4.0.22025-08-1664987Update dependencies
4.0.12025-08-0964612Update dependencies
4.0.02025-08-0764512Update API version to v20
3.15.02025-08-0464495Promoting release candidate 3.15.0-rc.1 to a main version.
3.15.0-rc.12025-07-2064124Switch all streams to paginated endpoints for improved reliability
3.14.22025-07-2863753Switching click_view to paginated endpoint for improved reliability
3.14.12025-07-2661472Update dependencies
3.14.02025-07-2363733Promoting release candidate 3.14.0-rc.1 to a main version.
3.14.0-rc.12025-07-1863357Migrate incremental events streams
3.13.02025-07-1863369Promoting release candidate 3.13.0-rc.2 to a main version.
3.13.0-rc.22025-07-1663348Minor metadata update
3.13.0-rc.12025-07-1662510Migrate click_view, campaign_bidding_strategy, and ad_group_bidding_strategy streams to low-code
3.12.02025-07-1663335Promoting release candidate 3.12.0-rc.2 to a main version.
3.12.0-rc.22025-07-1563323Fixes erroneous transformation override
3.12.0-rc.12025-07-1562510Migrate additional streams to low-code: See PR for more details
3.11.02025-07-1563302Promoting release candidate 3.11.0-rc.1 to a main version.
3.11.0-rc.12025-07-1462846Migrate views streams to Low Code
3.10.02025-07-1463282Promoting release candidate 3.10.0-rc.1 to a main version.
3.10.0-rc.12025-07-1062066Migrate AdGroup stream to Low Code
3.9.02025-07-1062900Promoting release candidate 3.9.0-rc.6 to a main version.
3.9.0-rc.62025-07-0862857Add per partition state migration
3.9.0-rc.52025-07-0462518Fix state migration for new empty states
3.9.0-rc.42025-07-0362513Update rollout flag in metadata
3.9.0-rc.32025-07-0362494Handle ServiceUnavailableErrors and retry on account check
3.9.0-rc.22025-07-0362505Fix state migration for empty states
3.9.0-rc.12025-06-1861674Migrate Campaign stream to Low Code
3.8.22025-05-3151664Update dependencies
3.8.12025-05-3061002Fix error during connection check for custom queries.
3.8.02025-05-3061000Promoting release candidate 3.8.0-rc.1 to a main version.
3.8.0-rc.12025-05-2860949Update API version to v18
3.7.102025-01-1147090Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
3.7.92024-10-1446893Update getting customers logic
3.7.82024-10-1246120Update dependencies
3.7.72024-10-0745852Change to the objects serialization in lists to JSON
3.7.62024-09-2146543Raise exception on missing stream
3.7.52024-09-2145801Update dependencies
3.7.42024-09-2044600Update API documentation URLs
3.7.32024-09-1445497Update dependencies
3.7.22024-09-0745263Update dependencies
3.7.12024-08-3144326Update dependencies
3.7.0 2024-08-1544095Migrate to google-ads v17
3.6.5 2024-08-1243882Update dependencies
3.6.42024-08-1043628Update dependencies
3.6.32024-08-0343138Update dependencies
3.6.22024-08-0242971Fix attribute error on check connection
3.6.12024-08-0242960Update error message for Interval Server Error
3.6.02024-07-3142544Migrate to CDK v4.0.2
3.5.102024-07-2742714Update dependencies
3.5.92024-07-2042339Update dependencies
3.5.82024-07-1341911Update dependencies
3.5.72024-07-1041528Update dependencies
3.5.62024-07-0941323Update dependencies
3.5.52024-07-0640933Update dependencies
3.5.42024-06-2540326Update dependencies
3.5.32024-06-2240158Update dependencies
3.5.22024-06-0639277[autopull] Upgrade base image to v1.2.2
3.5.12024-06-1339425Fix integration tests; update acceptance tests
3.5.02024-05-2237840Fix custom GAQL queries default value
3.4.32024-05-2038270Replace AirbyteLogger with logging.Logger
3.4.22024-04-2436638Schema descriptions and CDK 0.80.0
3.4.12024-04-0836891Optimize check method
3.4.02024-03-1936267Pin airbyte-cdk version to ^0
3.3.72024-03-1536208Added error message when there is the unrecognized field inside of the custom query
3.3.62024-03-0135664Fix error for new customers for incremental events streams
3.3.52024-02-2835709Handle 2-Step Verification exception as config error
3.3.42024-02-2135493Rolling back the patch 3.3.3 made for user_interest steam
3.3.32024-02-1435280Temporary patch that disables some fields to avoid 500 error when syncing user_interest steam
3.3.22024-02-1235158Manage dependencies with Poetry.
3.3.12024-01-1634007prepare for airbyte-lib
3.3.02024-01-1234212Remove metric from query in Ad Group stream for non-manager account
3.2.12024-01-1234200Disable raising error for not enabled accounts
3.2.02024-01-0933707Add possibility to sync all connected accounts
3.1.02024-01-0933603Fix two issues in the custom queries: automatic addition of segments.date in the query; incorrect field type for DATE fields.
3.0.22024-01-0833494Add handling for 401 error while parsing response. Add metrics.cost_micros field to Ad Group stream.
3.0.12023-12-2633769Run a read function in a separate thread to enforce a time limit for its execution
3.0.02023-12-0733120Upgrade API version to v15
2.0.42023-11-1032414Add backoff strategy for read_records method
2.0.32023-11-0232102Fix incremental events streams
2.0.22023-10-3132001Added handling (retry) for InternalServerError while reading the streams
2.0.12023-10-2731908Base image migration: remove Dockerfile and use the python-connector-base image
2.0.02023-10-0431048Fix schem default streams, change names of streams.
1.0.02023-09-2830705Fix schemas for custom queries
0.11.12023-09-2630758Exception should not be raises if a stream is not found
0.11.02023-09-2330704Update error handling
0.10.02023-09-1930091Fix schemas for correct primary and foreign keys
0.9.02023-09-1428970Add incremental deletes for Campaign and Ad Group Criterion streams
0.8.12023-09-1330376Revert pagination changes from 0.8.0
0.8.02023-09-0130071Delete start_date from required parameters and fix pagination
0.7.42023-07-2828832Update field descriptions
0.7.32023-07-2428510Set dates with client’s timezone
0.7.22023-07-2028535UI improvement: Make the query field in custom reports a multi-line string field
0.7.12023-07-17283650.3.1 and 0.3.2 follow up: make today the end date, not yesterday
0.7.02023-07-1228246Add new streams: labels, criterions, biddig strategies
0.6.12023-07-1228230Reduce amount of logs produced by the connector while working with big amount of data
0.6.02023-07-1028078Add new stream Campaign Budget
0.5.02023-07-0728042Add metrics & segment to Campaigns stream
0.4.32023-07-0527959Add audience and user_interest streams
0.3.32023-07-0327913Improve Google Ads exception handling (wrong customer ID)
0.3.22023-06-2927835Fix bug introduced in 0.3.1: update query template
0.3.12023-06-2627711Refactor date slicing; make start date inclusive
0.3.02023-06-2627738License Update: Elv2
0.2.242023-06-0627608Improve Google Ads exception handling
0.2.232023-06-0626905Replace deprecated authSpecification in the connector specification with advancedAuth
0.2.222023-06-0226948Refactor error messages; add pattern_descriptor for fields in spec
0.2.212023-05-3025314Add full refresh custom table asset_group_listing_group_filter
0.2.202023-05-3025624Add asset Resource to full refresh custom tables (GAQL Queries)
0.2.192023-05-1526209Handle Token Refresh errors as config_error
0.2.182023-05-1525947Improve GAQL parser error message if multiple resources provided
0.2.172023-05-1125987Categorized Config Errors Accurately
0.2.162023-05-1025965Fix Airbyte date-time data-types
0.2.142023-03-2124945For custom google query fixed schema type for “data_type: ENUM” and “is_repeated: true” to array of strings
0.2.132023-03-2124338Migrate to v13
0.2.122023-03-1722985Specified date formatting in specification
0.2.112023-03-1323999Fix incremental sync for Campaigns stream
0.2.102023-02-1122703Add support for custom full_refresh streams
0.2.92023-01-2321705Fix multibyte issue; Bump google-ads package to 19.0.0
0.2.82023-01-1821517Write fewer logs
0.2.72023-01-1020755Add more logs to debug stuck syncs
0.2.62022-12-2220855Retry 429 and 5xx errors
0.2.52022-11-2219700Fix schema for campaigns stream
0.2.42022-11-0919208Add TypeTransofrmer to Campaings stream to force proper type casting
0.2.32022-10-1718069Add segments.hour, metrics.ctr, metrics.conversions and metrics.conversions_values fields to campaigns report stream
0.2.22022-10-2117412Release with CDK >= 0.2.2
0.2.12022-09-2917412Always use latest CDK version
0.2.02022-08-2315858Mark the query and table_name fields in custom_queries as required
0.1.442022-07-2715084Fix data type ad_group_criterion.topic.path in display_topics_performance_report and shifted campaigns to non-managers streams
0.1.432022-07-1214614Update API version to v11, update google-ads to 17.0.0
0.1.422022-06-0813624Update google-ads to 15.1.1, pin protobuf==3.20.0 to work on MacOS M1 machines (AMD)
0.1.412022-06-0813618Add missing dependency
0.1.402022-06-0213423Fix the missing data issue
0.1.392022-05-1812914Fix GAQL query validation and log auth errors instead of failing the sync
0.1.382022-05-1212807Documentation updates
0.1.372022-05-0612651Improve integration and unit tests
0.1.362022-04-1912158Fix *_labels streams data type
0.1.352022-04-189310Add new fields to reports
0.1.342022-03-2911602Add budget amount to campaigns stream.
0.1.332022-03-2911513When end_date is configured in the future, use today’s date instead.
0.1.322022-03-2411371Improve how connection check returns error messages
0.1.312022-03-2311301Update docs and spec to clarify usage
0.1.302022-03-2311221Add *_labels streams to fetch the label text rather than their IDs
0.1.292022-03-2210919Fix user location report schema and add to acceptance tests
0.1.282022-02-2510372Add network fields to click view stream
0.1.272022-02-1610315Make ad_group_ads and other streams support incremental sync.
0.1.262022-02-1110150Add support for multiple customer IDs.
0.1.252022-02-049812Handle EXPIRED_PAGE_TOKEN exception and retry with updated state.
0.1.242022-02-049996Use Google Ads API version V9.
0.1.232022-01-258669Add end date parameter in spec.
0.1.222022-01-249608Reduce stream slice date range.
0.1.212021-12-289149Update title and description
0.1.202021-12-229071Fix: Keyword schema enum
0.1.192021-12-148431Add new streams: Geographic and Keyword
0.1.182021-12-098225Include time_zone to sync. Remove streams for manager account.
0.1.162021-11-228178Clarify setup fields
0.1.152021-10-076684Add new stream click_view
0.1.142021-10-016565Fix OAuth Spec File
0.1.132021-09-276458Update OAuth Spec File
0.1.112021-09-226373Fix inconsistent segments.date field type across all streams
0.1.102021-09-136022Annotate Oauth2 flow initialization parameters in connector spec
0.1.92021-09-075302Add custom query stream support
0.1.82021-08-035509Allow additionalProperties in spec.json
0.1.72021-08-035422Correct query to not skip dates
0.1.62021-08-035423Added new stream UserLocationReport
0.1.52021-08-035159Add field login_customer_id to spec
0.1.42021-07-284962Support new Report streams
0.1.32021-07-234788Support main streams, fix bug with exception DATE_RANGE_TOO_NARROW for incremental streams
0.1.22021-07-064539Add AIRBYTE_ENTRYPOINT for Kubernetes support
0.1.12021-06-234288Fix Bugfix: Correctly declare required parameters
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.