Overview

Apart from the ease of use & setup, UserGuiding allows you to display the right content to the right user at the right time.

Sending user properties and event data to UserGuiding will ensure that the context & timing for your content is perfect for your users. We recommend you pass this data as you install UserGuiding on your platform to save developer time in the long run and give a smooth start to your project.

Here are some specific examples to help you think about your organization’s case on what data you should send to UserGuiding to provide a tailor-made experience for your end users.

Use Case Examples for Custom User Properties and Event Data

User Onboarding

Passing custom user properties & event data to UserGuiding, creating segments based on this information, and setting those segments to the onboarding content will make sure that the in-app onboarding process of your platform is always tailored for each relevant user.

For this use case, you can consider sending user attributes such as:

  • Signup date - If you want to initiate the onboarding process only for your new users, not the existing ones, you may consider passing this attribute. Learn more about segmenting new & existing users here.

  • User role - If your onboarding process varies based on different roles/types of users, you may consider passing this attribute. An example would be an Onboarding Checklist that will be shown only to technicians.

  • Plan type - If your product offers different experiences based on different plan types, you may consider creating different onboarding processes based on this information.

  • First name - You may use this attribute to personalize the onboarding experience. You can learn more about how to achieve this here.

For events, you may consider targeting your new users based on an event that is specific to your product, related to their activation & hasn’t occurred yet.

Here’s an example of an onboarding Checklist that is shown to users who didn’t go live with UserGuiding yet:

You can create a similar experience for your platform by following the steps explained in this use case article.

Product Adoption

Giving small nudges to users who have already taken some key actions in your platform helps them understand what’s more to achieve with your product. For such cases, to make sure the content is displayed to correct users at the correct time, you can:

Pass user attributes such as:

  • Sign up date

  • Plan

  • Role

Or, pass platform-specific adoption events that are tracked in your product that can let you know the product adoption progress of a user.

Here’s an example:

To set a segment for this Guide, we used:

  • Team Member Limit Property

  • Team Member Count Property

You can create a similar experience for your platform by following the steps explained in this use case article.

Feature Adoption

Letting users know about the latest feature releases inside the application is a great way to boost feature adoption. To make sure you are targeting the right audience for such announcements, you can:

Pass user attributes such as:

  • Signup date - All features are new for a newly signed-up user. So you might want to announce the release of a new feature to your existing users only.

  • Plan - It is important to consider different authorization levels of different plans when announcing a new feature. A feature may be disabled for specific plans.

  • Feature usage - This may help if you want to announce an improvement for an existing feature already used by some users. Instead of letting all users know about this specific improvement, you can announce it to those already using the old version.

Or, pass platform-specific feature adoption events that are tracked in your product that can let you know if a user has already discovered or adopted a new feature.

Here’s an example:

To set a segment for this Guide, we used:

  • Resource Center Created (Boolean)

You can create a similar experience for your platform by following the steps explained in this use case article.

In-app Surveys

It may create some friction and decrease the response rate of your surveys to ask for your user’s feedback on product experience via email or 1-1 meetings. Instead, you can use UserGuiding to display in-app surveys at the right place & time.

Here’s an example of an in-app survey that we used to collect feedback regarding the implementation period of UserGuiding:

We used Created At property to target users who have been paying customers for more than two months. You can use other properties or event data to display your in-app surveys to the correct audience.

In-app Announcements

Announcements inside the platform can be used to let users know about various things related to your product - such as the latest updates, a planned downtime, an upcoming webinar, etc. While announcements may be relevant to all users, some instances may require you to set a segment to the content to display it to the correct audience.

Here’s an example of an in-app announcement that we used to announce an upcoming webinar to users who have been using UserGuiding for more than three weeks:

We used Created At property to target those users. We chose not to show it to relatively new accounts because we did not want to distract them with too much information as they create content actively & learn their way around the application.

You can create a similar experience for your platform by following the steps explained in this use case article.

Did this answer your question?