Next steps

  • Useful resources are available to continue your Google Ads API journey after a successful API call.

  • Suggested topics for further exploration include Performance Max campaigns, conversion management, and reporting.

  • References for building and productizing your app, such as best practices and access levels, are provided.

Now that you've made a successful API call using the Google Ads API, here are some useful resources to continue on your Google Ads API journey.

Experiment safely

You can experiment with the Google Ads API without modifying your production Google Ads accounts. Here are some ways to experiment with the API without risking your existing campaigns:

  • Use test accounts: With a developer token with test account access, or by creating test accounts under your manager account, you can make API calls that don't affect your production data. We recommend using test accounts for all development and testing, as described in Quick start.
  • Stick to read-only requests: Many API calls, such as retrieving reports or campaign settings, are read-only and don't modify your account data. The example in Quick start, which retrieves a list of campaigns, is a read-only request that does not modify data.
  • Use validate_only for mutate requests: If you need to test a request that modifies data (a mutate request), you can use the validate_only field. When this field is set to true, the request is validated, but not executed, allowing you to check for errors without changing any data.
  • Review Change History: If you make a change using the API, you can review it in Change history in the Google Ads UI.

Suggested topics for further exploration

References for building and productizing your app

Previous
Common errors