Detect Locale in Triggers
Please consider adding the ability to detect the visitor locale in Triggers as a built-in function. We know this is available via custom code, but we can't always rely on Web development to support our needs.
One use case:
Trigger 1:
- if ALL the following conditions are met:
- "Visitor Locale" = "es"
- Then take the following actions:
- "Add Tag" = "spanish"
Trigger 2:
- If ALL the following conditions are met:
- "Visitor Locale" = "fr"
- Then take the following actions:
- "Add Tag" = "french"
That would allow us to properly leverage the skills-based routing and make it work with visitor language, without the need for development intervention. This would be a huge advantage.
-
Hi Zac,
Thank you for the suggestion. Apart from the custom code, you could consider using visitor country or country-specific visitor URLs as proxy for locale. However, I understand that country-specific visitor URLs instead of locale would not work for your mobile users.
It is a good suggestion and would reduce effort towards custom code development. We will consider your feedback whenever we plan improvements for triggers in the future.
- Prakruti
-
Most of our traffic comes from the United States and Canada, where the language is not necessarily based on country (ex. US traffic could very likely be Spanish-speaking, while CA traffic could easily be French-speaking - but not always). Country-specific URLs would also be a great approach, but our pages are not designed with country-specific URLs so localization is handled by some other property of the session.
Thank you for the suggestions. I am sharing this only to further clarify why we think these improvements are important for our use case.
Please sign in to leave a comment.
2 Comments