Automatically launch topics for new users

With autolaunchers, you can automatically launch topics on your website. This is a super effective solution to launch announcements and updates to users upon logging in or playing onboarding guides for new users.

Before you create an autolauncher

In this article, we won’t talk about building guides as such. If you haven’t created your onboarding guide yet, take a look here for instructions.

Creating an autolauncher requires several features to be enabled or implemented. This article will provide instructions on how to enable each feature to create an autolauncher for new users.

When you enable people tracking, Inline Manual will start tracking your website or application users. With that data, you can access reports to see who they are, and their behaviors. You can use these reports to discover where they are from, which tutorials they completed, and their latest activity. Enabled people tracking is required to automatically play your walkthroughs.

To enable people tracking and allow Inline Manual to gather information about your users, you need to first enable analytics. Next, add few lines of code above the regular player code.

Place the script tag with window.inlineManualTracking = {} code above the line which embeds Inline Manual Player to your web application. If your application is single page app (Angular, React, Ember), please follow instructions here.

See example implementation below:

<!-- User tracking data -->
<script>
  window.inlineManualTracking = {
    uid: "1", // Only this field is mandatory
    email: "john@doe.com",
    username: "johndoe",
    name: "John Doe",
    created: 1360610467,
    updated: 1433168312,
    roles: ["admin", "editor"],
    group: "Doe & Partners Inc.",
    plan: "Gold"
  }
</script>
<!-- Inline Manual embed code -->
<script>!function(){var e=document.createElement("script"),t=document.getElementsByTagName("script")[0];e.async=1,e.src="https://inlinemanual.com/embed/player.a9f92b0ea59e550eae1fdf4d1f7e7cc0.js",e.charset="UTF-8",t.parentNode.insertBefore(e,t)}();</script>

Your application should replace the values set above with the currently logged in user id. The uid is the only field that is required and can be anything that is unique for the current user - a string, integer, number, e-mail etc.

The created and updated fields are in UNIX Timestamp format in seconds.

To use variables from your application, replace the values with the variable name. For example:

<script>
  window.inlineManualTracking = {
    uid: app_uid,
    email: app_email,
    username: app_username,
    name: app_name,
    created: app_created,
    updated: app_updated,
    roles: app_roles,
    group: app_group,
    plan: app_plan
  }
</script>

To check if people tracking is enabled correctly, go to Inline Manual portal and see if under the Site -> People tab, there are any users profiles gathered. Alternatively, use the Status in the Authoring tool.

Now it's time to create Segments.

Segments allow you to categorize users into specific segments, that you can then target. There are 2 default segments that you can use: New Users and Everyone but new users. However, you can create new segments with a different set of rules.

To create a segment: 1. Login to Inline Manual portal with your e-mail and password.

  1. Go to Sites and choose a site you want to create segmentation for.

  1. Go to Segments tab. You will see 2 default segments: Everyone but new users and New users. You can use those segments right away if you send the relevant data to us. If you want to add your own, custom segment proceed to point 4.

  1. Click + New segment button.

  1. Name your new segment.

  1. Add relevant rules based on the data you pass to us. Refer to people tracking for more information. Set up Field (eg. role) and Condition (eg. contains: Admin).

  1. Confirm adding a rule with Done button.

  2. You can add more rules with + Add rule button, or confirm adding a segment with Save button.

Can't determine new users by created/registration date:

The default New users segment may be a simple choice but might impose an issue. Newly created users may see the topic if they stay signed in to the application but might miss it if they suddenly sign out or leave. Once they get back, the rule Created within 30 minutes will return false and the topic won’t launch for them anymore.

You can use the First Seen rule for this, or you can send info from your platform that they are new as part of one of the fields. Note that the player will be checking the First seen information on the time when the user is seen after the Inline Manual player is implemented. So for example, a user logs in a day before the Inline Manual player has been implemented then logs back in a day after the player has been implemented, then that will be the first time that the user has been seen by the player.

You can abuse fields from people tracking e.g. roles or groups to send other information that is not available from the default people tracking fields.

To create an autolauncher:

  1. Login to Inline Manual portal with your e-mail and password.

  2. Go to Sites and choose a site you want to create an autolauncher for.

  1. Go to Automation tab.

  1. Click + New autolauncher to add an autolauncher

  1. It will open a form that you need to fill in with relevant data.

  1. Choose a topic that you want to apply an autolauncher to.

  1. Choose a segment. Default Segments are:

New users - the autolauncher will launch for users that were created (signed up) in less than 30 minutes and haven't seen the topic.
Everyone but new users - the autolauncher will launch for users that were created (signed up) in more than 24 hours and haven't seen the topic.
Everyone - the autolauncher will launch for all users.

You can choose the default New users segment, or a segment you created.

  1. Choose a number of plays - how many times the autolauncher should play the selected topic. By default, the autolauncher is set to play only once. If you want to launch the autolauncher several times, enter the specific number. If you want to play it again and again, enter 0.

  1. Check play only if topic wasn't completed. Checking this option (checked by default) will make the autolauncher play only if it wasn't completed (the user didn't go through the whole walkthrough to the end).

  1. You can also check Allow users to dismiss this autolaunched topic. Choosing this option allows your users to opt out from the autolaunched topic. If the user has chosen to dismiss the autolaunched topic, the topic will not be launched automatically in the future whether the user has completed the topic or not.

  1. With Play again after, you can set up autolauncher to play topic multiple times. This setting allows you to set minimum time interval to start the topic again. If you set it to 24 hours, the autolauncher will launch again after the 24 hours interval.

Now if you want to, you can take advantage of advanced activation rules.

  1. You can select a language. The autolauncher will activate only when InlineManualOptions.language is set to appropriate language code (ISO 639-1 code e.g. en for English).

  1. You can select Device. The autolauncher will activate only on particular device category. Choose from All, Mobile or Desktop.

  1. You can also set up URL Match:

Pattern - the autolauncher is activated only when URL matches this pattern. Enter absolute URL with * as a wildcard: e.g. ://.example.com/*, :///some/path, :///?aa=&bb=123#xxx
Match (regex) - enter regular expression that should match.
Not match (regex) - enter a regular expression that should not match.

It’s useful when you want to create an onboarding sequence that encourages your users to explore the app. You can automatically launch guides whenever they visit a specific section for the first time.

If all set, confirm adding the autolauncher with Save button.

Once your autolauncher is set up, you can check for inconsistencies using the Inline Manual Status Tool. This tool checks the overall status of the player on your website, along with other features like segments, variables, automation and more.

The main sections that need to be checked on the results are the segmentation and autolaunchers.

You can find the whole guide about troubleshooting autolaunchers here.

FAQ
Was this article helpful?