Using v201402 I don't seem to be able to use AWQL as is claimed by the
changelog:
http://googleadsdeveloper.blogspot.com/2014/03/announcing-v201402-of-adwords-api.html
Uncaught SoapFault exception: [Client] Function ("query") is not a valid
method for this service in
Stack trace:
#0 foo.php(
Using v201402 I can't seem to use AWQL to query ManagedCustomerService as
the release notes seem to indicate I should be able to:
http://googleadsdeveloper.blogspot.com/2014/03/announcing-v201402-of-adwords-api.html
PHP Fatal error: Uncaught SoapFault exception: [Client] Function ("query")
is
operations and parameters.
>
> Cheers,
>
> Ray
>
> On Tuesday, March 18, 2014 4:28:45 PM UTC-4, Ian Knox wrote:
>>
>> Using v201402 I can't seem to use AWQL to query ManagedCustomerService as
>> the release notes seem to indicate I should be able to:
>
I'm in the process of writing a simplified wrapper for the Adwords API
client lib and it would be really helpful if there was some way to get a
list of AWQL fields for service calls other than copy/pasting them from
this website:
https://developers.google.com/adwords/api/docs/appendix/selector
It's handy but currently the country code attribute seems broken (or at
least with the PHP client)
$selector->fields = array('Id', 'LocationName',
'CanonicalName','DisplayType', 'ParentLocations', 'Reach',
'TargetingStatus', 'CountryCode');
$selector->predicates[] = new Predicate('ID', 'E
For what it's worth, we've been seeing the same issue while using PHP
client lib 3.2.1 and v201209 *and* v201206.
I see that 3.2.2 has been released so I'll give that a go and report back
shortly.
Ian Knox
On Wednesday, November 7, 2012 12:56:18 PM UTC-6, Gatsby Lee wrote:
ad no luck with 3.2.2 either.
:(
On Wednesday, November 7, 2012 3:02:07 PM UTC-6, Ian Knox wrote:
>
> For what it's worth, we've been seeing the same issue while using PHP
> client lib 3.2.1 and v201209 *and* v201206.
> I see that 3.2.2 has been released so I'l
We've been experimenting with using pthreads in php (see pthreads.org) in
order to make a multi-threaded application for fast retrieval of
TargetingIdeaService data and we've run into a bit of a snag. Any member
of a thread must support serialization and since the client library uses
the built
I've been seeing this behavior as well.
I assume this is because we've been pre-approved at the "standard" level
for the new pricing structure but I have an e-mail out to our CSR to
confirm.
(reference:
http://googleadsdeveloper.blogspot.com/2013/01/new-simplified-adwords-api-pricing.html)
On
So has anyone heard if there's going to be a Q4 workshop for 2014?
We're hoping to send someone but schedules fill up fast this time of year.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.goog
In 201409 several field names were changed
(see: https://developers.google.com/adwords/api/docs/guides/migration/v201409)
however it appears that the displayFieldName and xmlAttributeName data
found in the ReportDefinitionService isn't changing:
[54] => Google\Api\Ads\AdWords\v201409\ReportDefin
e
> name tend to follow the same conventions as the UI.
>
> Cheers,
> Josh, AdWords API Team
>
> On Monday, December 1, 2014 2:37:46 PM UTC-5, Ian Knox wrote:
>>
>> In 201409 several field names were changed (see:
>> https://developers.google.com/adwords/api/docs/
Hi there,
Has anyone else noticed a big increase in the amount of time it takes to
get keyword performance reports starting on 12/06/2014? The following
query (see below) repeated 385 times (once per account) currently takes
somewhere around 6 hours to generate ~2GBs of reports. To the best of
. Oommen,
> AdWords API Advisor.
>
> On Wednesday, January 21, 2015 at 12:44:24 AM UTC+5:30, Ian Knox wrote:
>>
>> Hi there,
>> Has anyone else noticed a big increase in the amount of time it takes to
>> get keyword performance reports starting on 12/06/2014? T
#x27; will be 1.57, but when you use
the same max CPC for the term 'chicago bike shop' alone it returns a value
of 1.47.
As you can imagine this provides a bit of a problem for
getting individual keyword values since the maximum number
of campaignEstimates per SOAP request (we
Anyone have any idea about this?
I've attached a the SOAP_LOG from two example transactions that exhibit this
behavior... notice the difference in the values returned for 'Chicago Bike
Shop'
Ian
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group
Anyone have any idea about this?
I've attached a the xml log from two example transactions that exhibit this
behavior... notice the difference in the values returned for 'Chicago Bike
Shop'
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http
transaction and generates a ton of un-wanted XML overhead.
Ian Knox
On Sep 6, 1:12 pm, David S wrote:
> Hello,
>
> I have discovered a problem with the TrafficEstimatorService which I can
> reproduce in my own code using v201101 and I can also reproduce it using
> Google's o
Hi Eric, thanks for getting back to me about this but I still think there's
something gone wrong here.
I understand that the estimates aren't being generated in a vacuum but it
seems that under some circumstances they should be and they aren't. For
instance if you had a traffic estimate reques
Eric,
I don't think it's a coincidence-- my results in testing have been
consistent: estimating single keywords in a series of different
adgroups yields the same result as estimating them in one adgroup _unless_
you place the individual adgroups in separate campaigns.
I've attached SOAP XML lo
Thanks for confirming it Eric-- I'll follow up with the general AdWords
forum and see where that takes me.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=
So I just thought I'd follow up here to see if there might be any new
thinking regarding this issue. I attempted to get some information about
this in the AdWords forum but no-one seemed to have any idea why the
Estimator behaves this way.
Eric (or whomever), is there another resource I can u
I have a suspicion that there's been some problems in AdWords-land. We've
been seeing the same behavior with the TargetingIdeaService on and off for
the past few days.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.
Hi folks,
For the past 5 days or so our software that gets information from the
Targeting Idea Service has been generating the dreaded unexpected internal
API errors like crazy. It's been only working correctly about 10% of the
time.
I've attached a sample XML file of the errors-- any idea wha
Hi Kevin, thanks for looking into this for me--
That extra tag shouldn't have been there, but after fixing it the results
are still the same-- log attached.
Ian
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http
Has anyone else noticed a massive slowdown in the TrafficEstimatorService
and/or the TargetingIdeaService over the last few days? We've seen our
overall queries per second drop from 25-ish to less than 2.
There have been no software changes and some testing indicates the API
taking around .5
Sadly, the only way I know of is to submit each keyword in it's own
campaign and adgroup which limits you to 5 (yes,* 5*) keywords per request.
I've asked about this in the past and the API team has referred me to the
general adwords group, where my requests have fallen on deaf ears.
For referen
27 matches
Mail list logo
