Google Ads Update
Automatic handling of renamed API fields, and clearer failures
Google renamed a number of fields in the Google Ads Query Language (GAQL) API in recent versions. Configurations still using the old field names had their report queries rejected by Google — and in some cases the job finished without surfacing an error while the report table simply wasn't imported. This update fixes both:
- Old field names keep working. If your query uses a field Google has since renamed, the extractor now automatically sends the current name to the API and keeps your output table's original column names — so existing configurations and downstream tables continue to run with no change on your side. (Controlled by a new advanced setting, on by default, contact support if you want to know more)
- Failures are no longer silent. If a run fails for every account, the job now fails with a clear error instead of finishing "successfully" with no data. A single unreadable account in a multi-account setup is still skipped, as before.
- New "Continue on account failure" option (on by default) — keep importing the other accounts when one fails; turn it off to stop on the first error.
No action needed. Optionally, update your query to the current field names and switch off the compatibility setting to receive the native v25 columns.
Field renames handled automatically (support reference)
| Old name | Current (v25) name |
|---|---|
| metrics.average_cpv | metrics.trueview_average_cpv |
| metrics.video_views | metrics.video_trueview_views |
| metrics.video_view_rate | metrics.video_trueview_view_rate |
| metrics.video_view_rate_in_feed | metrics.video_trueview_view_rate_in_feed |
| metrics.video_view_rate_in_stream | metrics.video_trueview_view_rate_in_stream |
| metrics.video_view_rate_shorts | metrics.video_trueview_view_rate_shorts |
| campaign.start_date | campaign.start_date_time |
| campaign.end_date | campaign.end_date_time |