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 finalUrls set )
cheers
On Tuesday, June 23, 2015 at 3:16:06 PM UTC+1, Giles Bodger wrote:
>
> 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 create a
> BiddableAdGroupCriterion and set the finalUrls value (new string[]
> {"myurl"}) and i do nothing with the destinationUrl property. My keyword is
> created no problem. HOWEVER when i try to apply the same logic to adding a
> new keyword to a campaign that already exists (but has yet to be migrated
> (i.e. it isn't July yet)) I am getting this error ....
>
> *AdGroupCriterionError.CANNOT_SET_BOTH_DESTINATION_URL_AND_FINAL_URLS*
>
> This, i cannot understand because i removed the code that would set my url
> to the old destinationUrl property, and coded up the setting of the
> finalUrls.
>
> Does your whole campaign have to have been migrated before you can start
> to add new entities with a finalUrls value ? Are you not allowed to have
> keywords in a campaign that some have destinationUrl set and others have
> finalUrls set ??
>
> I have read that a work around might be to set the detinationUrl to null
> or an empty string, but that seems to be a hack and in any way the
> destinationUrl is readonly as of july 1st so trying to set it after that
> time will give me an error i believe
>
>
> 2. Our internal processes caused a duplication of several new keywords we
> were adding. All with the finalUrls set, but for whatever reason we created
> pairs of identical keywords to be added in 1 api call. All good, and we
> have built in management to account for the errors given back by the
> interface, BUT the error we got is a little misleading - if indeed it
> actually means "you have a duplicate in your request" - the error we are
> getting is ...
>
> *AdGroupCriterionError.CANNOT_MODIFY_URL_FIELDS_WITH_DUPLICATE_ELEMENTS*
>
> We would have expected an error like "DUPLICATE_ELEMENT" or something, if
> indeed this is a duplicate error issue
>
>
>
> Anyhow, many thanks in advance
>
> Giles
>
>
>
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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
---
You received this message because you are subscribed to the Google Groups
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/d56abd2a-ccfe-4896-a7ca-2aa9ef13ea58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
