Hi, Okay, I'll do it for now.
Thanks for the commitment, Max On Nov 25, 7:52 pm, AdWords API Advisor <[EMAIL PROTECTED]> wrote: > Hello, > > After some investigation, it was determined that there are some > scenarios in which the keyword variations service will effectively > returns nothing. (I can't get into all the situations in which this > might occur, but there are some scenarios in which "adult" keywords > could trigger it, though it's also possible for other types of > keywords.) The AdWords API erroneously thinks that it failed to talk > to the keyword variation backend service when this occurs; hence the > "There was an error contacting the keyword variation server." SOAP > fault. > > The behavior of the keyword variations service is not going to > change, but there are plans to make the the AdWords API deal with this > scenario in a more graceful manner and either return a more accurate > SOAP fault or just return a normal response with an empty array of > variations. In the meantime, you should interpret the existing SOAP > fault as such. > > Cheers, > -Jeff Posnick, AdWords API Team > > On Nov 21, 12:05 pm, Max <[EMAIL PROTECTED]> wrote: > > > Really... I had not seen. > > > thank you, > > Max > > > On Nov 21, 2:32 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > wrote: > > > > Hello Max, > > > > Please see an earlier thread about that: > > > > http://groups.google.com/group/adwords-api/browse_thread/thread/0cf23... > > > > Cheers, > > > -Jeff Posnick, AdWords API Team > > > > On Nov 21, 6:53 am, Max <[EMAIL PROTECTED]> wrote: > > > > > Hi Jeff, > > > > > Yes, by the way, I continued doing some tests and apparently realized > > > > that the API is not respecting the parameter type(match) of the word, > > > > and sometimes the numbers do not correspond with volume numbers for > > > > the web interface. The same thing happens to you? > > > > > Thanks for your time, > > > > Max > > > > > On Nov 19, 6:44 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > > > wrote: > > > > > > Hello Max, > > > > > > The previously-filed bug report was for keywords that were definitely > > > > > not "adult" in nature. The keywords that triggered the problem in that > > > > > case now function properly, so this might be a transitory issue with > > > > > the keyword suggestion service backend--but that's just speculation on > > > > > my part. > > > > > > I'll let you know what information I can get from the engineering > > > > > team. > > > > > > Cheers, > > > > > -Jeff Posnick, AdWords API Team > > > > > > On Nov 19, 3:10 pm, Max <[EMAIL PROTECTED]> wrote: > > > > > > > Exactly, I have tested the keyword "pornographic movie" in the web > > > > > > interface, with the "Includeadultcontent in my keyword results" > > > > > > option unchecked. The keyword variations showed up normally. > > > > > > Probably > > > > > > these keyword variations are not classified asadultcontent. > > > > > > I also have noticed that other keyword variations that areadult > > > > > > keywords are not classified asadultcontent. > > > > > > That's why I still think that the error was related toadultkeywords. > > > > > > Also, I only had this problem withadultkeywords. Are there any cases > > > > > > that are not envolved withadultcontent? > > > > > > > Tks, > > > > > > Max > > > > > > > On Nov 19, 5:00 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > > > > > wrote: > > > > > > > > Just a quick update: this may not in fact be triggered by alladult > > > > > > > content (for instance, "pornographic movie" will return > > > > > > > variations as > > > > > > > expected). > > > > > > > > I came across bug already on record related to a very similar > > > > > > > error > > > > > > > with getKeywordVariations() and specific keywords, so this looks > > > > > > > like > > > > > > > it might be another example of that. I'll update the thread when > > > > > > > I get > > > > > > > some word from the engineering team as to possible causes. > > > > > > > > Cheers, > > > > > > > -Jeff Posnick, AdWords API Team > > > > > > > > On Nov 19, 1:32 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > > > > > > wrote: > > > > > > > > > Hello Max, > > > > > > > > > Yes, it looks like passing in "adult" keywords to the > > > > > > > > getKewordVariations() methods does lead to this exception. I'll > > > > > > > > find > > > > > > > > out from the engineering team whether this is intentional (in > > > > > > > > which > > > > > > > > case we'll update the documentation accordingly). > > > > > > > > > Cheers, > > > > > > > > -Jeff Posnick, AdWords API Team > > > > > > > > > On Nov 18, 4:07 pm, Max <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi folks, > > > > > > > > > > Recently, the KeywordTool was updated in both places, web > > > > > > > > > interface > > > > > > > > > and API. I noticed that the web interface now has > > > > > > > > > theadultcontent > > > > > > > > > filter and in the API there are two new fields: average > > > > > > > > > search volume > > > > > > > > > in recent months and last month. All the improvments are > > > > > > > > > great ! > > > > > > > > > > But I think it is strange that when trying to submit a word > > > > > > > > > that is > > > > > > > > > related toadultcontent, the API returns the following error > > > > > > > > > message: > > > > > > > > > > Request: > > > > > > > > > > POST /api/adwords/v13/KeywordToolService HTTP/1.0 > > > > > > > > > Host: adwords.google.com > > > > > > > > > User-Agent: NuSOAP/0.7.3 (1.114) > > > > > > > > > Content-Type: text/xml; charset=UTF-8 > > > > > > > > > SOAPAction: "" > > > > > > > > > Content-Length: 1059 > > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > > > > > > <SOAP-ENV:Envelope > > > > > > > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/ > > > > > > > > > envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > > > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > > > > > > > > xmlns:SOAP- > > > > > > > > > ENC="http://schemas.xmlsoap.org/soap/encoding/"; > > > > > > > > > xmlns:ns7020="http:// > > > > > > > > > tempuri.org"> > > > > > > > > > <SOAP-ENV:Header> > > > > > > > > > <email>INSERT_LOGIN_EMAIL_HERE</email> > > > > > > > > > <password>INSERT_PASSWORD_HERE</password> > > > > > > > > > > > > > > > > > > <clientEmail>INSERT_CLIENT_LOGIN_EMAIL_HERE</clientEmail> > > > > > > > > > <useragent>INSERT_COMPANY_NAME</useragent> > > > > > > > > > > > > > > > > > > <developerToken>INSERT_DEVELOPER_TOKEN_HERE</developerToken> > > > > > > > > > > > > > > > > > > <applicationToken>INSERT_APPLICATION_TOKEN_HERE</applicationToken> > > > > > > > > > </SOAP-ENV:Header> > > > > > > > > > <SOAP-ENV:Body> > > > > > > > > > <getKeywordVariations> > > > > > > > > > <seedKeywords> > > > > > > > > > <negative>false</negative> > > > > > > > > > <text>porn movie</text> > > > > > > > > > <type>Exact</type> > > > > > > > > > </seedKeywords> > > > > > > > > > <useSynonyms>true</useSynonyms> > > > > > > > > > <languages>es</languages> > > > > > > > > > <countries>US</countries> > > > > > > > > > </getKeywordVariations> > > > > > > > > > </SOAP-ENV:Body> > > > > > > > > > </SOAP-ENV:Envelope> > > > > > > > > > > Response: > > > > > > > > > > HTTP/1.1 500 Internal Server Error > > > > > > > > > Content-Type: text/xml; charset=utf-8 > > > > > > > > > Transfer-Encoding: chunked > > > > > > > > > Date: Tue, 18 Nov 2008 20:29:49 GMT > > > > > > > > > X-Content-Type-Options: nosniff > > > > > > > > > Expires: Tue, 18 Nov 2008 20:29:49 GMT > > > > > > > > > Cache-Control: private, max-age=0 > > > > > > > > > Server: GFE/1.3 > > > > > > > > > Connection: Close > > > > > > > > > > <soapenv:Envelope > > > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/ > > > > > > > > > envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > > > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > <soapenv:Header> > > > > > > > > > <responseTime > > > > > > > > > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/ > > > > > > > > > next" soapenv:mustUnderstand="0" > > > > > > > > > xmlns="https://adwords.google.com/api/ > > > > > > > > > adwords/v13">622</responseTime> > > > > > > > > > <operations > > > > > > > > > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/ > > > > > > > > > next" soapenv:mustUnderstand="0" > > > > > > > > > xmlns="https://adwords.google.com/api/ > > > > > > > > > adwords/v13">0</operations> > > > > > > > > > <units > > > > > > > > > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; > > > > > > > > > soapenv:mustUnderstand="0" > > > > > > > > > xmlns="https://adwords.google.com/api/ > > > > > > > > > adwords/v13">0</units> > > > > > > > > > <requestId > > > > > > > > > soapenv:actor="http://schemas.xmlsoap.org/soap/actor/ > > > > > > > > > next" soapenv:mustUnderstand="0" > > > > > > > > > xmlns="https://adwords.google.com/api/ > > > > > > > > > adwords/v13">76358a9f559291b6ac4286bb7b9b5aca</requestId> > > > > > > > > > </soapenv:Header> > > > > > > > > > <soapenv:Body> > > > > > > > > > <soapenv:Fault> > > > > > > > > > > > > > > > > > > <faultcode>soapenv:Server.generalException</faultcode> > > > > > > > > > <faultstring>There was an error > > > > > > > > > contacting the keyword variation > > > > > > > > > server.</faultstring> > > > > > > > > > <detail> > > > > > > > > > <ns1:fault > > > > > > > > > xmlns:ns1="https://adwords.google.com/api/adwords/v13";> > > > > > > > > > <ns1:code>95</ns1:code> > > > > > > > > > <ns1:message>There was an > > > > > > > > > error contacting the keyword variation > > > > > > > > > server.</ns1:message> > > > > > > > > > </ns1:fault> > > > > > > > > > > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
