Learn how to deliver the right product updates to the right users! In this tutorial, we demonstrate how to target your changelog releases to specific user segments based on custom metadata like language, region, or user roles.
By leveraging Olvy's user tagging and segmentation features, you can ensure your release notes remain highly relevant, preventing clutter and improving user engagement.
If you already have the Olvy announcement widget embedded in your application, this step-by-step guide will show you exactly how to implement setUser functions, pass custom tags, create automated user segments, and publish targeted updates.
1. Start with the changelog widget already embedded 0:00
- The walkthrough assumes the Olvy announcement/changelog widget is already installed in your application.
- Users should already be able to open the widget from inside the app.
- The basic setup is done using the standard installation guide and showWidget call.
2. Decide what user attribute you want to target on 0:23
- The example uses language as the targeting attribute.
Two sample users are introduced:
- Jane Doe → language set to Swedish
- John Doe → language set to Norwegian
- The goal is to show a release only to users whose language matches a chosen value, such as Norwegian.
3. Send user metadata into Olvy with setUser 2:04
- In addition to showWidget, use the setUser function in the Olvy utils.
Pass logged-in user metadata such as:
- identity
- unique ID
- designation
- custom tags
- The key idea is to include a tags array for each user.
- In this example, the user’s preferred language is stored as a tag.
Read more about User Identification in Olvy Widgets here:
Anand Inamdar
4. Tag users with their language code 3:07
- When a user logs in, call setUser and include their language as a tag.
Example tags might represent:
- English
- Swedish
- Norwegian
- Once the widget loads, Olvy captures these tags for each user.
- This makes it possible to identify users by language inside the platform.
5. Create segments based on those tags 4:27
Create separate segments for each language, such as:
- English
- Swedish
- Norwegian
- For each segment, add a condition based on the tag value.
Example:
- The Norwegian segment includes users whose tags contain the Norwegian language code (NO).
- Any user with that tag is automatically added to the matching segment.
6. Assign a segment to a release in the release settings 6:06
- Open the release you want to target.
- In Step 3: Settings, go to the Advanced section.
- Under Segments, choose the target segment.
Example:
- Select Norwegian if the release should only be visible to Norwegian-speaking users.
- Publish the release after selecting the segment.
7. Verify that only matching users can see the release 7:44
- Test with a user whose language is Swedish.
- After refreshing the app and opening the widget, the Norwegian-targeted release does not appear.
- This confirms the user is not part of the Norwegian segment.
8. Confirm visibility for a user in the target segment 8:38
- Test with a user whose language is Norwegian.
- After reloading the app and opening the widget, the Norwegian release appears.
- This confirms segment-based targeting is working correctly.
9. Repeat the process for other segments 9:38
- You can target other releases to other segments the same way.
Example:
- Publish a release targeted to the Swedish segment.
- Swedish users will see that release.
- Norwegian users will continue to see the Norwegian release, but not the Swedish one.
10. Key takeaway 10:33
- Segment-based release targeting lets you show changelog updates only to the right users.
- You control segmentation by sending user metadata through setUser.
- Tags can be based on language, region, or any other custom criteria.
- This makes changelog releases more relevant and personalized.