Google-ads v21 — Breaking Changes Checklist

7 items total3 critical~1 hour for a typical integration

Before You Upgrade

1.Review the official Google Ads API v21 release notes for a comprehensive list of all changes.
2.Identify all areas of your codebase that interact with the resources and services affected by the breaking changes listed above.
3.Update your Google Ads client libraries to the latest compatible version.
4.Set up a staging environment or use test accounts to perform thorough testing.

0/3

Review modifications to fields, resources, and services in v21 that may impact your existing integrations.

Remove usage of the deprecated CAMPAIGN_DRAFT status.Criticaleasy

The CAMPAIGN_DRAFT status is deprecated and will be removed in a future version. Migrate any logic relying on this status to use 'PROPOSED' instead.

⚠ Your integration may fail when trying to use or query for campaigns with the CAMPAIGN_DRAFT status.

Update AssetGroupListingGroupFilter syntax.Highmedium

The 'asset_group_listing_group_filter_type' field has been deprecated. Use the new 'listing_group_filter_type' field with updated enum values.

⚠ Requests involving asset group listing group filters might fail or behave unexpectedly.

Remove CampaignCriterion bid constants from mutate requests.Criticaleasy

CampaignCriterion bid constants are no longer supported in mutate requests. Ensure your code does not attempt to set these values.

⚠ Mutate requests containing CampaignCriterion bid constants will be rejected.

0/1

Ensure you are using the latest compatible versions of the Google Ads client libraries.

Update your Google Ads client library to the latest version.Higheasy

New API versions often require updated client libraries to support new features and address breaking changes.

⚠ You might encounter compatibility issues or be unable to use new API features if you don't update.

0/3

Thoroughly test your integration in a staging environment before deploying to production.

Test all API calls that interact with deprecated or modified fields/resources.Criticalmedium

Verify that your code correctly handles the changes and continues to function as expected.

⚠ Production errors and unexpected behavior in campaign management or reporting.

Validate reporting data for any changes in metrics or dimensions.Mediummedium

Some changes might affect how certain metrics are calculated or reported. Cross-reference with the UI or previous API versions.

⚠ Inaccurate or inconsistent reporting data, leading to poor campaign optimization decisions.

Review and update error handling logic for potential new error codes or messages.Loweasy

New API versions can introduce new error types or change existing ones. Ensure your application can gracefully handle them.

⚠ Application failures or incorrect responses when encountering new API errors.

✓Deploy the updated code to your staging environment.
✓Execute all test cases, paying close attention to the areas identified as affected by breaking changes.
✓Monitor API logs for any new or recurring errors.
✓Compare reporting data from v21 with data from the previous version to ensure consistency.
✓Once confident, deploy the changes to your production environment.
✓Continue to monitor performance and error logs post-deployment.

Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.