Pablo Martin Calvo
12/29/2025, 2:31 PMkapa.ai
12/29/2025, 2:31 PMad_group_ad stream never exposes metrics in its schema. What we do see: - The Google Ads connector has gone through several breaking changes (1.0.0, 2.0.0, 3.0.0) that affected schemas and default streams. In all of these cases, the recommended fix for missing/changed fields is to refresh the source schema and reset affected streams after upgrading. [[Upgrading to 1.0.0](https://docs.airbyte.com/integrations/sources/google-ads-migrations#upgrading-to-100); [Upgrading to 2.0.0](https://docs.airbyte.com/integrations/sources/google-ads-migrations#upgrading-to-200); [Upgrading to 3.0.0](https://docs.airbyte.com/integrations/sources/google-ads-migrations#upgrading-to-300)] - There are known cases where: - A stream that used to exist is no longer present after an upgrade (e.g. ad_group_ad_report vs ad_group_ads), and the fix was to align with the new default streams and names. [[Google Ads ad_group_ad_report failing](https://discuss.airbyte.io/t/792)] - Custom queries or streams don’t show up in the connection schema until the schema is refreshed or the source is recreated, or when the customer_id doesn’t actually have permission to access the underlying accounts. [[Custom GAQL not working](https://discuss.airbyte.io/t/3756); [Missing custom queries streams](https://github.com/airbytehq/airbyte/issues/52680)] - There is also a closed issue about custom GAQL queries failing when metrics are included, but that’s about a TypeError: 'GAQL' object is not subscriptable during check_connection, not about metrics missing from the ad_group_ad schema. [[GAQL object not subscriptable](https://github.com/airbytehq/airbyte/issues/59182)] None of these sources clearly state “`ad_group_ad` cannot/does not expose metrics,” nor do they describe a confirmed bug matching exactly what you’re seeing. Given that, the only documented steps I can confidently suggest (based on the sources) are: 1. Refresh the source schema for your Google Ads source. 2. Reset the affected streams (including ad_group_ad) after the refresh. [[Upgrading to 1.0.0](https://docs.airbyte.com/integrations/sources/google-ads-migrations#upgrading-to-100); [Upgrading to 2.0.0](https://docs.airbyte.com/integrations/sources/google-ads-migrations#upgrading-to-200)] 3. If you’re using custom GAQL for ad_group_ad, double‑check that: - The custom stream actually appears in the catalog after a schema refresh. - Your customer_id / login_customer_id has access to the accounts you expect, otherwise some streams/fields may not appear. [[Missing custom queries streams](https://github.com/airbytehq/airbyte/issues/52680)] Beyond these general remediation steps, the knowledge sources do not explicitly mention a known issue where ad_group_ad returns only properties and no metrics, so I can’t confirm it as a documented bug from this context alone.