Recently, I received the fol­low­ing ques­tion from a blog reader:

We offer our web­site in mul­ti­ple lan­guages, as such we want to track which lan­guage a user was view­ing on a par­tic­u­lar page. There is no URL dif­fer­ence, as that value is stored in ses­sion. What is the best prac­tice for record­ing this met­ric, and report­ing on it? Can the real time reports in SC 14 make use of this met­ric as well (exam­ple: Page view per day by language)?

There­fore, I thought I would answer this ques­tion here in case any of you out there are in a sim­i­lar sit­u­a­tion and offer web­site con­tent in mul­ti­ple languages.

Se Habla Español?  Parle Ital­iano?
As we move to a global mar­ket­place, pro­vid­ing con­tent in mul­ti­ple lan­guages is becom­ing more and more com­mon.  How­ever, adding for­eign lan­guage capa­bil­i­ties to your web­site can be a dif­fi­cult, time-consuming effort.  Hence, over time, you might want to use Site­Cat­a­lyst to see if these efforts are pay­ing off or if adding this func­tion­al­ity is con­tribut­ing to the bot­tom line.  The fol­low­ing will show how I have dealt with this in the past.

Page­names and Pathing
The first item in this area I tackle is the Page­name vari­able since it is so impor­tant and dri­ves page-level pathing.  Obvi­ously, the first ques­tion here is whether you should have a dif­fer­ent page name for each page in each lan­guage.  While I can see rea­sons for doing this, I am a strong believer that you should have only one page­name for each page — regard­less of which lan­guage it is in.  This allows you to see the true pathing of pages irre­spec­tive of lan­guage.  Another rea­son I advo­cate this is based upon the sim­ple fact that you may have 20,000 pages on your site and if you trans­late them all into 10 lan­guages you will now have 200,000 pages to deal with in your pages and pathing reports!

How­ever, I con­cede that there may be cases where you want to see how vis­i­tors look­ing at pages in Span­ish dif­fer from those look­ing at pages in Chi­nese.  The eas­i­est way to do this is to use Omni­ture Dis­cover where you can eas­ily seg­ment on a lan­guage vari­able (see below) and then view the pathing reports dif­fer­ently for each lan­guage (or even com­bine a bunch of lan­guages together!).  But if you are not for­tu­nate enough to have Omni­ture Dis­cover, there is still a way to see pathing dif­fer­ences by lan­guage.  To do this, sim­ply con­cate­nate the lan­guage and the page­name (i.e. spanish:home page) and place that value into a new cus­tom Traf­fic Vari­able (sProp) and enable pathing.  Doing this will allow you to find any page in any lan­guage and then view pathing behav­ior tak­ing place before/after that page as shown here:

Suc­cess Events by Lan­guage
The next ques­tion I get from cus­tomers is to show them which of their web­site Suc­cess Events take place in each lan­guage.  For exam­ple, of all lead forms that are filled out, how many were sub­mit­ted by a user using the Span­ish lan­guage pages.  While you can derive this infor­ma­tion by look­ing at var­i­ous page reports as described above, the eas­i­est way to do this is through the con­ver­sion area.  On each page, sim­ply set a cus­tom Con­ver­sion Vari­able (eVar) with the value indi­cat­ing in which lan­guage that page is being viewed.  By hav­ing this value in an eVar, you can the open up that eVar report and add any Suc­cess Event met­ric you wish and see the per­cent­ages asso­ci­ated with each lan­guage as shown here:

Pages by Lan­guage
There are two other “traf­fic” related items that I like to show clients related to lan­guages.  The first is which pages are most often viewed in mul­ti­ple lan­guages.  To do this, I pass the lan­guage the page is being shown in to a Traf­fic Vari­able (at the same time it is passed to the eVar men­tioned above) and then cre­ate a Traf­fic Data Cor­re­la­tion between it and the Page­name vari­able.  Once you have done this, you can use the cor­re­la­tion to find any page on your site and then break it down by lan­guage to see how often it is viewed in each for­eign lan­guage as shown here:

Also, since cor­re­la­tions go both ways, you can eas­ily open the Lan­guage sProp report, find the “Span­ish” row and see what pages are most often viewed in Span­ish for your entire site.

The final thing you can review is how many pageviews and/or vis­its involve for­eign lan­guages.  Using the same sProp describes above, you can open up the sProp report and use Pageviews or Vis­its (if enabled) as met­rics to see the over­all usage of each lan­guage as shown here:

Any other cool things you have done to answer ques­tions related to for­eign lan­guages?  If so, please com­ment here…

Have a ques­tion about any­thing related to Omni­ture Site­Cat­a­lyst?  Is there some­thing on your web­site that you would like to report on, but don’t know how?  Do you have any tips or best prac­tices you want to share?  If so, please leave a com­ment here or send me an e-mail at insidesitecatalyst@​omniture.​com and I will do my best to answer it right here on the blog so every­one can learn! (Don’t worry — I won’t use your name or com­pany name!).  If you are on Twit­ter, you can fol­low me at http://​twit​ter​.com/​O​m​n​i​_​man.

Learn more about Omni­ture Consulting
Learn more about Omni­ture University
Tagged with →  
  • suzuki

    Site­cat­a­lyst report charts still have Japan­ese char­ac­tor cor­rups under v14.5. it is seri­ously prob­lem for for­eign lan­guage customers.

  • http://blogs.omniture.com/author/bgaines Ben Gaines

    suzuki — We would be happy to look into this. Please work with your Account Man­ager Omni­ture Client­Care to report and doc­u­ment the issue.

  • suzuki

    We are going to solve this issue w/ local AE and Client Care, The SaaS is easy to update and main­te­nance for client, No CDROM, no acti­va­tion keys ;-) , Thanks

  • Bar­bara

    Great post. We’re cap­tur­ing the lan­guage in an evar, then set this up as ASI seg­ment. I can then get full report­ing on page views, con­tent con­sumed etc in this ASI slot. Is this an alter­na­tive accept­able solution?

  • http://blogs.omniture.com/author/bgaines Ben Gaines

    Bar­bara: Yes, that’s an excel­lent alter­na­tive to the solu­tion described here. I don’t believe there is any func­tion­al­ity men­tioned in this post that you wouldn’t have in that ASI slot.