Though it's worth noting that we do already have some keywords with
umlauts in their urls - they got there through adwords editor, I
believe. It's only through the API that we have a problem.
On Aug 20, 2:55 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
I can confirm that you can't set the destinationUrl of a keyword to
something containing the ü character. However, this behavior is
identical to the behavior from the AdWords web interface--attempting
to do that from the web interface leads to the same "These characters
are not allowed: ü" error message. Considering that this behavior is
identical I'd have to assume it's intentional and AdWords legitimately
does not support that character in URLs.
I'm not sure how some keywords could have been added via the AdWords
Editor that violated this, as the same rules should apply there.
Perhaps this was a recent policy change, although I don't recall
hearing anything about it.
Cheers,
-Jeff Posnick, AdWords API Team
On Aug 20, 3:15 pm, dq <kayakm...@gmail.com> wrote:
> Though it's worth noting that we do already have some keywords with
> umlauts in their urls - they got there through adwords editor, I
> believe. It's only through the API that we have a problem.
> On Aug 20, 2:55 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
> wrote:
> > Hello DQ,
> > Is this in the Sandbox or Production environment?
> > Cheers,
> > -Jeff Posnick, AdWords API Team
> > On Aug 20, 2:50 pm, dq <kayakm...@gmail.com> wrote:
> > > I'm trying to set the url of a keyword to something that includes an
> > > umlaut. When I update they keyword, I get the following error:
> > > These characters are not allowed: ü
> > > I've tried both with and without url encoding. Urls with either adgro
> > > %C3%BCp or adgroüp in the url fail with the same error message.
> > > Is there any way to make this work? Is it linked to the campaign's
> > > language targeting?
> I can confirm that you can't set the destinationUrl of a keyword to
> something containing the ü character. However, this behavior is
> identical to the behavior from the AdWords web interface--attempting
> to do that from the web interface leads to the same "These characters
> are not allowed: ü" error message. Considering that this behavior is
> identical I'd have to assume it's intentional and AdWords legitimately
> does not support that character in URLs.
> I'm not sure how some keywords could have been added via the AdWords
> Editor that violated this, as the same rules should apply there.
> Perhaps this was a recent policy change, although I don't recall
> hearing anything about it.
> Cheers,
> -Jeff Posnick, AdWords API Team
> On Aug 20, 3:15 pm, dq <kayakm...@gmail.com> wrote:
> > Though it's worth noting that we do already have some keywords with
> > umlauts in their urls - they got there through adwords editor, I
> > believe. It's only through the API that we have a problem.
> > On Aug 20, 2:55 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
> > wrote:
> > > Hello DQ,
> > > Is this in the Sandbox or Production environment?
> > > Cheers,
> > > -Jeff Posnick, AdWords API Team
> > > On Aug 20, 2:50 pm, dq <kayakm...@gmail.com> wrote:
> > > > I'm trying to set the url of a keyword to something that includes an
> > > > umlaut. When I update they keyword, I get the following error:
> > > > These characters are not allowed: ü
> > > > I've tried both with and without url encoding. Urls with either adgro
> > > > %C3%BCp or adgroüp in the url fail with the same error message.
> > > > Is there any way to make this work? Is it linked to the campaign's
> > > > language targeting?
this indeed is a 'recent' change. It was introduced with no
notification or public announcement (that I know of) and I had the
same problems you did, DQ. I also thought that it worked using Adwords
Editor, but try it again now, you'll get an error and have to change
the display url in Adwords Editor, too.
So you can't use umlauts in your urls any more. And no, there is no
way to esapce or encode them.
- Jan
On 20 Aug., 23:17, dq <kayakm...@gmail.com> wrote:
> Thanks for looking into it. Is there no escaping of the umlauts that
> I can apply to have them appear in the url?
> Thank you,
> DQ
> On Aug 20, 4:47 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
> wrote:
> > Hello DQ,
> > I can confirm that you can't set the destinationUrl of a keyword to
> > something containing the ü character. However, this behavior is
> > identical to the behavior from the AdWords web interface--attempting
> > to do that from the web interface leads to the same "These characters
> > are not allowed: ü" error message. Considering that this behavior is
> > identical I'd have to assume it's intentional and AdWords legitimately
> > does not support that character in URLs.
> > I'm not sure how some keywords could have been added via the AdWords
> > Editor that violated this, as the same rules should apply there.
> > Perhaps this was a recent policy change, although I don't recall
> > hearing anything about it.
> > Cheers,
> > -Jeff Posnick, AdWords API Team
> > On Aug 20, 3:15 pm, dq <kayakm...@gmail.com> wrote:
> > > Though it's worth noting that we do already have some keywords with
> > > umlauts in their urls - they got there through adwords editor, I
> > > believe. It's only through the API that we have a problem.
> > > On Aug 20, 2:55 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
> > > wrote:
> > > > Hello DQ,
> > > > Is this in the Sandbox or Production environment?
> > > > Cheers,
> > > > -Jeff Posnick, AdWords API Team
> > > > On Aug 20, 2:50 pm, dq <kayakm...@gmail.com> wrote:
> > > > > I'm trying to set the url of a keyword to something that includes an
> > > > > umlaut. When I update they keyword, I get the following error:
> > > > > These characters are not allowed: ü
> > > > > I've tried both with and without url encoding. Urls with either adgro
> > > > > %C3%BCp or adgroüp in the url fail with the same error message.
> > > > > Is there any way to make this work? Is it linked to the campaign's
> > > > > language targeting?
|
