Tours can be shared or sent by a link. This works by sending your users a link to the page where the tour starts, and appending a query parameter to the end of it that willl tell Product Fruits to try to start a specified tour. Product Fruits needs to be installed into the application for this to work.
https://my.productfruits.com/portal/workspace/xxxxxxxxxxxx/in-app-content/tours/detail/65649
then the tour ID is 65649.https://playground.productfruits.space
and the tour is meant to start on the /dashboard
page, then the URL where the tour starts is https://playground.productfruits.space/dashboard
.?pf_start_tour=TOURID
query parameter to the end of it, replacing TOURID with the tour id that we found in the first step. So, to finish the example, we would send users https://playground.productfruits.space/dashboard?pf_start_tour=65649
. Unfortunately, if you follow this url a tour won't actually start as Product Fruits isn't installed into this page.If your application routing is removing query parameters (e.g. there is redirect/URL rewrite triggered by your application) before Product Fruits is loaded, the tour will not start. In these cases, we are not able to detect the pf_start_tour
parameter.