Google-ads v22 — Breaking Changes Checklist

6 items total2 critical~1 hour for a typical integration

Before You Upgrade

1.Identify all API endpoints and resources your integration interacts with.
2.Consult the official Google Ads API v22 release notes for a comprehensive list of changes.
3.Review the 'API Changes' section of this checklist and note any affected areas in your codebase.
4.Ensure your development environment has the latest stable version of the Google Ads client library installed.
5.Backup your current codebase and any relevant configuration files.

API Changes

0/2

Review modifications to existing resources, fields, and methods. These changes can directly impact your API requests and responses.

Remove usage of the 'campaign_budget' field in CampaignService.Criticaleasy

The 'campaign_budget' field in the CampaignService has been removed. You should no longer attempt to set or retrieve this field.

⚠ API calls attempting to use the removed field will fail with an error.

Update logic for AdGroupAd statuses to account for new enum values.Highmedium

The AdGroupAd status enum has been updated with new values. Ensure your code handles these new statuses gracefully to avoid unexpected behavior.

⚠ Your system might misinterpret ad statuses, leading to incorrect reporting or campaign management.

Authentication & Authorization

0/1

Verify your authentication flow and any changes to access scopes or permissions. Incorrect authentication can prevent API access entirely.

Review and confirm your OAuth2 scopes are still valid and sufficient.Mediumeasy

While no specific scope changes are announced for v22, it's good practice to review your granted scopes to ensure they align with your application's current needs and any potential future requirements.

⚠ Your application might lose access to certain Google Ads data or functionalities if scopes are inadvertently reduced or become insufficient.

SDK & Library Updates

0/1

Ensure you are using a compatible version of the Google Ads client libraries or SDKs. Outdated libraries can cause integration issues.

Update your Google Ads client library to the latest version compatible with v22.Criticaleasy

Using an older version of the client library may result in compatibility issues or prevent you from accessing new features and fixes in v22.

⚠ You may encounter errors, unexpected behavior, or be unable to use features available in v22.

Testing & Validation

0/2

Thoroughly test your integration after applying changes to ensure everything functions as expected.

Execute regression tests for critical functionalities.Highmedium

Run your suite of automated and manual tests to verify that existing features continue to work correctly after the API upgrade and code modifications.

⚠ Undiscovered bugs or regressions could lead to data loss, incorrect ad serving, or broken workflows.

Validate key reporting metrics and data accuracy.Mediummedium

Compare reports generated with v22 against historical data to ensure consistency and accuracy, paying close attention to any fields that might have been affected by API changes.

⚠ Inaccurate reporting can lead to poor decision-making and flawed campaign optimization strategies.

After You Upgrade

✓Deploy your updated integration to a staging or testing environment.
✓Perform smoke tests on all critical API interactions.
✓Execute your full regression test suite.
✓Monitor API logs for any new errors or warnings.
✓Manually verify key reports and campaign performance metrics.
✓Gradually roll out the changes to your production environment while continuing to monitor closely.

Never get blindsided by an API change again

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

Join the Waitlist