[go: nahoru, domu]

We’ve always enabled advertisers to export their ad campaigns from AdWords to accomplish their online advertising goals. We recently committed to updating our AdWords API Terms and Conditions to give advertisers using third party ad management tools even more flexibility.

Today, we’re making the following changes to the Adwords API Terms and Conditions:
  1. We’ve removed former Section III(2)(c)(i) (“Co-Mingling of AdWords Data: Input Fields for Creation Functionality and Management Functionality”), which covered Adwords API clients showing input fields that collected or transmitted campaign management data in the same tab or screen with the content of third parties.
  2. We’ve removed former Section III(2)(c)(ii) (“Co-Mingling of AdWords Data: Copying Data”), which covered AdWords API clients offering functionality that copied campaign management data between Google and a third party.
  3. We’ve updated Section (III)(2)(f) ("Required Minimum Functionality"), in part by adding subsection (ii) (“Data Transmission”), which requires disclosure to users of the names of networks the data is transmitted to, explanation of any incompatibilities, and opportunities for users to resolve any issues.
For more information about these changes, please review our updated Terms and Conditions.

- The AdWords API Team

Today, in an ongoing effort to improve clarity, we have released an update to the Terms & Conditions for AdWords API Clients. As a reminder, per our terms and conditions, Google retains the right to modify the terms and conditions at any time. Note that continued use of the API means that you accept these terms. You can refuse to accept the terms by ceasing to use the API.

Below is an overview of what has changed:
  1. We’ve updated the definition of an AdWords API client. In addition, we’ve modified the definition of an “End-Advertiser-Only AdWords API Client” (section I).
  2. We clarify when we may terminate a token for non-use (section II.1).
  3. We’ve added a clause specifying that a token may only be used for the applications/tools that it was approved for in the application process, and that we need to be notified of any changes (section II.5).
  4. We’ve clarified the “Copying Data” section of the co-mingling clause to ensure that users manually import or export all campaigns (section III.2.c.ii).
  5. We will now require clients to contact Google within 15 days of a change of control via written notice and re-application for a token (section IV.16).
  6. We’ve added an "experimental program" clause and are deprecating our current 4-month deprecation clause (section IV.2.a). We are giving people 4 months notice before these changes take effect (section IV.17).
Please review the complete Terms & Conditions here.