And... since we had another extra two weeks of development time, we
were able to include the AdWords Keyword Tool
(https://adwords.google.com/support/bin/answer.py?answer=25109) to V3.
So to recap...
Version 3 includes support for our new Content Bidding
(https://adwords.google.com/support/bin/answer.py?answer=26507)
functionality. For background information on the Content Bidding
feature, please see our earlier post entitled "Exposing Content
Bidding via the API in January"
(http://adwordsapi.blogspot.com/2005/11/exposing-content-bidding-via-api-in.html).
In addition, we have exposed the AdWords Keyword Tool via a new
KeywordToolService
(http://www.google.com/apis/adwords/developer/KeywordToolService.html)
Finally, the campaignNegativeKeywords
[http://www.google.com/apis/adwords/developer/Campaign.html#campaignNegativeKeywords?version=3&from=2]
field is deprecated. Please use setCampaignNegativeCriteria and
getCampaignNegativeCriteria
[http://www.google.com/apis/adwords/developer/CriterionService.html#getCampaignNegativeCriteria]
requests in CriterionService instead.
Per our earlier stated policy, V2 will be supported for one month from
today, at which time it will be turned off. Therefore, please make sure
that you upgrade your code to v3 before March 27, 2006.
For technical details about V3, please review the Release Notes
[http://www.google.com/apis/adwords/developer/ReleaseNotes.html]
section of the Developer's Guide.
-- Rohit Dhawan, Product Manager
http://www.google.com/support/adwordsapi/bin/answer.py?answer=21996
Best regards,
Peer Jakobsen
AdWordsAPIAdvisor a écrit :
This is another symptom of Google's growing arrogance and
self-importance which is contributing to the general swell of bad
feeling about Google.
I really hope that the API team will reconsider this deadline - the
continual changes to the API at short notice are making them very hard
to work with. I can see that versioning can help with this, but only if
partners are given sufficient time to make the transition from one
version to the next. I believe 90 days would be sufficient for us, but
I suspect larger partners may need more notice of the new versions in
order to plan development work appropriately.
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
http://merjis.com/developers/adwords_api
We've updated our API to use v3, and added a handy command line tool
for exploring the KeywordToolService.
http://merjis.com/developers/adwords_api
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology -
A quick question. Is the Keyword Tool service "free" ? I don't see any
quota rate info for this new service:
http://www.google.com/support/adwordsapi/bin/answer.py?answer=21996
Best regards,
Peer Jakobsen
AdWordsAPIAdvisor a écrit :
>
> In addition, we have exposed the AdWords Keyword Tool via a new
> KeywordToolService
> (
So Google continue to ignore their largest partners who have planned
deployment and development schedules
and assume that partners will drop everything else they are doing in
order to comply with their latest edict.
This is another symptom of Google's growing arrogance and
self-importance which is contributing to the general swell of bad
feeling about Google.
I really hope that the API team will reconsider this deadline - the
continual changes to the API at short notice are making them very hard
to work with. I can see that versioning can help with this, but only if
partners are given sufficient time to make the transition from one
version to the next. I believe 90 days would be sufficient for us, but
I do have a more general concern about the continued use of betas, and
your belief that simply by labelling something as a beta, you no longer
need to follow accepted etiquette (e.g. sunset periods) about running
enterprise-class systems with multi-million pound (or dollar) partners.
Witness the furore over Microsoft's sunsetting of support for Windows
NT 4.0. While I appreciate that is a significantly different scenario,
as Google starts to deal with larger partners running business-critical
systems against your API, you start to acquire similar responsibilities
and obligations to support those partners, regardless of whether or not
you call your API a beta.
We have in fact now dropped all our other projects for the time being
in order to meet your deadline, as we simply cannot take the risk that
you will still disable the v2 API on March 27th. However, as I am sure
you can appreciate, the stakeholders of those other projects are not at
all happy.
Is there no developer in the API team, which have tried to make money
with selling software or an online service? No experiences?
The solution of the TOS & quota & linking could be a "user token"
instead of the developer token, see
http://groups.google.com/group/adwords-api/browse_thread/thread/8ad8ec6d228489f3/a04fc07b4799109d#a04fc07b4799109d
Thanks for reading,
Robert
Best regards,
Peer Jakobsen
Patrick Chanezon a écrit :
> Sorry about this missing information. The page has been updated now. yes it
> costs 25 quota units.
>
> P@
>
> On 2/27/06, Peer Jakobsen <peer.j...@gmail.com> wrote:
> >
> >
> > A quick question. Is the Keyword Tool service "free" ? I don't see any
> > quota rate info for this new service:
> >
> > http://www.google.com/support/adwordsapi/bin/answer.py?answer=21996
> >
> > Best regards,
> > Peer Jakobsen
> >
> > AdWordsAPIAdvisor a écrit :
> >
> > >
> > > In addition, we have exposed the AdWords Keyword Tool via a new
> > > KeywordToolService
> > > (http://www.google.com/apis/adwords/developer/KeywordToolService.html)
> > >
> >
> >
> >
> >
>
>
> --
> Patrick Chanezon, AdWords API evangelist
> http://blog.chanezon.com/
> http://www.google.com/apis/adwords/
>
> ------=_Part_7828_15637110.1141174977755
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> X-Google-AttachSize: 1298
>
> Sorry about this missing information. The page has been updated now. yes it costs 25 quota units.<br><br>P@<br><br><div><span class="gmail_quote">On 2/27/06, <b class="gmail_sendername">Peer Jakobsen</b> <<a href="mailto:peer.j...@gmail.com">
> peer.j...@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>A quick question. Is the Keyword Tool service "free" ? I don't see any
> <br>quota rate info for this new service:<br><br><a href="http://www.google.com/support/adwordsapi/bin/answer.py?answer=21996">http://www.google.com/support/adwordsapi/bin/answer.py?answer=21996</a><br><br>Best regards,<br>
> Peer Jakobsen<br><br>AdWordsAPIAdvisor a écrit :<br><br>><br>> In addition, we have exposed the AdWords Keyword Tool via a new<br>> KeywordToolService<br>> (<a href="http://www.google.com/apis/adwords/developer/KeywordToolService.html">
> <br><br></blockquote></div><br><br clear="all"><br>-- <br>Patrick Chanezon, AdWords API evangelist <br><a href="http://blog.chanezon.com/">http://blog.chanezon.com/</a><br><a href="http://www.google.com/apis/adwords/">http://www.google.com/apis/adwords/
> </a>
>
> ------=_Part_7828_15637110.1141174977755--
I'm getting this error on our CampaignService SOAP routines, that have
functioned perfectly for the last several months:
The request namespace is invalid for the service URL.
What is going on?
Regards,
Keith
I think this was a known bug. Previously the services didn't pay much
attention to the namespace URL given in the XML, but now they have to
contain the exact namespace, ending with .../v2/ or .../v3/
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com