Creating a Challenge

Creating a challenge in OuterSpatial is a great way to engage with your existing OuterSpatial users and grow your user base.

Each challenge in OuterSpatial can include any number of tasks, each of which can be completed by visitors in one of two ways:

By responding to a "questionnaire" (which can be made up of one or more question)
By "checking-in" to an area, outing, point of interest, or trail

A few more notes about challenges:

Visitors can respond to challenge tasks even when they don't have a network connection. Responses created while offline get cached on-device and synchronized when a network connection is available.
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

Creating a Questionnaire Challenge

If you'd like to create a questionnaire challenge (a challenge that requires visitors to respond to one or more questionnaire to complete the challenge), your organization must be on the OuterSpatial enterprise tier and you'll need to work with our customer success team to get the challenge up-and-running.

To get started, open a ticket.

Creating a Check-in Challenge

Organizations on the team tier or higher can create and edit check-in challenges in OuterSpatial Manager.

To get started, click the "Challenges" link in Manager's left-hand navigation then click the "New Challenge" button in the upper, right-hand corner of the page.

Downloading Reports

You can download participant and response reports for your challenge on-demand in OuterSpatial Manager. Just select your organization, go to the "Challenges" section, click the "Actions" button next to the challenge you want to download reports for, and click either "Download Participants" or "Download Responses". This will download the corresponding report in CSV format.

Some notes about the fields that will come down in the "Responses" 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.