Creating Challenges

Creating challenges in OuterSpatial is a great way to engage with your visitors. You can ask visitors to respond to one or more questionnaires while camping in the backcountry or publish a trails challenge that requires visitors to check-in to one or more outing to complete.

Each challenge in OuterSpatial can include any number of "Tasks", each of which can be completed by visitors in one of two ways:
  1. By "checking-in" to an area, outing, point of interest, or trail
  2. By responding to a "questionnaire" (one or more questions)
A few more notes about challenges:
  • Visitors can respond to challenges even when they don't have a network connection
  • You can require that visitors successfully complete either all of a challenge's tasks or just a subset of the challenge's tasks to complete the challenge
  • You can download visitor responses to each challenge's tasks on-demand from within Manager
We're looking forward to making challenges available to all OuterSpatial organizations soon. We'll update this help article with more information as we work towards a full launch of this new feature.

Submitting a Challenge

If you are interested in creating a challenge and the OuterSpatial team has asked your organization to submit details for the challenge, please provide the following:
  1. Name
  2. Description: A one-paragraph description of the challenge. Short and concise.
  3. Start Date: Only required if the challenge is available for only a specific period of time
  4. End Date: Only required if the challenge is available for only a specific period of time
  5. Onboarding Text: Text to display to visitors when they start participating in your challenge. This can be multiple paragraphs and can contain links and lists. You can use this to highlight "Terms & Conditions" or just general information about your challenge that you want visitors to acknowledge before they start participating.
  6. Tasks: One or more challenge tasks your visitors can complete. There are two types of challenge tasks available:
    1. Check-in:
      1. Feature Type: The type of feature your visitors have to "Check-in" to to complete this task. Can be "Area", "Outing", "Point of Interest", or "Trail".
      2. Feature ID: The ID of the feature your visitors have to "Check-in" to to complete this task
    2. Questionnaire:
      1. Title
      2. Subtitle
      3. Work with the OuterSpatial team to develop the form configuration
  7. Ordered: Do your challenge's tasks have to be completed in a specific order? Can be "true" or "false". (This will be "false" for most challenges.)
  8. Completion Level Number: How many of your tasks do visitors have to complete to "Complete" the Challenge? For instance, if your challenge has 10 tasks, the number would be "10" if visitors have to complete all the tasks to "Complete" the challenge.
  9. Visibility: Do you want to make this challenge available to all OuterSpatial users? Can be "true" or "false". If "false", the only way visitors can "Participate" in your challenge is if you create a Campaign and use the associated deep link/QR code to "onboard" visitors into your challenge.
  10. User Email Access Required: If your challenge requires that the user gives your organization permission to access their email address, this should be "true". Otherwise, it should be "false".

Download Challenge Responses

You can download all of the responses to your challenge on-demand in OuterSpatial Manager. Just select your organization, go to the "Challenges" section, and select the "Download" option in the "Actions" button next to the challenge name. This will download all of the challenge responses in CSV format.

Some notes about the fields that will come down in the CSV file:

  • "enrolled_at": The date/time, in UTC timezone, that the visitor started "participating" in the challenge.
  • "enrolled_at_local_time": The date/time, in your organization's designated timezone, that the visitor started "participating" in the challenge.
  • "started_at": The date/time, in UTC timezone, that the visitor started the challenge response on-device.
  • "started_at_local_time": The date/time, in your organization's designated timezone, that the visitor started the challenge response on-device.
  • "submitted_at": The data/time, in UTC timezone, that the visitor submitted the challenge response on-device.
  • "submitted_at_local_time": The data/time, in your organization's designated timezone, that the visitor submitted the challenge response on-device.
  • "received_at": The date/time, in UTC timezone, that the challenge response was submitted to the server/database.
  • "received_at_local_time": The date/time, in your organization's designated timezone, that the challenge response was submitted to the server/database.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us