Google Ads API is returning to beta status. Please read our blog post for more details.

Migration Planning

This guide provides a high-level overview of the major steps to complete a migration of an existing AdWords API application to Google Ads API.

Make your first call

As mentioned in the Carryover concepts, the credentials that were previously used with the AdWords API are equally applicable to the Google Ads API. To ensure that credentials are correct, the first step is to try to make your first API call.

Learn the API and try the samples

Using your preferred client library, become familiar with the variety of sample code. Be sure to try both search and mutate examples in order to learn the differences in API between the Google Ads API and the AdWords API. While the concepts are the same, the call formats are significantly different. The objective at this point to become familiar enough with the new call formats in order to determine the work required to migrate your specific application.

Plan your migration

The Google Ads API and the AdWords API have been tested for concurrent usage within the same application. This implies that an application can be migrated incrementally rather than as one massive changeover.

In order plan a migration, there are two categories of task: overall migration components and per-service components.

Overall migration components include:

  1. Overhead of running both APIs simultaneously.
  2. Migrating Reports

Per-service components include:

  1. Information retrieval: migrating queries / searches
  2. Information updates: migrating mutates

It is possible to use the Google Ads API for retrieval and the legacy AdWords API code for information updates within the same application. It depends on the number of updates and desired level of granularity for a specific migration.

Ensure that the migration plan allocates sufficient time for testing. Use test accounts for this purpose.

Phased rollout

Once the migration plan is complete, complete the code implementation and deployment service-by-service. This limits impact while gaining familiarity with the new API.

By the end of this phase, all existing and new features of the application should be using the Google Ads API in production.

Complete transition

From the time of the V1 release of the Google Ads API, there will be approximately one year to complete the migration to the new code base. Google will sunset and disable the AdWords API at that time. Calls to the AdWords API will fail after the sunset.

发送以下问题的反馈:

此网页
Google Ads API Beta
Google Ads API Beta
需要帮助?请访问我们的支持页面