Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.userpilot.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Userpilot allows you to create flows that span multiple pages using the Page Change step. This feature ensures a seamless user experience when guiding users through a multi-page journey. While we generally recommend creating separate flows per page, Page Change steps help maintain continuity when necessary.

​
Use Cases

  • Onboarding Flows: Guide new users across multiple pages for a complete onboarding experience.
  • Feature Walkthroughs: Showcase features that require user interaction on different pages.
  • Multi-Step Processes: Assist users in completing forms, or multi-step actions across different URLs.
  • User Education: Provide tooltips or modals across various sections of an app without breaking the flow.

​
Adding a page change step

Here are the step-by-step instructions to add a page change step between your flow steps.
  1. Create the first part of your flow on the initial page.
  2. Navigate to the URL where the flow should continue.
  3. Click on Add Page Change in the flow editor.
  4. Configure the page change as Silent or Forced.
  5. Save and test your flow.

​
Silent vs. Forced Page Changes

  • Silent Page Change: The flow waits for the user to navigate to the URL on their own before continuing.
  • Forced Page Change: The system automatically redirects the user to the specified URL and continues the flow.
If your URL contains dynamic elements, you can handle them using:
  • Wildcards (*): Replace dynamic sections with an asterisk in Silent page changes (e.g., /dashboard/*/settings).
  • User Attributes: For Forced page changes, replace the dynamic part with a user attribute already passed via the Userpilot script.
The Build URL must match the exact target page and cannot include an asterisk (*), as this would direct users to a URL with an asterisk instead of dynamically adjusting.

​
Testing your page change rule

To verify that your Page Change step is configured correctly:
  1. Expand the Test Page Rule in the page change editor.
  2. Enter the URL path you want to validate.
  3. Click on the Test to check if it matches the expected settings.
This is particularly useful when testing scenarios where user-specific URLs may vary.

​
Smart Continue

The Smart Continue feature allows users to resume a flow from the step where they left off, ensuring a smoother experience without restarting from the beginning.

​
How it works

  • When enabled, users who leave and return to the page will continue from the last completed step.
  • This option is available under the Page Change step in the flow settings.
  • By default, Smart Continue is disabled. You can enable it as needed.
It only applies to manually triggered flows and does not affect flows triggered automatically.

​
How to enable smart continue

  1. Navigate to the flow settings.
  2. Locate the Page Change step.
  3. Check the “Smart Continue” option to activate it.
  4. Save and publish your changes.
Pagechange Pn

​
FAQs

If the URL does not change when navigating between pages, trigger a fake reload and set the Page Change step to activate on that fake reload URL configured by your dev team.
The Page Change allows the flow to continue across pages, either after a user navigates (Silent) or is redirected (Forced). In contrast, the “Go to URL” button action simply redirects the user to another page, but the flow stops, and the next step won’t trigger.
Yes, loading delays after a page change are normal. That’s because flows are designed with two display features:
  • stop running after a page change
  • start running once a page is fully loaded