AdWords
2.7K members online now
2.7K members online now
Use AdWords conversion tracking and reporting to measure your results. Have a question about Google Analytics? Post it here, on the Google Analytics Community!
Guide Me
star_border
Reply

reading value track paremeters for {keyword} when non latin laguage

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi,

 

When my ad is clicked the {keyword} value in the URL is replaced with non latin chars (hebrew).
When I try to retrieve it from my servlet I get non readable chars.

I undestand it has to do with the encoding of the tomcat.
I tried to set the encoding to UTF-8 but didn't see a change.

 

Is there a setting I can use in the URL itself that will give me the values in Unicode or other encoding?

 

Thanks.

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by Mini-CM (Community Manager)
September 2015

Re: reading value track paremeters for {keyword} when non latin laguage

Top Contributor
# 3
Top Contributor

Hello and welcome;

AdWords supports non-Latin characters. (i.e UNICODE and Punycode) in display and destination URLs

 

It seems to me that servlet on the Apache Tomcat does not support the Hebrew encoding of the destination URL. (But, you need to check that with Apache developers.)

 

Read more:

Non-ASCII characters now supported in display and destination URLs

 

-Moshe

 

Moshe, AdWords Top Contributor , Twitter | Linkedin | Community Profile | Ad-Globe
Did you find any helpful responses or answers to your query? If yes, please mark it as the ‘Best Answer’

View solution in original post

Re: reading value track paremeters for {keyword} when non latin laguage

[ Edited ]
Zee Community Manager
Community Manager
# 2
Zee Community Manager
Community Manager

Hi ace1977,

I've asked Moshe, our expert Top Contributor, to help out.

Zee
G+
Marked as Best Answer.
Solution
Accepted by Mini-CM (Community Manager)
September 2015

Re: reading value track paremeters for {keyword} when non latin laguage

Top Contributor
# 3
Top Contributor

Hello and welcome;

AdWords supports non-Latin characters. (i.e UNICODE and Punycode) in display and destination URLs

 

It seems to me that servlet on the Apache Tomcat does not support the Hebrew encoding of the destination URL. (But, you need to check that with Apache developers.)

 

Read more:

Non-ASCII characters now supported in display and destination URLs

 

-Moshe

 

Moshe, AdWords Top Contributor , Twitter | Linkedin | Community Profile | Ad-Globe
Did you find any helpful responses or answers to your query? If yes, please mark it as the ‘Best Answer’