AdWords API Re: Insert Keywords = UNEXPECTED INTERNAL API ERROR
I did some more research on this subject, and i think i found a possible reason for this error. It seems that i get more errors when AdGroups contain more than +/- 3000 keywords. When i create a new AdGroup, and fill this with Keywords, this process goes very fast until the number of keywords reaches +/- 3000. After the AdGroup reaches +/- 3000 keywords, the Unexpected Internal Api Error's keep increasing dramatically. Maybe this points you API Guys in the right direction tracking this bug down! :) On 30 nov, 21:02, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, Thanks for bringing this to our attention and providing detailed technical information. The core engineering team is aware of the issue and working on a fix. If you see this behavior on any other services please let us know. Best, - Eric Koleda, AdWords API Team On Nov 30, 12:40 pm, MaxT maxicttilb...@gmail.com wrote: Hi, I'm inserting batches of multiple keywords trough the AdGroupCriterion Service. Unfortunately the system is returning more and more UNEXPECTED INTERNAL API ERROR's I tried to add about 4 keywords, and 70% of this operations returned this error.. I read a lot about this error, and if i'm right it is not my fault. I tried inserting keywords in batches of 10/20/50/100 and all these different settings keeps returning there errors. Can someone please help me, as this is getting very annoying. My last 2 Request ID's: 57c98e01c76a54563e46e39cf073a03e 7c9c8e7fb08774d657b6cfb5733ee3b4 -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Re: EntityNotFound.INVALID_ID
Hi,
I've found the problem:
$AdGroupAdNEW-adGroupId = 570837;
We should not use around the ID, removing them made the script run
properly. I hope this will help ;)
On Dec 1, 10:09 am, prouted remindtestlive...@gmail.com wrote:
Hi,
I'm new using the Google Adwords API. I managed to create campains and
adgroups, and list them based on the examples provided with the latest
AdWords API PHP Client Library.
I have a problem when trying to create an adgroupad. Indeed, I always
get the message EntityNotFound.INVALID_ID @ operations
[0].adGroupAd.adGroupId; trigger:'AdGroupId: 2147483647'. The problem
here is that the adgroupid I use is not 2147483647.
Here is the code I user:
// Get AdWordsUser from credentials in ../auth.ini
// relative to the AdWordsUser.php file's directory.
$user = new AdWordsUser();
// Log SOAP XML request and response.
$user-LogDefaults();
// Get the AdGroupadsService.
$adService = $user-GetAdGroupAdService();
$AdGroupAdNEW = new AdGroupAd();
$AdGroupAdNEW-adGroupId = 570837;
$AdGroupAdNEW-status = 'PAUSED';
$ad = new TextAd();
$ad-url='http://www.test.com';
$ad-displayUrl='http://www.test.com';
$ad-headline='This is my title';
$ad-description1='This is my desc1.1';
$ad-description2='This is my desc2.1';
$AdGroupAdNEW-ad = $ad;
$operations = new AdGroupAdOperation($AdGroupAdNEW,NULL,'ADD');
$adgroupAdReturnValue = $adService-mutate($operations);
// Display new campaigns.
foreach ($adgroupAdReturnValue-value as $ad)
{
print 'New ad with name '.$ad-name.' and id '.$ad-id.' was created.
\n';
}
The adgroup I would like to use is using the ID 570837. My
authentification settings are the same as the ones used when creating
the campains and adgroup. What do I do wrong here ?
Many thanks in advance for your help !!
--
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-...@googlegroups.com.
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en.
AdWords API V2009 Reseller
I believe at this point it is impossible to use V2009 and V13 reseller in the same JVM ... AdWordsUser objects from both releases have the same package ( com.google.api.adwords.lib.AdWordsUser ) but when you try to retrieve V13 reseller services from the V2009 AdWordsUser, you receive ClassCastExceptions: java.lang.ClassCastException: com.google.api.adwords.v13.AccountServiceSoapBindingStub It seems the only way to use V2009 in the same JVM as V13 reseller is to re-package one or the other with different package names for AdWordsUser ( and potentially other classes ) What does Google recommend? -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Re: Bulgarian region codes
Hi, I am getting this data from the DefinedReportJob service, when selecting Geographic as a selectedReportType and the following selected columns: 'AdGroupId', 'Country', 'City', 'Region', 'Clicks', 'Impressions', I can also provide you with an example XML if you give an e-mail or FTP, as this is private data of our clients? On Nov 30, 9:27 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, From what service are you obtaining region codes like BG-01, etc? Best, - Eric Koleda, AdWords API Team On Nov 30, 5:22 am, veseo hernicet...@gmail.com wrote: Hello, have Bulgarian region codes been added to the Region Codes listings, as in the stats we are getting from Google, we have BG-01 and similar codes? If yes, why aren't they listed in the official Region Codes listings? Given the different codes and the actual cities that the stats come from, I can logically conclude which region corresponds to the code, but is that official? http://code.google.com/apis/adwords/docs/developer/adwords_api_region... -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Re: InfoService getUnitCount returns 0 for November 25 through 28
Today, I can see non-zero API units for all of the days! So something has been fixed. On Nov 30, 3:19 pm, j.e.frank j.e.fr...@gmail.com wrote: Thanks. Let me know if you need any additional info, such as the developer token and login that I am using. On Nov 30, 2:51 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, Thank you for bringing this to our attention. The core engineering team is looking into the issue. Best, - Eric Koleda, AdWords API Team On Nov 30, 11:16 am, j.e.frank j.e.fr...@gmail.com wrote: Every day I run a process to get my API usage. This returned 0 for 4 days, from November 25th through November 28th, and with smaller than normal numbers on the 24th and 29th. So far today it seems to be tracking normally again. I have double-checked that all of my processes that actually use API points have been running steadily, and even checked the AdWords change history to confirm that things have been working as expected. So I am puzzled as to why the usage reports 0 for those days. I thought it might have to do with the fact that I hadn't upgraded to v2009, but I just ran a test with the v2009 InfoService and got the same results. Is there any way for me to figure out what happened? -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Re: limitation on number of location entries
Is there an impact on the campaigns that I already uploaded more than 300 location entries before v13? On Nov 30, 8:30 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Andy, There is a limit of 300 positive geo targets per campaign, which has been in affect since v13:http://code.google.com/apis/adwords/docs/developer/GeoTarget.html. Best, - Eric Koleda, AdWords API Team On Nov 28, 1:44 pm, Andy Doan a...@iconvex.com wrote: Your answer is appreciated! Question: A few weeks ago, I was able to add over 1000s location entries (1000s different zips) to my campaigns. Last night, I was only be able to add max 300 location entries (either via API or Adwords Interface) Is this a limitation that is recently asserted by Google Adwords? Please advise! Thanks. Andy Doan iConvex, Inc. Find information about our services at www.iconvex.com w (714) 515-6620 | F (800) 360-2841 | a...@iconvex.com 17060 San Mateo St. Unit J. Fountain Valley, CA 92708 -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Re: v2009 API Is quota charged on SOAP Faults
Hi Fred, Thank you for the follow up information. The API units reported in the SOAP header are billed to your account, even if the request resulted in an error. In cases where the error was due to a problem on Google's servers and not user input the units will not be charged to your account. Because of the cost associated with errors, we recommend using the new validateOnly header to check your request for errors before you actually run them. A blog post on this header will be published later this week. Best, - Eric On Nov 30, 7:27 pm, fred dec...@decideinteractive.com wrote: I assume you want the SOAP from the delete call which had the dodgy operations header. Unfortunately I did not save the XML last week, but was getting that behaviour consistently on Friday (Thursday evening in the US) This week I am unable to reproduce this issue. When deleting keywords with an invalid adgroup ID it still gives an INTERNAL ERROR but now returns a response with headers of 1 operation and one 1 unit. Most of the time. On one occasion I did get a very different operation/unit count (but still only 1 unit per operation). The SOAP is below. I will keep an eye on it, and will save the XML if I do get the issue again. If you wanted other SOAP (e.g. the 15 quota per invalid keyword in an Add operation) then I can still reproduce that. Do we actually get charged the quota reported in the headers of SOAP Faults? 1201-112153 W P4PGoogle.pm/2241 ERROR REQUEST: POSThttps://adwords.google.com/api/adwords/cm/v200909/AdGroupCriterionSer... HTTP/1.1 Accept: text/xml Accept: multipart/* Content-Length: 2032 Content-Type: text/xml; charset=utf-8 SOAPAction: https://adwords.google.com/api/adwords/cm/v200909#mutate; ?xml version=1.0 encoding=UTF-8? SOAP-ENV:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema- instance xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; SOAP- ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; SOAP-ENV:Header RequestHeader xmlns=https://adwords.google.com/api/adwords/cm/ v200909 SOAP-ENC:arrayType=xsd:string[4] authToken xsi:type=xsd:stringsomething1/authToken useragent xsi:type=xsd:stringsomething2/useragent developerToken xsi:type=xsd:stringsomething3/developerToken applicationToken xsi:type=xsd:stringsomething4/applicationToken /RequestHeader /SOAP-ENV:Header SOAP-ENV:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v200909; operations operatorREMOVE/operator operand xsi:type=BiddableAdGroupCriterion bids xsi:type=ManualCPCAdGroupCriterionBids SOAP- ENC:arrayType=xsd:anyType[1] maxCpc amount microAmount xsi:nil=true/ /amount /maxCpc /bids adGroupId3690779520/adGroupId userStatus xsi:nil=true/ criterion xsi:type=Keyword text xsi:nil=true/ id14899356282/id matchTypeBROAD/matchType /criterion destinationUrl xsi:nil=true/ /operand /operations operations operatorREMOVE/operator operand xsi:type=BiddableAdGroupCriterion bids xsi:type=ManualCPCAdGroupCriterionBids SOAP- ENC:arrayType=xsd:anyType[1] maxCpc amount microAmount xsi:nil=true/ /amount /maxCpc /bids adGroupId3690779520/adGroupId userStatus xsi:nil=true/ criterion xsi:type=Keyword text xsi:nil=true/ id14899572282/id matchTypeBROAD/matchType /criterion destinationUrl xsi:nil=true/ /operand /operations /mutate /SOAP-ENV:Body /SOAP-ENV:Envelope 1201-112153 W P4PGoogle.pm/2243 ERROR RESPONSE: HTTP/1.1 200 OK Cache-Control: private, max-age=0 Connection: close Date: Tue, 01 Dec 2009 00:21:53 GMT Server: GFE/2.0 Content-Type: text/xml; charset=UTF-8 Expires: Tue, 01 Dec 2009 00:21:53 GMT Client-Date: Tue, 01 Dec 2009 00:21:53 GMT Client-Response-Num: 1 Client-SSL-Cert-Issuer: /C=US/O=Equifax/OU=Equifax Secure Certificate Authority Client-SSL-Cert-Subject: /C=US/ST=California/L=Mountain View/O=Google Inc./CN=adwords.google.com Client-SSL-Cipher: AES256-SHA Client-SSL-Warning: Peer certificate not verified Client-Transfer-Encoding: chunked X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN X-XSS-Protection: 0 soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Header ResponseHeader xmlns=https://adwords.google.com/api/adwords/cm/ v200909 requestId5e72e19c21b7d51ee7e7304b27770e16/requestId operations787/operations responseTime172/responseTime units787/units /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringInternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ / faultstring detail ApiExceptionFault xmlns=https://adwords.google.com/api/adwords/cm/ v200909 messageInternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ /message ApplicationException.TypeApiException/ApplicationException.Type errors xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:type=InternalApiError fieldPath /fieldPath trigger /trigger
AdWords API Re: InfoService getUnitCount returns 0 for November 25 through 28
Hi, Yes, the problem has been resolved and all API usage should be returned correctly now. Let us know if you see this problem again. Best, - Eric On Dec 1, 11:43 am, j.e.frank j.e.fr...@gmail.com wrote: Today, I can see non-zero API units for all of the days! So something has been fixed. On Nov 30, 3:19 pm, j.e.frank j.e.fr...@gmail.com wrote: Thanks. Let me know if you need any additional info, such as the developer token and login that I am using. On Nov 30, 2:51 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi, Thank you for bringing this to our attention. The core engineering team is looking into the issue. Best, - Eric Koleda, AdWords API Team On Nov 30, 11:16 am, j.e.frank j.e.fr...@gmail.com wrote: Every day I run a process to get my API usage. This returned 0 for 4 days, from November 25th through November 28th, and with smaller than normal numbers on the 24th and 29th. So far today it seems to be tracking normally again. I have double-checked that all of my processes that actually use API points have been running steadily, and even checked the AdWords change history to confirm that things have been working as expected. So I am puzzled as to why the usage reports 0 for those days. I thought it might have to do with the fact that I hadn't upgraded to v2009, but I just ran a test with the v2009 InfoService and got the same results. Is there any way for me to figure out what happened? -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
AdWords API Re: v2009 API Is quota charged on SOAP Faults
Thanks for following this up Eric. I will make sure we account for quota on faults to. When you say where the error was due to a problem on Google's servers does that mean whenever the error is internal error? In the example I posted (reported as 787 quota) it was reported as an INTERNAL_API_ERROR, but was due to me deliberately using a bad adgroup ID. Is this considered a server error or input error? i.e. Would this be charged or not? Interstingly most of the time it was only 1 quota, but when I added a few more 0's to the invalid adgroup id it gave the 787 On Dec 2, 3:53 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Fred, Thank you for the follow up information. The API units reported in the SOAP header are billed to your account, even if the request resulted in an error. In cases where the error was due to a problem on Google's servers and not user input the units will not be charged to your account. Because of the cost associated with errors, we recommend using the new validateOnly header to check your request for errors before you actually run them. A blog post on this header will be published later this week. Best, - Eric On Nov 30, 7:27 pm, fred dec...@decideinteractive.com wrote: I assume you want the SOAP from the delete call which had the dodgy operations header. Unfortunately I did not save the XML last week, but was getting that behaviour consistently on Friday (Thursday evening in the US) This week I am unable to reproduce this issue. When deleting keywords with an invalid adgroup ID it still gives an INTERNAL ERROR but now returns a response with headers of 1 operation and one 1 unit. Most of the time. On one occasion I did get a very different operation/unit count (but still only 1 unit per operation). The SOAP is below. I will keep an eye on it, and will save the XML if I do get the issue again. If you wanted other SOAP (e.g. the 15 quota per invalid keyword in an Add operation) then I can still reproduce that. Do we actually get charged the quota reported in the headers of SOAP Faults? 1201-112153 W P4PGoogle.pm/2241 ERROR REQUEST: POSThttps://adwords.google.com/api/adwords/cm/v200909/AdGroupCriterionSer... HTTP/1.1 Accept: text/xml Accept: multipart/* Content-Length: 2032 Content-Type: text/xml; charset=utf-8 SOAPAction: https://adwords.google.com/api/adwords/cm/v200909#mutate; ?xml version=1.0 encoding=UTF-8? SOAP-ENV:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema- instance xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; SOAP- ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; SOAP-ENV:Header RequestHeader xmlns=https://adwords.google.com/api/adwords/cm/ v200909 SOAP-ENC:arrayType=xsd:string[4] authToken xsi:type=xsd:stringsomething1/authToken useragent xsi:type=xsd:stringsomething2/useragent developerToken xsi:type=xsd:stringsomething3/developerToken applicationToken xsi:type=xsd:stringsomething4/applicationToken /RequestHeader /SOAP-ENV:Header SOAP-ENV:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v200909; operations operatorREMOVE/operator operand xsi:type=BiddableAdGroupCriterion bids xsi:type=ManualCPCAdGroupCriterionBids SOAP- ENC:arrayType=xsd:anyType[1] maxCpc amount microAmount xsi:nil=true/ /amount /maxCpc /bids adGroupId3690779520/adGroupId userStatus xsi:nil=true/ criterion xsi:type=Keyword text xsi:nil=true/ id14899356282/id matchTypeBROAD/matchType /criterion destinationUrl xsi:nil=true/ /operand /operations operations operatorREMOVE/operator operand xsi:type=BiddableAdGroupCriterion bids xsi:type=ManualCPCAdGroupCriterionBids SOAP- ENC:arrayType=xsd:anyType[1] maxCpc amount microAmount xsi:nil=true/ /amount /maxCpc /bids adGroupId3690779520/adGroupId userStatus xsi:nil=true/ criterion xsi:type=Keyword text xsi:nil=true/ id14899572282/id matchTypeBROAD/matchType /criterion destinationUrl xsi:nil=true/ /operand /operations /mutate /SOAP-ENV:Body /SOAP-ENV:Envelope 1201-112153 W P4PGoogle.pm/2243 ERROR RESPONSE: HTTP/1.1 200 OK Cache-Control: private, max-age=0 Connection: close Date: Tue, 01 Dec 2009 00:21:53 GMT Server: GFE/2.0 Content-Type: text/xml; charset=UTF-8 Expires: Tue, 01 Dec 2009 00:21:53 GMT Client-Date: Tue, 01 Dec 2009 00:21:53 GMT Client-Response-Num: 1 Client-SSL-Cert-Issuer: /C=US/O=Equifax/OU=Equifax Secure Certificate Authority Client-SSL-Cert-Subject: /C=US/ST=California/L=Mountain View/O=Google Inc./CN=adwords.google.com Client-SSL-Cipher: AES256-SHA Client-SSL-Warning: Peer certificate not verified Client-Transfer-Encoding: chunked X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN X-XSS-Protection: 0 soap:Envelope
AdWords API Re: PHP Client Library for v2009, EntityNotFound.INVALID_ID @ selector ERROR
Thanks heaps Eric. Time to start digging through very old emails. On Dec 2, 4:01 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Fred, That's correct, you must use the MCC account that owns the developer token for all requests. This is the only service where that specific user is required. Best, - Eric On Dec 1, 2:20 am, fred dec...@decideinteractive.com wrote: Hi, Very useful thread, thanks for that. Just want to confirm I understand this correctly. Does this mean that you can only call InfoService::get if the username you use for authorisation is the same user who owns the developerToken? Are there any other situations in v2009 where the username and devToken have to match? (either directly or via an MCC relationship). As I understand it there were no such rules in v1 through v13 Thanks On Nov 19, 6:11 am, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Eugene, Great, I'm glad to hear that it's working now. I'm working with the documentation team to make the authentication requirements clearer. The forum is the best way to get help with the AdWords API, and we try to respond to questions at least twice a day. Best, - Eric On Nov 18, 1:24 pm, Eugene popov...@aheadworks.com wrote: Eric, I found email and password associated with my token and it works! And yes it works only with MCC account email/password. Thank you very much! Is there any way to contact you directly to get help faster? We are migrating our apps from apility (v13) to PHP Client Library for AdWords API v2009. So I think we will have more problems, questions... Thanks again.- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - -- 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-...@googlegroups.com. To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
