Overview

Virtual Stadium is a social engagement platform tailored for the betting space where bettors can interact, gather insights and discover new betting opportunities.

#Features

• Match and tournament level chat rooms where bettors can interact and form communities.
• Comprehensive betting tools such as Bet Sharing, Bet Copying and Flash bets generated by live match events.
• Live action visualization via Live Channel Online streams and Live Match Tracker.
• VIP chat which gives users the opportunity to interact with influencers and VIPs.
• AI assisted moderation tools such as Copilot, Autopilot, anti-spamming and blacklisted words that provide a simple way of moderating hundreds of channels.
• Roles and permission based moderation system.
• Extensive analytics tools.

---

#Integration Timeline Overview

The Virtual Stadium integration follows a structured three-phase approach with responsibilities split between Sportradar Effort 🔵 and Client Effort 🔴. The entire process can take as little as 2-3 weeks when using Sportradar odds and opting for the hosted adapter integration. However, the timeline may extend to 1-3 months when incorporating mixed or third-party odds or implementing a custom adapter integration.

---

#Phase 1: Initiation (1-2 Days)

#Communication Channel Setup

Your sales contact person will initiate a shared communication channel via Slack invite to facilitate real-time collaboration between teams. This channel serves as the primary medium for answering questions, exchanging required information, and providing ongoing integration support.

#Language Support Requirements

Specify the languages you intend to support in your Virtual Stadium implementation via the communication channel.

#JWT Authentication

Some Virtual Stadium features require validated data integrity from your backend to prevent misuse by end-users or malicious actors. You'll need to create and sign a JSON Web Token (JWT) using a public/private key pair. The public key will be shared with via the communication channel to validate tokens signed by your private key.

#Moderation Setup

The integration team will set up a moderation client for your organization during the integration process. This client is secured using your JWT authentication credentials (see Authentication), ensuring only authorized users from your organization can access it. A Supervisor role will be assigned to your designated administrator, giving them the ability to manage brands, operators, channels, invite team members, and configure AI-assisted moderation tools.

---

#Phase 2: Technical Kickoff Meeting (1 Hour Meeting)

Your sales contact person will organize a kickoff meeting with your technical team and Sportradar's integration team. This meeting serves as the formal start of the technical integration process and ensures both teams are aligned on requirements, timelines, and next steps.

#Supervisor Access Setup

The moderation client must be associated with a user assigned the supervisor role. Please be prepared to provide the email address for this supervisor. During the meeting integration team will issue invitation to the provided email to finish the Moderation setup process.

#Introduction Session

During the Introduction Session, the integration team presents Virtual Stadium modules, explains what the adapter is and how it is used to gather the required data, demonstrates Moderation UI capabilities, outlines the recommended integration process, and answers outstanding questions.

#Adapter Type Decision

The integration team validates the client's odds sources and recommends the adapter type. Using Sportradar odds points to the hosted adapter for the fastest, easiest path, while mixed or third-party odds require the own implementation adapter.

---

#Phase 3: Setup

After completing Phase 1 (Initiation) and Phase 2 (Technical Kickoff), the Phase 3 (Setup) begins with post-kickoff setup tasks before proceeding to Phase 4 platform-specific integration.

#Brand & Operator Setup

The Supervisor will set up your brand and operator structure in the moderation interface. This typically takes ~1 day and establishes the organizational hierarchy for managing channels and moderation across different languages or regions.

#Supervisor and Moderator Invitation

The Supervisor will invite moderator team members who will handle day-to-day content moderation. Moderators are assigned to specific operators based on language proficiency and regional knowledge.

#Channel Setup

#Manual Creation

To get started and explore available options, we recommend the Supervisor manually create channels through the moderation interface. This is the recommended approach for initial testing as it allows you to see all configuration options and understand the channel structure.

#Backend Automation

For production environments, consider implementing a backend solution to automate channel creation. Common approaches include creating channels ahead of time using scheduled jobs (e.g., cron jobs before matches begin) or generating them on-demand when users first access a match or event. Automating channel creation helps maintain consistency and reduces manual overhead as you scale.

#JWT Creation

Your development team will implement JWT token generation on your backend using the RSA keys shared during Phase 1. This enables secure authentication for your users and moderation team.

#Phase 4: Integration

After completing the post-kickoff setup, you can proceed with your platform-specific integration: