Create and Launch a Scavenger Hunt in Proxi

Define the scavenger hunt as a clue-based experience where participants solve clues, travel to locations, check in, and earn points or prizes.

Use this format for events such as:

Confirm the participant journey before setup:

Create a Proxy collection of places first whenever possible.

Use the collection to populate the scavenger hunt locations.

If places are not already in a collection, add them directly in the scavenger hunt setup.

Recommended workflow:

From the Proxy dashboard, go to Scavenger Hunts.

Select New Scavenger Hunt.

Enter a name for the hunt.

Import the places from your collection.

Open the setup page and review the progress bar on the left to track completion.

Enter the scavenger hunt name.

Add a description that explains the experience.

Add a Terms and Conditions link if needed.

Rename the default check-in wording if desired.

Enable personal notes on places if participants should be able to record observations or clue-solving notes.

Set the start date and end date for the hunt.

Upload branding assets:

Choose the visit recurrence rule:

Choose how participants will verify location visits.

Select one or more check-in methods based on the event needs:

Decide whether photos are auto-approved.

Use combined methods if needed, such as geolocation plus photo or QR code plus photo.

If participants may be offline, allow photo upload later.

Set display options:

Configure hunt behavior:

Add a registration page header.

Write a short registration description.

Set the call-to-action button label, such as:

Decide whether participation requires payment or a donation.

Select registration form fields to collect:

Add custom fields as needed, such as:

Set up the registration method and complete the registration page before launch.

Open the Places tab.

Expand each location using the dropdown arrow.

Add the following for each place:

Assign higher point values to more difficult or harder-to-reach locations.

Download the completed place setup if needed for review or backup.

Add optional point-earning activities such as:

Assign point values to each activity.

Choose icons for each activity if desired.

Create awards and badges by defining:

Set success criteria based on:

Add a completion message that tells participants how to claim the reward.

Turn on the Registration toggle to make the registration page live.

Use the Share option to generate:

Share the hunt before the event to build registrations.

Keep registration open for as long as needed before participants begin solving clues.

Choose the delivery channel for each message:

Create blast messages for general communication.

Schedule blast messages for key moments:

Create automated messages for key participant actions:

Edit the subject line, reply-to email, and message body before activating each automation or message.

Go to the Participate section to review performance.

Track summary metrics such as:

Review participant-level data as needed.

Check location-level activity to see who visited each place.

Review the photo feed and download photos if needed.

Use available download options to export reports for analysis or recordkeeping.

Do not publish the hunt before all locations, clues, and registration settings are reviewed.

Be careful with participant data in the Participants view, since it may contain personally identifiable information.

If using geolocation or photo check-in, confirm the method works in areas with limited service.

If you enable point deductions for hints, make sure the scoring rules are communicated clearly to participants.

Review payment or donation settings carefully before turning on registration.

Build a collection of places first so scavenger hunt setup is faster and more organized.

Reuse a standard hunt template for future events to save time.

Use automated messages for registration confirmation and reward notifications to reduce manual follow-up.

Turn on the progress bar/checklist in setup to ensure no required step is missed.

Test the participant experience with a demo registration before launching publicly.

Use the photo feed and leaderboard only if they support the event goals, since they add engagement but may not be necessary for every hunt.