Skip to content

Give new users a clear place to start.

Bring the first steps into one onboarding page. Explain the task, show what comes next, and link users to the action they need to complete in your product.

Onboarding example
  1. Welcome
  2. Connect data
  3. First report
First report

Your sample data is ready.

Create a report to see the result.

Sample dataConnected for this example

Help users move from welcome to work.

Explain the first task.

Use text, images, and video to show where to begin and what a useful result looks like.

Keep the next step in view.

Organize setup into steps so users can move through the task without piecing together separate instructions.

Put help beside the action.

Open a product tour when a step needs a closer walkthrough, or link to the relevant page in your product.

Try it as your user

Move through a short onboarding example and create a sample report.

Your product

Let’s create your first report.

0 of 3 steps complete

Step 1 of 3

Welcome

Start with your data. Connect a sample source, then create a report your team can use.

Demo only. No account or data connection required.

Choose where onboarding appears.

Inline

Place onboarding inside an existing page, alongside the work users need to do.

How to set it up

Connect your product. Build the first path.

Add Flowtomate through Google Tag Manager or an SDK integration. A developer may need to connect the user properties and actions your onboarding uses. After setup, your team can update the content without a new app release.

  1. Choose a useful result.

    Pick one task new users need to complete, such as creating their first report.

  2. Build the steps.

    Add explanations and buttons, then connect each step to the relevant action or tour.

  3. Preview and publish.

    Check the flow in your interface and publish it for the audience you choose.

Questions about onboarding pages

How is an onboarding page different from a checklist?

A checklist keeps a set of tasks visible. An onboarding page gives those steps room for explanations, media, and actions. Use the format that fits the amount of help each task needs.

Can a step open a product tour?

Yes. Add a button that starts a tour when users need help with a task in the interface.

Do we need a developer?

A developer may be needed for installation, user data, product actions, or the place where inline onboarding appears. After setup, your team can change the content and publish updates without a developer for each change.

Does completing onboarding mean the user got value?

Completing the guide and completing a useful action are different results. Define the action you want users to take in your product and review it alongside onboarding progress.

Map your first onboarding flow.

Bring one task your new users need to complete. We’ll walk through the steps, choose where guidance fits, and define the action you want users to finish.

Request a demo

Leave your details. We’ll email you to find a time for the demo.