Test & go live
Walk through the full lifecycle in the environment you intend to launch.
On this page
Prerequisites
- A working integration in a test environment.
- A test participant and an eligible, approved quest.
Step 1: Verify configuration
- The platform is accepted, active and configured with the intended allowed origins / package.
- The public key, embed UUID, participant secret and API URL all belong to the intended environment.
- Private credentials are stored only on your backend. Participant sessions are authenticated and not publicly cached.
- The platform’s appearance changes are published and visible in your integration.
Step 2: Walk through as a participant
Sign in as a test participant and obtain a session from your own backend.
Open the widget, confirm the expected feed and start a quest of each format you intend to offer.
Fulfill the actual timer, question, visit or growth evidence. Confirm completion and reward state match the API.
Reload and check the recorded completion and balance. Retry a submission to confirm it does not grant twice.
Test token expiry, logout, account switching, network failure and an ineligible participant.
If using lotteries, test a confirmed entry, an uncertain response retry with the same idempotency key, results and claims.
If using webhooks, verify signatures, deduplication, durable processing and a replayed delivery.
Step 3: Check your production placement
- Use HTTPS and review the real host’s frame, API, font and media policies.
- Test keyboard navigation, readable text, narrow screens, long content and native back / close behavior.
- Keep API failures visible and recoverable. Do not replace a rejected result with a success animation.
- Check quest and platform analytics with known test outcomes. Public quest totals may aggregate across placements; platform-scoped stats answer a different question.