5 tips to optimize your tour

Updated 2 years ago by Corine Barbazanges

The GuidiGO application contains many features that can improve the visitors’ experience of your tours and enable you to create something that users will want to be a part of.

  1. Synchronize your images and audio content
    You don’t need to be a professional editor in order to transform every stop of your tour into a mini documentary! By synchronizing your images and audio content, you will allow the visitor to see the image of your choice at the exact right moment of your commentary.

  1. Pay attention to the order of the stops
    Arrange the stops in a way that helps your visitor avoid walking an unnecessary distance. To move a stop within the tour, use the “Reorder” feature in the 2nd tab (Stops) or the drag & drop option in the 3rd tab (Map).
After you have changed the order of the stops, consider adjusting the route on the map.

  1. Draw the route of your tour on the map
    Even if a straight line is the shortest path from point A to point B, it does not necessarily guarantee the most enjoyable tour. Edit the default path to show the visitor which route you recommend they take.

  1. Utilize different types of content
    GuidiGO has always given you the option to add audio, images and text to your tours. Today, the possibilities are even greater. You can now enrich your stops with videos, 360-degree views / photospheres compatible with Google cardboard, as well as 3D models from the website sketchfab.com (read this article).
At the moment, 3D models from Sketchfab are available in the GuidiGO web app, but not in the GuidiGO mobile applications.

  1. Use Private Mode to test your own tours
    You know your tour by heart… Still, we advise you to test it yourself before making it public, in real conditions, and inside the application. This is the best way to spot the small details which, once optimized, will make all the difference to your users. In order to do that, publish your tour in Private Mode; you will then be the only one to have access to it in the application.

How Did We Do?

Powered by HelpDocs (opens in a new tab)