We are happy to announce the release of the AdWords API Version 12
(V12).
V12 introduces several changes to the AdWords API. Below, you'll find
the main highlights from this release. For a complete list of V12
changes, please see our release notes (http://www.google.com/apis/ adwords/developer/releasenotes.html).
V12 HIGHLIGHTS
* Conversion Optimizer support: Now you can enable Conversion
Optimizer (http://www.google.com/apis/adwords/developer/ adwords_api_services.html#conversion_optimizer_section) to pay only
when an ad click leads to a conversion. Using Conversion Optimizer
requires conversion tracking to be enabled on an existing campaign
with at least 200 conversions in the past 30 days.
Per our versioning policy (http://www.google.com/support/adwordsapi/ bin/answer.py?answer=33152), V11 will be supported for four months
from today, after which time it will be turned off. Therefore, please
make sure that you upgrade to V12 before July 26, 2008. As with every
new version of the AdWords API, we strongly encourage you to review
the Release Notes (http://www.google.com/apis/adwords/developer/ releasenotes.html) section of the Developer's Guide (http://
www.google.com/apis/adwords/developer/index.html) to learn more about
this version.
The release notes indicate that the AdGroup.id field has been changed
from V11 to V12. However there is no difference in the field
description between the V11 and V12 versions of the docs. Is this
simply an error in the release notes?
<adwordsapiadvi...@google.com> wrote:
> We are happy to announce the release of the AdWords API Version 12
> (V12).
> V12 introduces several changes to the AdWords API. Below, you'll find
> the main highlights from this release. For a complete list of V12
> changes, please see our release notes (http://www.google.com/apis/ > adwords/developer/releasenotes.html).
> V12 HIGHLIGHTS
> * Conversion Optimizer support: Now you can enable Conversion
> Optimizer (http://www.google.com/apis/adwords/developer/ > adwords_api_services.html#conversion_optimizer_section) to pay only
> when an ad click leads to a conversion. Using Conversion Optimizer
> requires conversion tracking to be enabled on an existing campaign
> with at least 200 conversions in the past 30 days.
> Per our versioning policy (http://www.google.com/support/adwordsapi/ > bin/answer.py?answer=33152), V11 will be supported for four months
> from today, after which time it will be turned off. Therefore, please
> make sure that you upgrade to V12 before July 26, 2008. As with every
> new version of the AdWords API, we strongly encourage you to review
> the Release Notes (http://www.google.com/apis/adwords/developer/ > releasenotes.html) section of the Developer's Guide (http://www.google.com/apis/adwords/developer/index.html) to learn more about
> this version.
> The release notes indicate that the AdGroup.id field has been changed
> from V11 to V12. However there is no difference in the field
> description between the V11 and V12 versions of the docs. Is this
> simply an error in the release notes?
> Thanks.
> Tim
> On Mar 26, 10:12 am, AdWords API Advisor
> <adwordsapiadvi...@google.com> wrote:
> > We are happy to announce the release of the AdWords API Version 12
> > (V12).
> > V12 introduces several changes to the AdWords API. Below, you'll find
> > the main highlights from this release. For a complete list of V12
> > changes, please see our release notes (http://www.google.com/apis/ > > adwords/developer/releasenotes.html).
> > V12 HIGHLIGHTS
> > * Conversion Optimizer support: Now you can enable Conversion
> > Optimizer (http://www.google.com/apis/adwords/developer/ > > adwords_api_services.html#conversion_optimizer_section) to pay only
> > when an ad click leads to a conversion. Using Conversion Optimizer
> > requires conversion tracking to be enabled on an existing campaign
> > with at least 200 conversions in the past 30 days.
> > Per our versioning policy (http://www.google.com/support/adwordsapi/ > > bin/answer.py?answer=33152), V11 will be supported for four months
> > from today, after which time it will be turned off. Therefore, please
> > make sure that you upgrade to V12 before July 26, 2008. As with every
> > new version of the AdWords API, we strongly encourage you to review
> > the Release Notes (http://www.google.com/apis/adwords/developer/ > > releasenotes.html) section of the Developer's Guide (http://www.google.com/apis/adwords/developer/index.html) to learn more about
> > this version.
Nice to see it released, I would've liked to see some more optimizer
options, but I'm not complaining...
Just out of curiosity, I assume the developers allowed to set monthly
budget know who they are?
"Monthly - Indicates a monthly base budget (available only to a
limited set of developers). new in v12"
On 26 mrt, 16:12, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
> We are happy to announce the release of the AdWords API Version 12
> (V12).
> V12 introduces several changes to the AdWords API. Below, you'll find
> the main highlights from this release. For a complete list of V12
> changes, please see our release notes (http://www.google.com/apis/ > adwords/developer/releasenotes.html).
> V12 HIGHLIGHTS
> * Conversion Optimizer support: Now you can enable Conversion
> Optimizer (http://www.google.com/apis/adwords/developer/ > adwords_api_services.html#conversion_optimizer_section) to pay only
> when an ad click leads to a conversion. Using Conversion Optimizer
> requires conversion tracking to be enabled on an existing campaign
> with at least 200 conversions in the past 30 days.
> Per our versioning policy (http://www.google.com/support/adwordsapi/ > bin/answer.py?answer=33152), V11 will be supported for four months
> from today, after which time it will be turned off. Therefore, please
> make sure that you upgrade to V12 before July 26, 2008. As with every
> new version of the AdWords API, we strongly encourage you to review
> the Release Notes (http://www.google.com/apis/adwords/developer/ > releasenotes.html) section of the Developer's Guide (http://www.google.com/apis/adwords/developer/index.html) to learn more about
> this version.
It changes from int to long, but the v10/v11docs were accidently
changed (they make you believe that in v11 AdGroup.Id is a long, but
it is actually an int).
BTW The v12 docs has another omission:
DefinedReportJob.AdGroups is defined as an int[], I assume that must
be long[] ?!
Or does the API have an error?
Thanks.
On Mar 26, 5:10 pm, tozor <t...@adlucent.com> wrote:
> The release notes indicate that the AdGroup.id field has been changed
> from V11 to V12. However there is no difference in the field
> description between the V11 and V12 versions of the docs. Is this
> simply an error in the release notes?
Thanks for the feedback on the documentation update. The v11 docs do
appear to have been changed inadvertently; the ad group IDs are still
ints, not longs, in v11. I've let the docs team know about that.
As for the DefinedReportJob.AdGroups array, the v12 docs are correct.
The v12 ReportService service still expects an array of ints (which is
a little counter-intuitive, I know).
And as for the monthly budget changes, yes, accounts that have been
enabled for monthly budgets via the API will have been notified.
<zdvsoftw...@hotmail.com> wrote:
> It changes from int to long, but the v10/v11docs were accidently
> changed (they make you believe that in v11 AdGroup.Id is a long, but
> it is actually an int).
> BTW The v12 docs has another omission:
> DefinedReportJob.AdGroups is defined as an int[], I assume that must
> be long[] ?!
> Or does the API have an error?
> Thanks.
> On Mar 26, 5:10 pm, tozor <t...@adlucent.com> wrote:
> > The release notes indicate that the AdGroup.id field has been changed
> > from V11 to V12. However there is no difference in the field
> > description between the V11 and V12 versions of the docs. Is this
> > simply an error in the release notes?
Please note that now you can enable Conversion Optimizer to adjust
cost-per-acquisition bids through the AdWords API. The way this
feature was initially described was inaccurate. We apologize for the
confusion.
-- Borana Toska, Product Marketing
On Mar 27, 2:12 am, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
> We are happy to announce the release of the AdWords API Version 12
> (V12).
> V12 introduces several changes to the AdWords API. Below, you'll find
> the main highlights from this release. For a complete list of V12
> changes, please see our release notes (http://www.google.com/apis/ > adwords/developer/releasenotes.html).
> V12 HIGHLIGHTS
> * Conversion Optimizer support:Nowyou can enable Conversion
> Optimizer (http://www.google.com/apis/adwords/developer/ > adwords_api_services.html#conversion_optimizer_section) to pay only
> when an ad click leads to a conversion. Using Conversion Optimizer
> requires conversion tracking to be enabled on an existing campaign
> with at least 200 conversions in the past 30 days.
> Per our versioning policy (http://www.google.com/support/adwordsapi/ > bin/answer.py?answer=33152), V11 will be supported for four months
> from today, after which time it will be turned off. Therefore, please
> make sure that you upgrade to V12 before July 26, 2008. As with every
> new version of the AdWords API, we strongly encourage you to review
> the Release Notes (http://www.google.com/apis/adwords/developer/ > releasenotes.html) section of the Developer's Guide (http://www.google.com/apis/adwords/developer/index.html) to learn more about
> this version.
