Thanks Anash.
I forgot to mention we have partialFailure enabled. We're also aware of
how to find out about the failed operations as you pointed out in the
examples.
Our question was about how to handle the successful operations returned
result. We need to know the ID of the new ads that
Thanks Anash.
The documentation you pointed says that *Operations per request* has a
value of *5,000* but then its notes say:
*For performance reasons we typically recommend passing no more than 2,000
operations per request.*
Which value should we use?
On Tuesday, January 20, 2015 at
This is a bug because the bidModifier is supposed to vary from
0.1 - 10.0: AdSchedule
https://developers.google.com/adwords/api/docs/reference/v201409/CampaignCriterionService.AdSchedule.html
And also for newly created schedules, the default bidModifier is 1 as they
still run at their 100%
Thanks Anash.
Just to confirm, when you say:
But the failed operations will not have a valid ad field or ids.
Do you mean there will be a NULL in the position of the failed Ad, or do
you mean there will be an AdGroupAd with invalid Ad ID (maybe something
like 0)?
On Tuesday, January 20,
Thank you for the quick response!
Turns out I confused clientId with customClientId. Now it works for me.
Am Montag, 19. Januar 2015 18:25:15 UTC+1 schrieb tic...@onmacon.de:
Hi,
I´m using Python. I finally managed to get the access thing running (in
fact I hope so). I filled in the values
Hi Oliver,
All the operations (failed and successful) will be returned in the results,
in the same order as you passed them to the server. But the failed
operations will not have a valid ad field or ids. You can use either that
information, or lookup the errors to see which operations failed
Hi,
When you create a feed you can see it in the AdWords UI under *Shared
Library* - *Business data*.
Best regards,
Josh, AdWords API Team
On Saturday, January 17, 2015 at 4:24:02 AM UTC-5, treto...@gmail.com wrote:
Hi,
when creating feed it stored somewhere? or it is automatically deleted
Hello,
My apologies; I had followed up with Naresh on a separate thread and never
come back to this one.
Make sure that you are looking for the AdWords API section in an MCC
production account, not in a client account or a test account.
Regards,
Mike, AdWords API Team
On Monday, January 19,
Добрый день!
Пытаюсь послать запрос к сервису AdGroupFeedService. Текст запроса:
?xml version=1.0 encoding=UTF-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:v20=https://adwords.google.com/api/adwords/cm/v201409;
soapenv:Header
v20:RequestHeader
Hello,
Hope you all are doing great.
Here is the job description below for the immediate requirement
Job title: SCRUM-MASTER Project Manager
Job location: McLean,VA
Duration: 12 Months
Interview Mode- WebEx
Today itself.
Contact me as soon as possible. Greatly appreciated.
--
Thanks
Hi,
Starting on January 15th, we've been getting intermittent failures when
running the audience performance report, complaining about the IsRestrict
field included in the list of fields to download. The same code has worked
for many months, and is now failing roughly 1/7 of the time (e.g. on
Thanks, Anash. Hopefully you guys will keep the download URL for the latest
files the same across updates, so http://goo.gl/3Mxbei (DMA)
and http://goo.gl/HndLIn (Geo locations). That way we can grab it
programmatically
more easily.
.
Hans
--
--
Today, in the process that uses this report extensively for a number of
clients, it looks like all the calls failed.
FYI,
Greg
On Tuesday, January 20, 2015 at 11:53:27 AM UTC-6, GregT wrote:
Hi,
Starting on January 15th, we've been getting intermittent failures when
running the audience
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
14 matches
Mail list logo
