Migrate from v22 to v23

What Changed

customer.customer_lifecycle_goal

// Field removed, consider alternatives or removing

asset_group_listing_ad.listing_ad.product_ad.product_images

asset_group_listing_ad.listing_ad.product_ad.product_item_ids

Migration Steps

1. 1

   Update Google Ads API Client Library

   code

   Install the latest version of the Google Ads API client library for your programming language. This ensures compatibility with v23 and provides access to new features.

   • ↳Check the official Google Ads API documentation for the correct installation command for your language.
   • ↳Ensure all dependencies are compatible with the new client library version.
2. 2

   Address Breaking Changes

   code

   Review and modify your code to accommodate the breaking changes identified, particularly the removal of 'customer_lifecycle_goal' and deprecation of certain asset group fields.

   • ↳If 'customer_lifecycle_goal' was critical, investigate alternative ways to achieve the same objective in v23.
   • ↳Update any code that references deprecated asset group listing ad fields to use their replacements.
3. 3

   Update Service Endpoints and Request Headers

   config

   Ensure your API requests are directed to the correct v23 endpoints. While often handled by the client library, verify your configuration if you're making direct HTTP requests.

   • ↳The endpoint URL typically includes the API version.
   • ↳Confirm that any custom request headers, especially those related to developer tokens or authentication, are still valid.
4. 4

   Thoroughly Test Reporting and Campaign Management

   test

   Execute your existing test suite and conduct additional manual testing focused on campaign creation, updates, deletions, and performance reporting.

   • ↳Pay close attention to reports that might have been affected by field deprecations.
   • ↳Test edge cases and scenarios that were previously problematic.
5. 5

   Deploy to Staging Environment

   deploy

   Deploy your updated integration to a staging or non-production environment that mirrors your production setup. This allows for final validation without impacting live campaigns.

   • ↳Ensure your staging environment uses a separate Google Ads account or test accounts.
   • ↳Monitor logs closely for any unexpected errors or warnings.
6. 6

   Monitor Production Performance Post-Deployment

   verify

   After deploying to production, closely monitor key performance indicators (KPIs) and API error logs for any anomalies. Be prepared to roll back if necessary.

   • ↳Set up alerts for unusual error rates or performance drops.
   • ↳Have a rollback plan in place in case of critical issues.

Testing Checklist

1. 1.

   Campaign Creation and Updates

   Verify that new campaigns can be created and existing ones updated without errors, checking all relevant fields.

2. 2.

   Ad Group and Ad Management

   Test the creation, modification, and deletion of ad groups and ads, ensuring asset group fields function correctly.

3. 3.

   Performance Reporting

   Run reports for various metrics (impressions, clicks, conversions) and compare results against expected values or previous versions.

4. 4.

   Asset Uploads and Management

   Ensure all asset types, including images and videos, can be uploaded and associated with campaigns correctly.

5. 5.

   Error Handling

   Simulate API errors (e.g., invalid requests) to confirm your application handles them gracefully.

Common Mistakes