Experience Configuration
Configure saved iframe experiences in Phoenix Prediction admin
An experience is a saved iframe configuration for your operator. It lets the same Phoenix Prediction embed product appear as a homepage module, full-page prediction area, sidebar, or lobby widget without changing the launch contract.
Template and Experience
template is the base UI design. experience is a configured instance of that template.
template: classic
experiences:
homepage
compact-sidebar
casino-lobbyThe first Phoenix Prediction template is classic.
Configurable Areas
| Area | Examples |
|---|---|
| Theme | Mode, primary color, background, surface, text, radius, font |
| Features | Search, topics, comments, activity, leaderboard, portfolio |
| Layout | Start page, feed style, bottom nav, bet panel, mobile bet mode |
| Market filters | Category filters, topic filters, featured-only views |
| Bridge behavior | Auth, deposit, token refresh, allowed origins |
| Compliance | Terms, privacy, responsible gaming, support URLs |
| Sizing | Container or auto sizing |
Experience Keys
Experience keys are lowercase slugs. Use stable names because they are part of the iframe URL.
Good examples:
homepage
main-lobby
sports-tab
mobile-fullscreenAvoid putting market names, campaign names, or dates in the key unless the experience is genuinely temporary.
Publishing Changes
Experience changes affect future iframe loads. Players who already have the iframe open may need a refresh before they see a new theme or layout configuration.
Use staging or a non-production experience key for review before changing the main production key.