How Tour My App differs from open source scripts
A few people have asked me about how Tour My App differs from using open source scripts for showing pop up tours from within the application. There are a number of advantages in using Tour My App over an open source script, which is what I’ll be explaining in this blog post.
Tour My App takes care of a number of small things that makes it extremely easy to integrate with your site:
- Spanning pages: Tour My App automatically handles tours which cross across multiple pages.
- Repeat tours: Tour My App keeps track of users who have already seen a tour, and will not show the same tour to them again. Tour My App also allows you to force a tour, and display it again for a user who has already seen it. For example, if a user wants to replay a tour again.
- URL triggers: Tour My App allows you to trigger tours by passing parameters through the URL. This extremely powerful mechanism enables many unique use cases. For example, when a customer asks a question, you can reply back with a URL which contains a tour trigger. When the customer visits the page, it automatically triggers a tour that shows them how to perform the task they asked about.
- No coding: With an open source script, all your tour steps are hardcoded into the page. If you want to add, remove, or change steps, then you have to go into the code, make changes, re-test and re-deploy. With Tour My App, you just log in to our site, make changes using our Tour Builder, and save. All your users now see the updated tour automatically. No coding, no re-deploys.
- Analytics: Creating tours is one thing. Gauging their effectiveness and iterating on the data is another altogether. Tour My App provides real time analytics that show you how users are navigating the tours, and helps you identify if there are certain steps that cause users to quit the tour. Use this data to refine your tours and maximise their effectiveness.