To avoid having to create one single welcome flow that contains content in all the languages we offer, we’ve decided to create a single list for each language.
Yes, we are going to create e.g. a welcome flow for each language.
We have a Custom Property set with the language they get determined by which Country they’ve signed up from.
In our Manage Preferences List we’ve added a step where they can change their language from A to B. But this ofc. doesn’t move the subscriber from List A to List B.
If we use the Subscribe-form they are only able to subscribe for the list they already belong to - as it’s a sign-up form for that specific list.
= we can change the Custom Property, but not add/move the subscriber to the right list
→ Do any of you have any suggestions on how we could work around this? We’re trying to avoid using Hosted Pages.
Best answer by Omar
On the other hand if it's one store with multiple languages (switcher) then this is not an option.
As for the question you're asking I would use 1 list and have the language as a profile property.
The other way you could go around this is to have a language segment and use that for triggers in flows.
You wouldn't want to have people moving automatically from list a to b (same is true for segments) because it would probably trigger a welcome flow unless you filter these cases out.
My best bet would be to have 1 list, have a profile property which indicates the language they are using and use that to filter the flows.
Then for specifics use segments.
Hope it helps