Re: TrafficEstimatorService xml
Hi Manuel, I have been able to replicate the issue with credit card / EXACT. PHRASE and BROAD return results, but EXACT is oddly all 0's while the Traffic Estimator web interface does return some values. I'll follow up with the core engineering team to see if we can determine why this specific keyword is affected. Do you have any other example keywords that show the same behavior? Best, - Eric On Nov 9, 10:25 pm, manuel manuel_pa...@sapo.pt wrote: Yes, targeting options are the same. (Language and Country) Nothing explains a zero. Can you please check it out? Are there forbidden words? On Nov 9, 8:59 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Please remember to check your targeting options and ensure they are the same between the API and the Traffic Estimator UI. The Keyword Tool uses a different system and may return different results. Also, a video I made on the new v201008 TrafficEstimatorService is now available: http://www.youtube.com/watch?v=tR-YSrmszzw Best, - Eric On Nov 9, 1:18 pm, manuel manuel_pa...@sapo.pt wrote: Thanks Brendan but... Why is credit card returning $0 CPC from the API? And why $12.13 on the Keyword Tool and $10.22 on the Traffic Estimator? All set to English and US Thanks, Manuel On Nov 9, 3:21 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Below is a sample request to the v201008 TES. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/ envelope/ xmlns:o=https://adwords.google.com/api/adwords/o/v201008; xmlns:cm=https://adwords.google.com/api/adwords/cm/v201008; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header o:RequestHeader cm:authToken.../cm:authToken cm:clientEmail.../cm:clientEmail cm:developerToken.../cm:developerToken cm:userAgent.../cm:userAgent /o:RequestHeader /soapenv:Header soapenv:Body o:get o:selector o:campaignEstimateRequests o:adGroupEstimateRequests o:keywordEstimateRequests o:keyword cm:textdigital camera/cm:text cm:matchTypeEXACT/cm:matchType /o:keyword /o:keywordEstimateRequests o:maxCpc cm:microAmount100/cm:microAmount /o:maxCpc /o:adGroupEstimateRequests o:targets xsi:type=cm:CountryTarget cm:countryCodeUS/cm:countryCode /o:targets o:targets xsi:type=cm:LanguageTarget cm:languageCodeen/cm:languageCode /o:targets /o:campaignEstimateRequests /o:selector /o:get /soapenv:Body /soapenv:Envelope Brendan, You are sending a v13 TES request to the v201008 service. The XML format changed significantly between versions, so the same XML cannot be reused. More information about the new service is available here: http://adwordsapi.blogspot.com/2010/09/discover-v201008-trafficestima... Best, - Eric Koleda, AdWords API Team On Nov 8, 2:48 pm, brendangorm...@skinwest.com brendangorm...@skinwest.com wrote: Add me to the list. I've been using estimateKeywordList and it's giving me an exception: Fault occurred while processing. I'm posting it to this URL:https://adwords-sandbox.google.com/api/adwords/cm/v201008/CampaignSer... This is the same exact example from googles API website, except that I've inserted my credentials. ?xml version=1.0? env:Envelope xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; env:Header applicationTokenDQ--Q/applicationToken passwordXXX/password emailx...@example.com/email clientEmailclient_1+x...@example.com/clientEmail useragentnone/useragent developerTokenxx...@example.com++usd/developerToken /env:Header env:Body estimateKeywordList keywordRequests maxCpc10/maxCpc textmars cruise/text typeBroad/type /keywordRequests /estimateKeywordList /env:Body /env:Envelope The error is Fault occurred while processing If I change the password to BAD PASSWORD I get the same error, (not something to the effect of invalid credentials) this tells me the fault is occuring prior to authentication, if that helps. No error codes or anything that'd indicate what the problem is. It's really got me
Re: TrafficEstimatorService xml
Thanks. It was the first word that come to mind. I am sure there must be others, maybe in the top cpc values? On Nov 10, 11:41 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, I have been able to replicate the issue with credit card / EXACT. PHRASE and BROAD return results, but EXACT is oddly all 0's while the Traffic Estimator web interface does return some values. I'll follow up with the core engineering team to see if we can determine why this specific keyword is affected. Do you have any other example keywords that show the same behavior? Best, - Eric On Nov 9, 10:25 pm, manuel manuel_pa...@sapo.pt wrote: Yes, targeting options are the same. (Language and Country) Nothing explains a zero. Can you please check it out? Are there forbidden words? On Nov 9, 8:59 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Please remember to check your targeting options and ensure they are the same between the API and the Traffic Estimator UI. The Keyword Tool uses a different system and may return different results. Also, a video I made on the new v201008 TrafficEstimatorService is now available: http://www.youtube.com/watch?v=tR-YSrmszzw Best, - Eric On Nov 9, 1:18 pm, manuel manuel_pa...@sapo.pt wrote: Thanks Brendan but... Why is credit card returning $0 CPC from the API? And why $12.13 on the Keyword Tool and $10.22 on the Traffic Estimator? All set to English and US Thanks, Manuel On Nov 9, 3:21 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Below is a sample request to the v201008 TES. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/ envelope/ xmlns:o=https://adwords.google.com/api/adwords/o/v201008; xmlns:cm=https://adwords.google.com/api/adwords/cm/v201008; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header o:RequestHeader cm:authToken.../cm:authToken cm:clientEmail.../cm:clientEmail cm:developerToken.../cm:developerToken cm:userAgent.../cm:userAgent /o:RequestHeader /soapenv:Header soapenv:Body o:get o:selector o:campaignEstimateRequests o:adGroupEstimateRequests o:keywordEstimateRequests o:keyword cm:textdigital camera/cm:text cm:matchTypeEXACT/cm:matchType /o:keyword /o:keywordEstimateRequests o:maxCpc cm:microAmount100/cm:microAmount /o:maxCpc /o:adGroupEstimateRequests o:targets xsi:type=cm:CountryTarget cm:countryCodeUS/cm:countryCode /o:targets o:targets xsi:type=cm:LanguageTarget cm:languageCodeen/cm:languageCode /o:targets /o:campaignEstimateRequests /o:selector /o:get /soapenv:Body /soapenv:Envelope Brendan, You are sending a v13 TES request to the v201008 service. The XML format changed significantly between versions, so the same XML cannot be reused. More information about the new service is available here: http://adwordsapi.blogspot.com/2010/09/discover-v201008-trafficestima... Best, - Eric Koleda, AdWords API Team On Nov 8, 2:48 pm, brendangorm...@skinwest.com brendangorm...@skinwest.com wrote: Add me to the list. I've been using estimateKeywordList and it's giving me an exception: Fault occurred while processing. I'm posting it to this URL:https://adwords-sandbox.google.com/api/adwords/cm/v201008/CampaignSer... This is the same exact example from googles API website, except that I've inserted my credentials. ?xml version=1.0? env:Envelope xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; env:Header applicationTokenDQ--Q/applicationToken passwordXXX/password emailx...@example.com/email clientEmailclient_1+x...@example.com/clientEmail useragentnone/useragent developerTokenxx...@example.com++usd/developerToken /env:Header env:Body estimateKeywordList keywordRequests maxCpc10/maxCpc textmars cruise/text typeBroad/type /keywordRequests /estimateKeywordList /env:Body /env:Envelope The error is Fault occurred while processing If I
Re: TrafficEstimatorService xml
Hi Manuel, Below is a sample request to the v201008 TES. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/ envelope/ xmlns:o=https://adwords.google.com/api/adwords/o/v201008; xmlns:cm=https://adwords.google.com/api/adwords/cm/v201008; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header o:RequestHeader cm:authToken.../cm:authToken cm:clientEmail.../cm:clientEmail cm:developerToken.../cm:developerToken cm:userAgent.../cm:userAgent /o:RequestHeader /soapenv:Header soapenv:Body o:get o:selector o:campaignEstimateRequests o:adGroupEstimateRequests o:keywordEstimateRequests o:keyword cm:textdigital camera/cm:text cm:matchTypeEXACT/cm:matchType /o:keyword /o:keywordEstimateRequests o:maxCpc cm:microAmount100/cm:microAmount /o:maxCpc /o:adGroupEstimateRequests o:targets xsi:type=cm:CountryTarget cm:countryCodeUS/cm:countryCode /o:targets o:targets xsi:type=cm:LanguageTarget cm:languageCodeen/cm:languageCode /o:targets /o:campaignEstimateRequests /o:selector /o:get /soapenv:Body /soapenv:Envelope Brendan, You are sending a v13 TES request to the v201008 service. The XML format changed significantly between versions, so the same XML cannot be reused. More information about the new service is available here: http://adwordsapi.blogspot.com/2010/09/discover-v201008-trafficestimatorservic.html Best, - Eric Koleda, AdWords API Team On Nov 8, 2:48 pm, brendangorm...@skinwest.com brendangorm...@skinwest.com wrote: Add me to the list. I've been using estimateKeywordList and it's giving me an exception: Fault occurred while processing. I'm posting it to this URL:https://adwords-sandbox.google.com/api/adwords/cm/v201008/CampaignSer... This is the same exact example from googles API website, except that I've inserted my credentials. ?xml version=1.0? env:Envelope xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; env:Header applicationTokenDQ--Q/applicationToken passwordXXX/password emailx...@example.com/email clientEmailclient_1+x...@example.com/clientEmail useragentnone/useragent developerTokenxx...@example.com++usd/developerToken /env:Header env:Body estimateKeywordList keywordRequests maxCpc10/maxCpc textmars cruise/text typeBroad/type /keywordRequests /estimateKeywordList /env:Body /env:Envelope The error is Fault occurred while processing If I change the password to BAD PASSWORD I get the same error, (not something to the effect of invalid credentials) this tells me the fault is occuring prior to authentication, if that helps. No error codes or anything that'd indicate what the problem is. It's really got me baffled, is there some way I can turn on more details for the errors? On Nov 4, 11:37 am, manuel manuel_pa...@sapo.pt wrote:q Can someone please post an example of a working xml request to the updated v201008 TrafficEstimatorService? Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: TrafficEstimatorService xml
Thanks Brendan but... Why is credit card returning $0 CPC from the API? And why $12.13 on the Keyword Tool and $10.22 on the Traffic Estimator? All set to English and US Thanks, Manuel On Nov 9, 3:21 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Below is a sample request to the v201008 TES. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/ envelope/ xmlns:o=https://adwords.google.com/api/adwords/o/v201008; xmlns:cm=https://adwords.google.com/api/adwords/cm/v201008; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header o:RequestHeader cm:authToken.../cm:authToken cm:clientEmail.../cm:clientEmail cm:developerToken.../cm:developerToken cm:userAgent.../cm:userAgent /o:RequestHeader /soapenv:Header soapenv:Body o:get o:selector o:campaignEstimateRequests o:adGroupEstimateRequests o:keywordEstimateRequests o:keyword cm:textdigital camera/cm:text cm:matchTypeEXACT/cm:matchType /o:keyword /o:keywordEstimateRequests o:maxCpc cm:microAmount100/cm:microAmount /o:maxCpc /o:adGroupEstimateRequests o:targets xsi:type=cm:CountryTarget cm:countryCodeUS/cm:countryCode /o:targets o:targets xsi:type=cm:LanguageTarget cm:languageCodeen/cm:languageCode /o:targets /o:campaignEstimateRequests /o:selector /o:get /soapenv:Body /soapenv:Envelope Brendan, You are sending a v13 TES request to the v201008 service. The XML format changed significantly between versions, so the same XML cannot be reused. More information about the new service is available here: http://adwordsapi.blogspot.com/2010/09/discover-v201008-trafficestima... Best, - Eric Koleda, AdWords API Team On Nov 8, 2:48 pm, brendangorm...@skinwest.com brendangorm...@skinwest.com wrote: Add me to the list. I've been using estimateKeywordList and it's giving me an exception: Fault occurred while processing. I'm posting it to this URL:https://adwords-sandbox.google.com/api/adwords/cm/v201008/CampaignSer... This is the same exact example from googles API website, except that I've inserted my credentials. ?xml version=1.0? env:Envelope xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; env:Header applicationTokenDQ--Q/applicationToken passwordXXX/password emailx...@example.com/email clientEmailclient_1+x...@example.com/clientEmail useragentnone/useragent developerTokenxx...@example.com++usd/developerToken /env:Header env:Body estimateKeywordList keywordRequests maxCpc10/maxCpc textmars cruise/text typeBroad/type /keywordRequests /estimateKeywordList /env:Body /env:Envelope The error is Fault occurred while processing If I change the password to BAD PASSWORD I get the same error, (not something to the effect of invalid credentials) this tells me the fault is occuring prior to authentication, if that helps. No error codes or anything that'd indicate what the problem is. It's really got me baffled, is there some way I can turn on more details for the errors? On Nov 4, 11:37 am, manuel manuel_pa...@sapo.pt wrote:q Can someone please post an example of a working xml request to the updated v201008 TrafficEstimatorService? Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: TrafficEstimatorService xml
Hi Manuel, Please remember to check your targeting options and ensure they are the same between the API and the Traffic Estimator UI. The Keyword Tool uses a different system and may return different results. Also, a video I made on the new v201008 TrafficEstimatorService is now available: http://www.youtube.com/watch?v=tR-YSrmszzw Best, - Eric On Nov 9, 1:18 pm, manuel manuel_pa...@sapo.pt wrote: Thanks Brendan but... Why is credit card returning $0 CPC from the API? And why $12.13 on the Keyword Tool and $10.22 on the Traffic Estimator? All set to English and US Thanks, Manuel On Nov 9, 3:21 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Below is a sample request to the v201008 TES. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/ envelope/ xmlns:o=https://adwords.google.com/api/adwords/o/v201008; xmlns:cm=https://adwords.google.com/api/adwords/cm/v201008; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header o:RequestHeader cm:authToken.../cm:authToken cm:clientEmail.../cm:clientEmail cm:developerToken.../cm:developerToken cm:userAgent.../cm:userAgent /o:RequestHeader /soapenv:Header soapenv:Body o:get o:selector o:campaignEstimateRequests o:adGroupEstimateRequests o:keywordEstimateRequests o:keyword cm:textdigital camera/cm:text cm:matchTypeEXACT/cm:matchType /o:keyword /o:keywordEstimateRequests o:maxCpc cm:microAmount100/cm:microAmount /o:maxCpc /o:adGroupEstimateRequests o:targets xsi:type=cm:CountryTarget cm:countryCodeUS/cm:countryCode /o:targets o:targets xsi:type=cm:LanguageTarget cm:languageCodeen/cm:languageCode /o:targets /o:campaignEstimateRequests /o:selector /o:get /soapenv:Body /soapenv:Envelope Brendan, You are sending a v13 TES request to the v201008 service. The XML format changed significantly between versions, so the same XML cannot be reused. More information about the new service is available here: http://adwordsapi.blogspot.com/2010/09/discover-v201008-trafficestima... Best, - Eric Koleda, AdWords API Team On Nov 8, 2:48 pm, brendangorm...@skinwest.com brendangorm...@skinwest.com wrote: Add me to the list. I've been using estimateKeywordList and it's giving me an exception: Fault occurred while processing. I'm posting it to this URL:https://adwords-sandbox.google.com/api/adwords/cm/v201008/CampaignSer... This is the same exact example from googles API website, except that I've inserted my credentials. ?xml version=1.0? env:Envelope xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; env:Header applicationTokenDQ--Q/applicationToken passwordXXX/password emailx...@example.com/email clientEmailclient_1+x...@example.com/clientEmail useragentnone/useragent developerTokenxx...@example.com++usd/developerToken /env:Header env:Body estimateKeywordList keywordRequests maxCpc10/maxCpc textmars cruise/text typeBroad/type /keywordRequests /estimateKeywordList /env:Body /env:Envelope The error is Fault occurred while processing If I change the password to BAD PASSWORD I get the same error, (not something to the effect of invalid credentials) this tells me the fault is occuring prior to authentication, if that helps. No error codes or anything that'd indicate what the problem is. It's really got me baffled, is there some way I can turn on more details for the errors? On Nov 4, 11:37 am, manuel manuel_pa...@sapo.pt wrote:q Can someone please post an example of a working xml request to the updated v201008 TrafficEstimatorService? Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: TrafficEstimatorService xml
Yes, targeting options are the same. (Language and Country) Nothing explains a zero. Can you please check it out? Are there forbidden words? On Nov 9, 8:59 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Please remember to check your targeting options and ensure they are the same between the API and the Traffic Estimator UI. The Keyword Tool uses a different system and may return different results. Also, a video I made on the new v201008 TrafficEstimatorService is now available: http://www.youtube.com/watch?v=tR-YSrmszzw Best, - Eric On Nov 9, 1:18 pm, manuel manuel_pa...@sapo.pt wrote: Thanks Brendan but... Why is credit card returning $0 CPC from the API? And why $12.13 on the Keyword Tool and $10.22 on the Traffic Estimator? All set to English and US Thanks, Manuel On Nov 9, 3:21 pm, AdWords API Advisor adwordsapiadvi...@google.com wrote: Hi Manuel, Below is a sample request to the v201008 TES. soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/ envelope/ xmlns:o=https://adwords.google.com/api/adwords/o/v201008; xmlns:cm=https://adwords.google.com/api/adwords/cm/v201008; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header o:RequestHeader cm:authToken.../cm:authToken cm:clientEmail.../cm:clientEmail cm:developerToken.../cm:developerToken cm:userAgent.../cm:userAgent /o:RequestHeader /soapenv:Header soapenv:Body o:get o:selector o:campaignEstimateRequests o:adGroupEstimateRequests o:keywordEstimateRequests o:keyword cm:textdigital camera/cm:text cm:matchTypeEXACT/cm:matchType /o:keyword /o:keywordEstimateRequests o:maxCpc cm:microAmount100/cm:microAmount /o:maxCpc /o:adGroupEstimateRequests o:targets xsi:type=cm:CountryTarget cm:countryCodeUS/cm:countryCode /o:targets o:targets xsi:type=cm:LanguageTarget cm:languageCodeen/cm:languageCode /o:targets /o:campaignEstimateRequests /o:selector /o:get /soapenv:Body /soapenv:Envelope Brendan, You are sending a v13 TES request to the v201008 service. The XML format changed significantly between versions, so the same XML cannot be reused. More information about the new service is available here: http://adwordsapi.blogspot.com/2010/09/discover-v201008-trafficestima... Best, - Eric Koleda, AdWords API Team On Nov 8, 2:48 pm, brendangorm...@skinwest.com brendangorm...@skinwest.com wrote: Add me to the list. I've been using estimateKeywordList and it's giving me an exception: Fault occurred while processing. I'm posting it to this URL:https://adwords-sandbox.google.com/api/adwords/cm/v201008/CampaignSer... This is the same exact example from googles API website, except that I've inserted my credentials. ?xml version=1.0? env:Envelope xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; env:Header applicationTokenDQ--Q/applicationToken passwordXXX/password emailx...@example.com/email clientEmailclient_1+x...@example.com/clientEmail useragentnone/useragent developerTokenxx...@example.com++usd/developerToken /env:Header env:Body estimateKeywordList keywordRequests maxCpc10/maxCpc textmars cruise/text typeBroad/type /keywordRequests /estimateKeywordList /env:Body /env:Envelope The error is Fault occurred while processing If I change the password to BAD PASSWORD I get the same error, (not something to the effect of invalid credentials) this tells me the fault is occuring prior to authentication, if that helps. No error codes or anything that'd indicate what the problem is. It's really got me baffled, is there some way I can turn on more details for the errors? On Nov 4, 11:37 am, manuel manuel_pa...@sapo.pt wrote:q Can someone please post an example of a working xml request to the updated v201008 TrafficEstimatorService? Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API
Re: TrafficEstimatorService xml
Add me to the list. I've been using estimateKeywordList and it's giving me an exception: Fault occurred while processing. I'm posting it to this URL: https://adwords-sandbox.google.com/api/adwords/cm/v201008/CampaignService This is the same exact example from googles API website, except that I've inserted my credentials. ?xml version=1.0? env:Envelope xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:env=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; env:Header applicationTokenDQ--Q/applicationToken passwordXXX/password emailx...@example.com/email clientEmailclient_1+x...@example.com/clientEmail useragentnone/useragent developerTokenxx...@example.com++usd/developerToken /env:Header env:Body estimateKeywordList keywordRequests maxCpc10/maxCpc textmars cruise/text typeBroad/type /keywordRequests /estimateKeywordList /env:Body /env:Envelope The error is Fault occurred while processing If I change the password to BAD PASSWORD I get the same error, (not something to the effect of invalid credentials) this tells me the fault is occuring prior to authentication, if that helps. No error codes or anything that'd indicate what the problem is. It's really got me baffled, is there some way I can turn on more details for the errors? On Nov 4, 11:37 am, manuel manuel_pa...@sapo.pt wrote:q Can someone please post an example of a working xml request to the updated v201008 TrafficEstimatorService? Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
TrafficEstimatorService xml
Can someone please post an example of a working xml request to the updated v201008 TrafficEstimatorService? Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
