Why targeting matters

A tour that appears to every user on every visit quickly becomes noise. Targeting lets you show the right tour to the right people at the right time — new users get onboarding flows, power users get advanced feature introductions, and everyone else is left undisturbed.

Accessing targeting settings

Open any tour in the Userorbit dashboard and navigate to the Targeting tab. This is where you define who should see the tour and under what conditions. Targeting rules are evaluated each time a page loads, so changes take effect immediately for new sessions.

Targeting by user properties

User properties are attributes you pass to Userorbit when identifying users — things like plan type, role, signup date, or company size. To target based on a property:

  1. In the Targeting tab, click Add condition.
  2. Select User property as the condition type.
  3. Choose the property name from the dropdown (e.g., plan).
  4. Pick an operator: equals, does not equal, contains, is greater than, etc.
  5. Enter the value (e.g., free).

This is useful for scenarios like showing an upgrade prompt tour only to users on the free plan, or showing an admin-specific walkthrough only to users whose role equals admin.

Targeting by events

Event-based targeting lets you show tours based on what users have (or have not) done. For example:

  • Has performed "Created Project" — show a tour introducing collaboration features to users who have already created their first project.
  • Has not performed "Invited Team Member" — show a tour encouraging users to invite teammates if they haven't done so yet.

You can also add frequency constraints, such as "performed the event at least 3 times" or "performed the event in the last 7 days."

Targeting by URL rules

URL rules control which pages trigger the tour. Options include:

  • Exact match: The tour activates only on a specific URL, like /dashboard/settings.
  • Contains: The tour activates on any URL containing a substring, like /projects/.
  • Regex: For advanced patterns, use a regular expression to match dynamic URLs like /projects/[a-z0-9-]+/edit.

URL rules are especially helpful for multi-page tours or for ensuring a tour only appears in the correct section of your app.

Combining conditions

Real-world targeting usually requires multiple conditions working together. Userorbit supports both AND and OR logic:

  • AND (all conditions must be true): Show the tour only to free-plan users who signed up in the last 14 days and are on the dashboard page.
  • OR (any condition can be true): Show the tour to users on either the free plan or the trial plan.

You can nest groups to build more sophisticated rules. For example: (plan equals "free" OR plan equals "trial") AND (signup date is within last 14 days).

Testing your targeting

Before publishing, verify your rules work as expected:

  1. Use the Preview as user feature in the builder to simulate a specific user profile.
  2. Check that the tour appears when conditions are met and stays hidden when they are not.
  3. Review the Audience estimate shown in the Targeting tab — it tells you approximately how many current users match your rules.

Tips for effective targeting

  • Start broad, then narrow. Launch with simple conditions and refine based on analytics.
  • Avoid overlapping tours. If two tours target the same segment on the same page, users may see conflicting guides. Use display priority settings to resolve conflicts.
  • Combine with display frequency. Targeting decides who sees the tour; display frequency decides how often. Use both together for the best experience.

Was this page helpful?