Hi Hans
no worries - we have resolved our issues with josh's help so please carry
on with your questioning
cheers
Giles
On Wed, Jul 1, 2015 at 12:00 AM, HK wrote:
> Hi, Josh
>
> I'm still trouble-shooting this, but I just reproduced the error and
> captured the request ID - 000519c3d3f0bd000a
For the record, the requested details have been sent to Josh on a private
thread.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Hi Hans,
Thanks for providing all of the details. I've tried several variants and
can't seem to reproduce the behavior you described, but I can see that the
request ID you sent did indeed fail with the error you mentioned. I've
raised this with the shopping team and asked them to investigate. I
Josh,
Wanted to add some clarifications to the above. After playing with this
some more, it appears that if deleting a product partition and then
recreating it again (going from unit to subdiv), the APIs don't accept
having different custom parameters for the two, even though they don't have
t
Hi, Josh
I'm still trouble-shooting this, but I just reproduced the error and
captured the request ID - 000519c3d3f0bd000abf2547680fa3a5. Now, while
doing this, I noticed that the request has ...
true
Taking that out, resolves the issue for me. So it seems to be related to
custom parameters a
Hi Hans,
Thanks for posting these details. Do you happen to have the *requestId* from
one of your requests that failed? I've tried to replicate this issue in my
test account, but the request succeeds every time.
Cheers,
Josh, AdWords API Team
On Monday, June 29, 2015 at 7:50:42 PM UTC-4, HK wr
Guys, not sure if this will help or confuse, but we have a unit test for
Product Groups that have been working every day for at least the last six
months, but started failing 5/31 with
the CANNOT_MODIFY_URL_FIELDS_WITH_DUPLICATE_ELEMENTS error. I can provide
more details if needed, but it seems
No problem, and yes we will change our code accordingly as and when the
destinationUrl property is removed -
cheers for your help Josh
On Friday, June 26, 2015 at 5:09:21 PM UTC+1, Josh Radcliff (AdWords API
Team) wrote:
>
> Hi Giles,
>
> Thanks for helping identify the change in behavior with
Hi Giles,
Thanks for helping identify the change in behavior with duplicate keywords.
I'm following up with the upgraded URLs team to see if this was
intentional. I'll post back once I have an update.
As to whether you'll be able to continue to pass "" for *destinationUrl* after
July 1st, I'm
Hi Josh - ok so it looks like we were trying to add a keyword text / match
type combination that already existed. But we were actually trying to Add
and not update. So the system is smart enough to think that if there is
already a match on keyword and matchtype within the adgroup you are trying
Just so you know Josh, I can send the same scenario #1 request to our QA
sandbox environment and the creation succeeds.
New Keyword with finalurl set, destinationUrl not set, for an existing
adgroup and campaign (the adgroup now contains a mix of keywords some with
destinationUrl set some with
Just one more thing Josh - I have no problem creating the keywords affected
by scenario #1 on our QA environment
On Wednesday, June 24, 2015 at 1:17:56 AM UTC+1, Giles Bodger wrote:
>
> OK - i have got the soap request and requestId for a test i just ran to
> example the #1 scenario
>
> Requ
OK - i have got the soap request and requestId for a test i just ran to
example the #1 scenario
Request made approx 12.57am GMT 23-06-2015
Request header
https://adwords.google.com/api/adwords/cm/v201502";>
ADD
19071444504
Epica билеты концерт Krakow
EXACT
15
http://www.viag
Hi Giles,
On #1, are you sure this is happening when adding a *new* keyword to an
existing campaign's ad group, and not when trying to issue a *SET* operation
that passes the final URLs? To my knowledge, we'll only throw that error in
two scenarios:
1. On a *SET* where *finalUrls* is specif
Hi all
We have made a change to our API integration that now sets the finalUrls
value and not the destinationUrl on a BiddableAdGroupCriterion when adding
a keyword to an AdGroup and Campaign.
We have been seeing a couple of weird errors though
1. When adding a COMPLETELY NEW campaign i can cr
15 matches
Mail list logo
