Creating Quest Stops

Modified on Tue, 16 Apr at 5:29 PM

Place your first Quest Stop very near the Quest Starting Point, so that it will be easy for users to find, and they can understand how Quests work without having to hunt for the first stop. 

We recommend placing it less than 50 metres away from the Starting Point, for example, at the same intersection, but on the opposite side of the street. 

  • Create a Place for your first Quest Stop. Fill in the details for this stop in the following format:

Title: All Quest stops should have a title in the following format: [NAME OF QUEST] Stop 1: [NAME OF LOCATION]. 

For example, if you are creating a Quest named the “Lakeside Park Quest” the Title of your first stop might be: “Lakeside Park Quest Stop1: Park Entrance Gates”.

Description: In the Description field you will need to include clues to lead users to your next Quest stop. You can make your clues as easy or as hard as you like. You can give a hint as well, and your hint should always be very easy. Think about your audience - is your Quest for people who know your area well, or for people who are visiting for the first time? Is it kid friendly? 

  • Don’t forget to include images to accompany your Quest Stop. In addition to a main image that will appear at the top of your Quest Stop, you can include additional images as part of the clue in the description using the inline images tool or even add images under the read more line under the “Need a Hint? Click Read More below” statement (see below).

  • Once you’ve written your clue, insert the following standard text at the bottom:


Found this by accident? Click to learn more about this Quest, or to start from the beginning. [INSERT INTERNAL DEEP LINK TO THE QUEST START - documented below or contact support@driftscape.com to get this link once you are ready].


  • Insert this link into the above line https://www.driftscape.com/mobileappdeeplink?driftscape_action=open_feature&driftscape_feature_uuid=(paste your Quest start point UUID here) 

  • To find your Quest start points UUID follow the following steps:

    • Head to the your Quest Start Point POI [Point of Interest] in the CMS 

    • Look at the URL bar

    • In the URL you will find a code “POI&ID=” followed by a unique 6 digit no - this 6 digit no. is the unique identifier (UUID) to your Quest start points.  (a sample UUID is marked in the image below for your reference) 

    • Add only this 6 digit no. into the link above, as instructed above 

    • Once done, insert the link into the text

  • Once you’ve embedded the link as instructed, insert the following standard text at the bottom:


Need a Hint? Click Read More below.



  • Always add a hint using the ‘Read More’ feature to provide a hint. Make your hints really easy - you’re basically just telling the user where to go next. To add your hint, use the  ‘Add horizontal line’ icon in the toolbar at the top of the Description field:


Note: Everything below the horizontal line will only appear after the Read More button is tapped.

Here is what it looks like  in the app before and after the ‘Read more’ button is tapped:


  • For all Quest Stops, set “Allow Discovery Mode” to NO.

  • For all Quest Stops, set Quest Type to With hints.

  • Continue adding stops with clues to guide users to the next stop on your Quest.

  • On the final Quest Stop, insert the following standard text to the end of the Description field: 

Keep Exploring in Driftscape! [INSERT THIS INTERNAL DEEPLINK - https://www.driftscape.com/mobileappdeeplink?driftscape_action=show_all - TO TURN ALL CONTENT BACK ON].

  • On all Quest stops, you should set the ‘Quest Start Reference’ field:

  • A quest start reference field helps the app identify what quest starting point” those respective stops are related to. By setting this field, it will prevent the quest stop from accidentally being discovered in map and AR mode unless the user has previously opened the matching Quest start POI.

  • By default, this field is not set, which means that the quest stop can be discovered at any time by users.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article