strictly speaking, but I'll
pass your comments on to the correct team.
Best,
- Eric Koleda, AdWords API Team
On Jul 30, 5:27 pm, ojak ojakub...@gmail.com wrote:
More to the point, how about adding a field to
BiddableAdGroupCriterion called 'keywordInsertion' of type
'xsd:string
Anash,
I share Pitambari's frustration here. We also receive API errors
based on undocumented, arbitrary system limits and it's quite painful
to catch and correct for these sorts of exceptions (i.e. it kills our
productivity since we often spend more time writing error-handling/
retry code than
Currently, the AdWords keyword insertions framework is extremely
limiting. It forces advertisers into a weak choice between using an
exact keyword, or a generic default term based on an arbitrary string
length (25 or 35 characters). It seems that AdWord's current method
is biased toward a theory
'. This new
field would then be approved/disapproved by Google in much the same
way that Ad Unit copy is handled.
Any thoughts or better suggestions?
On Jul 30, 1:06 pm, ojak ojakub...@gmail.com wrote:
Currently, the AdWords keyword insertions framework is extremely
limiting. It forces advertisers
team regarding that error message and see if we can
get any further information about the cause. In regards to the
ReceiveTimeoutError, I'm assuming this is a client side timeout, and
not a message returned in the SOAP XML?
Best,
- Eric
On Jul 14, 4:09 am, ojak ojakub...@gmail.com wrote
that mean
there is a Google internal issue?
On Jul 13, 3:51 pm, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
Hi,
The reasons are listed here:
http://code.google.com/apis/adwords/v2009/docs/reference/BulkMutateJo...
Best,
- Eric Koleda, AdWords API Team
On Jul 11, 10:39 pm, ojak
retry your requests
after receiving this error as it may work the second time.
Best,
- Eric
On Jul 10, 6:55 pm, ojak ojakub...@gmail.com wrote:
Honestly, I can't get it to fail with any regularity. I'll send the
same SOAP request twice, sometimes it works, sometimes it fails.
Exact same
The example only shows campaign creation. Is it possible to submit Ad
operations without creating a mock campaign and ad group just to check
the Ad operation's syntax?
Thanks.
On Jul 13, 7:47 pm, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
Hi Suraj,
Yes, you can use the
The example in the link shows campaign creation validation, but is it
possible to validate Ad operation streams without creating a mock
campaign and ad group (e.g. verify request of Ad and Keyword
operations only)?
Thanks.
On Jul 13, 7:47 pm, AdWords API Advisor adwordsapiadvi...@google.com
on the
BulkMutateJobService. I'll bring this to the attention of the core
engineering team, and in the mean time you should retry your requests
after receiving this error as it may work the second time.
Best,
- Eric
On Jul 10, 6:55 pm, ojak ojakub...@gmail.com wrote:
Honestly, I can't get it to fail
Received the following error:
BulkMutateJobError.REQUEST_PART_IS_OUT_OF_ORDER @
operation.operand.request
The docs have this curt note:
REQUEST_PART_IS_OUT_OF_ORDER: The request part is not the next one
expected to be received.
So, my questions are:
* What order is it expecting?
* How
an
ExemptionRequest for the keyword that you can attach to the ADD
operation:
http://code.google.com/apis/adwords/v2009/docs/reference/AdGroupCrite...
Best,
- Eric Koleda, AdWords API Team
On Jul 11, 10:38 pm, ojak ojakub...@gmail.com wrote:
What causes a CriterionPolicyError for PolicyName 'trademark
for the keyword that you can attach to the ADD
operation:
http://code.google.com/apis/adwords/v2009/docs/reference/AdGroupCrite...
Best,
- Eric Koleda, AdWords API Team
On Jul 11, 10:38 pm, ojak ojakub...@gmail.com wrote:
What causes a CriterionPolicyError for PolicyName 'trademark' and
where
I'm not able to get BulkMutateJob's to behave for large jobs
(submitted to sandbox).
For example, the results (below) on a job with 500k operation reports
the status as COMPLETE, but the stats say the progress is 13%,
numUnprocessedOperation is 431,450, and the numFailedOperations is 0.
How can
What causes unprocessed results for completed jobs?
Thanks.
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received
It's 10k operations... can I send it directly to you?
On Jul 2, 2:42 pm, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
Hi,
Can you post the sanitized SOAP XML request and response that
demonstrates the error?
Best,
- Eric Koleda, AdWords API Team
On Jul 1, 2:43 pm, ojak
and response that
demonstrates the error?
Best,
- Eric Koleda, AdWords API Team
On Jul 1, 2:43 pm, ojak ojakub...@gmail.com wrote:
Receiving InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when
submitting a BulkMutateJob.
The API docs state is:
Indicates that a server-side error has occured
, and parts exist to allow you to
upload more than 10,000 operations into a single job.
Best,
- Eric Koleda, AdWords API Team
On Jul 6, 4:32 pm, ojak ojakub...@gmail.com wrote:
What criteria should be used when deciding how to segment
BulkMutateJob operations across multiple JOBS, PARTS
Operation streams exist to allow you to take advantage of concurrent
processing on different campaigns, and parts exist to allow you to
upload more than 10,000 operations into a single job.
Does this mean that since PARTS contain OPERATION STREAMS, do PARTS
also process concurrently?
For
After reading the BMJS overview (http://code.google.com/apis/adwords/
v2009/docs/bulkjobs.html), I'd like to verify whether I am reading the
limits correctly and how to apply these limits. The limits are as
follows:
* CLIENTS may contain up to 10 JOBS
* JOBS may contain up to 100 PARTS
*
What criteria should be used when deciding how to segment
BulkMutateJob operations across multiple JOBS, PARTS, and OPERATION
STREAMS?
After reading the BMJS overview (http://code.google.com/apis/adwords/
v2009/docs/bulkjobs.html), the limits appear to behave as follows:
* CLIENTS may contain
Receiving InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when
submitting a BulkMutateJob.
The API docs state is:
Indicates that a server-side error has occured. InternalApiErrors
are generally not the result of an invalid request or message sent by
the client.
REASON:
Advisor wrote:
Hi,
Your last analysis is correct, this error is because you are
specifying fractions of a penny, which isn't allowed.
Best,
- Eric Koleda, AdWords API Team
On Jun 29, 10:27 pm, ojak ojakub...@gmail.com wrote:
This might be an API limitation, maybe?
It looks like all
, AdWords API Team
On Jun 29, 10:27 pm, ojak ojakub...@gmail.com wrote:
This might be an API limitation, maybe?
It looks like all USD values need to be rounded to the nearest 10,000
micros, and then the API accepts the bids (i.e. minimum granularity of
$0.01 USD). I'm assuming
Is it possible to query the start time of a BulkMutateJob?
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received
I'm receiving BiddingError.BID_TOO_MANY_FRACTIONAL_DIGITS for a bid
microAmount that is not fractional (SOAP log confirms that the number
is indeed not fractional):
n2:operations xsi:type=n2:AdGroupCriterionOperation
n2:operatorADD/n2:operator
n2:operand
states that it's a Float precision problem. In
the Ruby issue in the above post, the microAmount is already being
cast to an Integer (using Float#to_i), so I'm not quite sure what's
going on?
On Jun 29, 3:33 pm, ojak ojakub...@gmail.com wrote:
I'm receiving
, ojak wrote:
I'm receiving BiddingError.BID_TOO_MANY_FRACTIONAL_DIGITS for a bid
microAmount that is not fractional (SOAP log confirms that the number
is indeed not fractional):
n2:operations xsi:type=n2:AdGroupCriterionOperation
n2:operatorADD/n2:operator
n2:operand xsi:type
29, 5:51 pm, ojak wrote:
Found a similar looking error from the PHP API, but it doesn't seem to
explain what's going on in the Ruby API:
http://groups.google.com/group/adwords-api/browse_thread/thread/662d1...
The PHP API problem states that it's a Float precision problem.
However, in the Ruby
On Jun 18, 7:57 pm, ojak ojakub...@gmail.com wrote:
The processingTimeMillis stat on jobs is not useful during monitoring,
as the processing time does not appear to be updated until the process
is complete.
Here is an example of a returned BulkMutateJobStats object (via Ruby
API
account to test your API calls. Do you
have the request id or job ids that are stuck in the sandbox?
Cheers,
Anash P. Oommen,
AdWords API Team.
On Jun 17, 11:43 pm, ojak ojakub...@gmail.com wrote:
Well, I have 8 stuck jobs that have been in there for 2 days, and they
were really small
account to test your API calls. Do you
have the request id or job ids that are stuck in the sandbox?
Cheers,
Anash P. Oommen,
AdWords API Team.
On Jun 17, 11:43 pm, ojak ojakub...@gmail.com wrote:
Well, I have 8 stuck jobs that have been in there for 2 days, and they
were really small
. Meanwhile, you
can use another fresh sandbox account to test your API calls. Do you
have the request id or job ids that are stuck in the sandbox?
Cheers,
Anash P. Oommen,
AdWords API Team.
On Jun 17, 11:43 pm, ojak ojakub...@gmail.com wrote:
Well, I have 8 stuck jobs that have been
The processingTimeMillis stat on jobs is not useful during monitoring,
as the processing time does not appear to be updated until the process
is complete.
Here is an example of a returned BulkMutateJobStats object (via Ruby
API):
#AdWords::V200909::BulkMutateJobService::BulkMutateJobStats:
I noticed that my Sandbox environment has multiple PENDING jobs that
have been there for many hours. Is there any way to remove them or
can I safely ignore them?
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
When querying a 'processing' job, the stats are always empty:
job
= #AdWords::V200909::BulkMutateJobService::BulkMutateJob:0x103e2bfb8
@id=30236, @numRequestPartsReceived=2, @status=PROCESSING,
@numRequestParts=2, @policy=[], @job_Type=BulkMutateJob,
yourself, and I don't know if Google performs a
periodic clean up of the pending jobs.
On Jun 17, 5:36 am, ojak ojakub...@gmail.com wrote:
I noticed that my Sandbox environment has multiple PENDING jobs that
have been there for many hours. Is there any way to remove them or
can I safely
=
service_bulk_mutate_job.module::BulkMutateJobSelector.new
selector.includeHistory = true
selector.includeStats = true
jobs = service_bulk_mutate_job.get(selector)
jobs[0].stats
Note that PENDING jobs will not return any stats (nil).
On Jun 16, 10:53 pm, ojak ojakub...@gmail.com
38 matches
Mail list logo
