Test the hunt
Check the route on real devices after you publish, before the campaign starts, and catch issues before participants arrive.
Test a Treasure Hunt end to end before participants arrive. You can't open a draft campaign, so publish it first, then walk the full hunt yourself before the start date using a practical device checklist.
Prerequisites
- The hunt and at least one object are configured.
- The final or near-final assets are in place.
- You have access to the phones or tablets participants are most likely to use.
Publish first, then test before the start date
You can't open a draft campaign. Publishing runs validation (which can block release until you fix any errors) and makes the hunt ready, but participants can only join from the start date. Use that window to test the full hunt yourself.
What to test before the start date
At minimum, test:
- the hunt entry point
- at least one object link or QR code
- the 3D or augmented-reality display on a real device
- the interaction flow for each question type you use
- the progression logic, whether participants collect in any order or follow a fixed route
- the completion rule and unlock message
Test the hunt
Open the published hunt to test it
After you publish, open the hunt and walk it yourself before the start date.
This lets you test the participant journey before participants can join.
Check the participant route from start to finish
Start at the hunt entry point, then move through the route exactly as a participant would.
Confirm:
- the banner, title, and subtitle look right
- the route makes sense
- each object opens correctly
- the final completion state appears as expected
Test the experience on real devices
Test on supported mobile devices and at least one device that cannot launch augmented reality.
- When to do this: any hunt that uses AR First, where the object appears in the participant's camera view.
Confirm:
- supported devices show the augmented-reality path correctly
- unsupported devices still open the in-page viewer
- the AR button is absent where augmented reality is not available
Verify the question logic
Test every interaction type you use:
- Direct should collect without answer fields
- Multi Choice should accept exactly one correct option
- Text Answer should validate the expected answer
Also test any hunt completion question you added in Treasure Hunt Configuration.
Test the route rules in the venue
Use the actual object links or QR codes you plan to distribute and walk the route in the real space.
For fixed-route hunts, make sure later steps stay locked until the earlier ones are completed. For any-order hunts, make sure each stop still feels clear even when participants start from different places.
Recheck scan and permission behavior
Test the permission flow on the device from a participant's point of view.
- When to do this: any hunt that depends on printed QR codes or camera-based augmented reality.
That means confirming:
- the camera can scan the printed QR code reliably
- the browser or device allows camera access where needed
- participants are not blocked by confusing permission prompts
Quick launch-readiness checklist
The hunt is usually ready to publish when:
- every object opens correctly
- the 3D or augmented-reality object loads on the intended devices
- the order and completion rules behave as designed
- the live QR placements make sense in the venue
- no unanswered validation errors remain
Related
Print & place QR codes
Prepare the final hunt and object QR set for the venue.
Publish a hunt
Run the validation flow and make the hunt live when testing is complete.
3D/AR rendering issues
Troubleshoot missing AR buttons, asset problems, and device support issues.
Object placement — QR codes in the venue
Improve the route design before you finalize the physical setup.