FAB PagePilot

GuideDocs
k
Getting Started
Module
Home
Settings
Other
Tour Visual Editor
Create A New Tour from Scratch
Target Page & Alternative Target Page

What is a Target Page?

A Target Page is the specific page where you want your Page-Pilot tour to start.

You do not need to enter your website's full URL. Simply enter the page path (the part of the URL that comes after your domain name).

Example

If your website URL is:

https://yourwebsite.com/dashboard

Enter this as the Target Page:

/dashboard

✅ Correct: /dashboard❌ Incorrect: https://yourwebsite.com/dashboard


How to Find the Target Page

  1. Open the page where you want the tour to appear.
  2. Look at the URL in your browser.
  3. Copy everything after the domain name, including the /.

Examples

Website URLTarget Page
https://yourwebsite.com/dashboard/dashboard
https://yourwebsite.com/pricing/pricing
https://yourwebsite.com/account/settings/account/settings
https://yourwebsite.com/products/new/products/new

Easy Tip

Think of a website address like this:

https://yourwebsite.com/dashboard
│──────── Domain ────────││── Page Path ──│

Only enter the Page Path in Page-Pilot:

/dashboard

What is an Alternative Target Page?

Sometimes the same page can be accessed using different URLs. Instead of creating multiple tours in Page-Pilot, you can add Alternative Target Pages. The tour will start when a visitor opens any of the specified page paths.

Example 1 — Same Dashboard, Two URLs

Your application allows users to open the Dashboard from two different routes.

Website URLConfigure As
https://yourwebsite.com/dashboardTarget Page: /dashboard
https://yourwebsite.com/homeAlternative Target Page: /home

Result: The same tour will appear on both /dashboard and /home.

Example 2 — Product Page

A product page is available through two routes.

Website URLConfigure As
https://yourwebsite.com/storeTarget Page: /store
https://yourwebsite.com/productsAlternative Target Page: /products

Result: Visitors opening either page will see the same tour.


Target Pages with Dynamic Slugs (Variable IDs in the URL)

Some pages in your application include a dynamic value in the URL — like a user ID, order number, or record ID. This value changes for every visitor or every record, so it can't be entered as a fixed path.

For these pages, use a placeholder in place of the dynamic part of the URL. In Page-Pilot, wrap the variable segment in a colon, like :id.

Example

If your actual page URLs look like this:

https://pagepilot.com/devesh/9876645552522/view
https://pagepilot.com/devesh/1122334455667/view
https://pagepilot.com/devesh/5566778899001/view

Notice that devesh and view stay the same, but the number in the middle changes for every visitor.

Enter this as the Target Page:

/devesh/:id/view

✅ Correct: /devesh/:id/view❌ Incorrect: /devesh/9876645552522/view (this only matches that one specific ID)

How It Works

Page-Pilot treats :id as a wildcard for that segment of the URL. Any value in that position — numbers, letters, or a mix — will match, and the tour will start correctly regardless of which record the visitor is viewing.

More Examples

Website URL PatternTarget Page (with placeholder)
/devesh/9876645552522/view/devesh/:id/view
/orders/45213/summary/orders/:orderId/summary
/users/john-doe/profile/users/:username/profile
/products/8891/edit/products/:productId/edit

When Should I Use a Dynamic Slug?

Use a placeholder like :id when:

  • The page URL contains a value that's unique per record (user ID, order ID, ticket number, etc.).
  • The rest of the URL structure (the parts before and after the dynamic value) stays the same across all instances of the page.
  • You want one tour to work across every record of that type, instead of creating a separate tour for each ID.

Best Practices for Dynamic Slugs

✅ Use a colon (:) followed by a descriptive name for the dynamic segment (e.g. :id, :orderId, :username). ✅ Keep the static parts of the path exactly as they appear in the real URL. ✅ You can combine dynamic slugs with Alternative Target Pages if the same dynamic page has more than one route.

❌ Do not enter one specific ID value as the Target Page — it will only match that single record. ❌ Do not leave the dynamic segment blank — always use a named placeholder.


When Should I Use an Alternative Target Page?

Use an Alternative Target Page when:

  • The same page is available through multiple URLs.
  • Different user roles open the same page using different routes.
  • Your application has old and new URLs that both lead to the same screen.
  • You want one tour to work across multiple routes without creating duplicate tours in Page-Pilot.

Best Practices

✅ Enter only the page path. ✅ Always start the path with a forward slash (/). ✅ Use Alternative Target Pages if the same page can be opened from multiple routes. ✅ Verify the path matches the URL exactly.

❌ Do not enter the full website URL. ❌ Do not omit the leading /. ❌ Do not add spaces before or after the path.


Common Mistakes

❌ Incorrect✅ Correct
https://yourwebsite.com/dashboard/dashboard
dashboard/dashboard
pricing/pricing
yourwebsite.com/pricing/pricing

Frequently Asked Questions

Why doesn't my tour appear?

Check the following in Page-Pilot:

  • The Target Page matches the page URL exactly.
  • The path begins with /.
  • You entered only the page path, not the full website URL.
  • If the page is available through another route, add it as an Alternative Target Page.

Can I add more than one Alternative Target Page?

Yes. You can add multiple Alternative Target Pages if the same page can be accessed through different URLs. The tour will start when the visitor opens any of the configured paths.

My page URL has a changing ID in it — how do I set the Target Page?

Replace the changing part of the URL with a named placeholder, such as :id. For example, if your URL is /devesh/9876645552522/view, set the Target Page to /devesh/:id/view. See Target Pages with Dynamic Slugs above.

Build by FAB Builder. The source code is available on GitHub.

ContactSponsor

Translate

Choose language

Select your preferred language for this documentation.