No programmatic way to get or set a member's language so emails go out with the correct language

Ask the community
, , ,
1

I have a multilingual site (two languages: primary Finnish, additional English). Member language preference seems to be set at registration based on the current language setting of the website. Check.

This information is saved somewhere because I can see and edit it from the dashboard: Site Members - Overview - Contact Info - Edit info - Language. Check.

I want to have site members be able to change this initial preference in such a way that future emails go out correctly. All the API calls I have been able to find are about site language functionality (i.e. changing the language the site is operating under) but not persisting the language preference into the member information (where it will be used by automation for email translation).

I can write custom code to mange the UI ways this could be changed by the user (explicitly or automatically) but I cannot find any API call to view or update the member information. Wix’s AI SDK Assistant confirms this in the response to the query “How do I access a member’s preferred language?” The short part of the answer was: “Based on the provided documentation, accessing a member’s preferred language directly from their member profile using current, non-deprecated APIs is not explicitly detailed.”

Anyone else encounter this?

2

Response from Wix support:

From what you’ve described, I understand that you’d like members to be able to change their language preference after registration so that future automated emails are sent in the correct language.

At the moment, I’d like to clarify that this information is not yet accessible via any public Velo API.

I’ve gone ahead and submitted feedback to our development team requesting that this member language information be exposed via an API, as we understand how useful this would be for managing multilingual email automation. While I can’t provide a timeline, we do hope this will be considered for a future implementation.

In the meantime, depending on your use case, you may consider a workaround using custom code. For example, you can retrieve the currently active site language using:

https://dev.wix.com/docs/velo/apis/wix-window-frontend/multilingual/current-language

You could then store this value in a custom member field or a CMS collection linked to the member, and use it for your own logic (such as determining which emails or content to send via the automation using velo code actions).