Tokens for language paths in URLS | Adobe Higher Education
Skip to main content
A
Anonymous
May 2, 2017
Vraag

Tokens for language paths in URLS

  • May 2, 2017
  • 1 reactie
  • 3920 Bekeken

We have several different websites that are localized by country. We also have a large resource library on our site (each one).

To localize our website, we have different language paths in the URLs. We track each resource that people download by having a separate program and smart campaign that drives people into individual SFDC campaigns. We do not separate SFDC campaigns by country, which means our trigger is based on the form they fill out and the URL they fill out the form on (each URL with the different language paths).

Often we have to fix a previous language path (en-uk to en-gb) or add additional language paths. I want to tokenize this so this process is global and more easily editable and fixable. But I haven't found a way to really do this effectively, has anyone else been able to do this or does anyone have any ideas for ways to do this?

Thank you!

Er kunnen geen reacties meer worden geplaatst op dit onderwerp.

1 reactie

A
Anonymous
May 4, 2017

Hi Joanna!

Let me make sure I'm understanding the scenario.

A resource like:

  1. Definitive Guide to Compliance Program Assessment | NAVEX Global (UK version)  
  2. Definitive Guide to Compliance Program Assessment | NAVEX Global (US version)

Will have one Marketo program and one SFDC campaign, correct? You'll use a smart campaign that looks at form fill and URL to add people to that program.

Then, when you say you have to "fix" a previous language path, what do you mean by that? Also, can you give me a bit more detail around your thought process for tokens?

A
Anonymous
May 4, 2017

Jamie,

You have the scenario correct.

An example of what I mean by "fix" a previous language path, when something goes from /en-uk/ to /en-gb/ for SEO purposes. The other situation I would like to solve for is when we add localized sites, for example we are in the process of launching a french version of our website that would be /fr-fr/. I would love to NOT have to go through all ~400 assets and add the links with the new french language path.

I've globalized things using tokens in the past so I've been trying to figure out a way to do this with tokens, but I understand there may be a different way of going about this and I'm open to all those things.

Thanks!

SanfordWhiteman
SanfordWhiteman
Level 10
May 4, 2017

Not sure there's any special trick here. Language in your examples is just another segment of the path. As such, if it exists verbatim as a lead field, include that token. If it needs to be derived from other fields, use Velocity.

ForumvoorwaardenAccessibility statement

Loading footer...