Many Sleekplan customers with diverse, international user bases face a common challenge: how to communicate product updates, collect and display feedback in their users' preferred languages. Whether you're running a global SaaS platform, a multi-regional mobile app, or any product serving customers across different countries, providing content in each user's native language is crucial for engagement and user satisfaction.
Setting Up Multilingual Content with SSO and Segmentation
While one approach is to create separate workspaces for each language, a more efficient solution is to use a single workspace with SSO authentication and user segmentation working together to dynamically display language-specific content depending on the user who is viewing it. Here's how to set it up:
Step 1: Pass Language Data Through SSO
Single Sign-On is needed because it is the source that is going to identify the user language. When implementing Single Sign-On, include the user's language preference as a custom user parameter in the SSO token sent to the Sleekplan app :
💡Payload example :
{
mail: 'youruser@login.com',
name: 'Derek Jovic',
meta: { user_language: 'en' },
iat: 1769283998
}
Step 2: Create Language-Based User Segments
1. Navigate to your Sleekplan Admin dashboard, Settings > Segmentation > Available Fields section , click on Add Field
📝Make sure that the field Identifier has the exact same spelling as the parameter in the token. In the example above that would be user_language
2. Click on Create Segment button. The Language field will now display as an available criteria for segmentation:
3. Click on Add Rule and type the token value for the specific language to which this segment is going to apply and click on Save Segment:
Step 3: Apply the segmentation to product announcements or feedback display
1. As an example, we are going to create a changelog which is going to appear only for the English speaking audience.
Navigate to your dashboard > Changelog > New.
2. Apply the Segment previously created to the changelog and publish it.
3. Only users with the matching SSO language meta data will be able to see this announcement in English.
🔗 More on User Segmentation here.