Multisports widgets
The multisport Game Tracker is a unique widget that has the capability to be used in different sports, so far and at the time of the creation of this document it has support for Football and Basketball.
This is possible because using the fixtureId (match identifier) the widget can identify the sport to display.
GameTracker Environments
UAT and Testing
https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker?fixtureId=<fixtureId>&productName=<productName>
https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker?fixtureId=<fixtureId>&productName=<productName>&layout=<layout>
https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker?fixtureId=<fixtureId>&productName=<productName>&widget=<widget>
Production
https://gsm-widgets.betstream.betgenius.com/multisportgametracker?fixtureId=<fixtureId>&productName=<productName>
https://gsm-widgets.betstream.betgenius.com/multisportgametracker?fixtureId=<fixtureId>&productName=<productName>&layout=<layout>
https://gsm-widgets.betstream.betgenius.com/multisportgametracker?fixtureId=<fixtureId>&productName=<productName>&widget=<widget>
Example
Layouts
The Multisport game tracker supports multiple layouts to give flexibility and changes the way how the customer wants to render the different component also is an advantage because is not required to create multiple customers on our database, with one customer is possible to set multiple layouts.
Regular Layout
The purpose of this layout is to render the game tracker with a tabs navigator, the idea is to use it on small or medium containers including mobile view.
When a tab has no data, that tab will be disabled until the data is available. When the tab is not supported on that sport, in that case, the tab will be hidden.
Note: iframe height should be at least 320px in order to have a properly functioning widget and its container should be at least 300px wide
Desktop Layout
The purpose of this layout is to render all the components in a single view, the idea is to use it on a large container.
When some data is not available to render the component, this will be hidden and the layout will adapt based on the available components.
Note: iframe height should be at least 580px in order to have a properly functioning widget and its container should be at least 900px wide
Stand Alone Layout
The purpose of this layout is to render different widgets on a stand-alone view. This is similar to having modular components, the customer can use the widget as a building block within their app or website. Can be used on large, medium, or small screens.
Integration details
The iframe code should be placed within the body of the webpage where you would like the widget to appear. The script below is an example that embeds a Football Game Tracker product.
Regular layout
Football
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker?fixtureId=9830657&productName=gsmdemo" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
Basketball
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker?fixtureId=9976439&productName=gsmdemo" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
Pitch tab for Basketball
Player Stats tab
Desktop layout
To render the desktop view is required to pass the query parameter layout with the value desktop
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker?fixtureId=9937582&productName=gsmdemo&layout=desktop" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
Stand-Alone Component
In case that requires a component, stand-alone needs to add the query param widget and define the component that will be rendered
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker/?fixtureId=9830657&productName=gsmdemo&widget=court" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
The components that can be used stand-alone are the following
ScoreBoard
To use the scoreboard stand-alone, the widget query parameter should be equal to the scoreboard
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker/?fixtureId=9830657&productName=gsmdemo&widget=scoreboard" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
Example URL:
Pitch
To use the Pitch stand-alone , the widget query parameter should be equal to the court
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker/?fixtureId=9830657&productName=gsmdemo&widget=court" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
Example URL:
Lineups
To use the lineup stand-alone , the widget query parameter should be equal to the lineups
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker/?fixtureId=9937582&productName=gsmdemo&widget=lineups" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
Example URL:
Play By Play
To use the play-by-play stand-alone, the widget query parameter should be equal to the playByPlay
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker/?fixtureId=9937582&productName=gsmdemo&widget=playByPlay" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
Example URL:
Team Stats
To use the team stats stand-alone , the widget query parameter should be equal to the teamStats
<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker/?fixtureId=9937582&productName=gsmdemo&widget=teamStats" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>
Example URL:
Supported components by Sport
Pitch | Team Stats | Player Stats | Play By Play | Lineups | |
|---|---|---|---|---|---|
Football | YES | YES | NO | YES | YES |
Basketball | YES | YES | YES | NO | NO |
Supported layouts by Sport
Regular | Desktop | Stand alone | |
|---|---|---|---|
Football | YES | YES | YES |
Basketball | YES | *YES (Needs additional support to show players stats instead of lineups while the lineups supports arrives) | YES |
Query parameters
Game Tracker
Name | Purpose | Mandatory | Notes |
|---|---|---|---|
| Dictates which configuration should be used to render the Game Tracker(customer) | Yes | It’s a string that would be provided by ops |
| Defines what content should be rendered. | Yes | Supports betgeniusIds and *sourceFixtureIds. *Feed to be used needs to be added to configuration |
| Defines the layout that will be displayed | No | The layout name would be provided by ops, the default layouts are default(tabs) or desktop |
| Chooses which locale should be used to load translations | No | Options are described in the translations section |
Game Tracker Stand-Alone View
Name | Purpose | Mandatory | Notes |
|---|---|---|---|
| Dictates which configuration should be used to render the Game Tracker(customer) | Yes | It’s a string that would be provided by ops |
| Defines what content should be rendered. | Yes | Supports betgeniusIds and *sourceFixtureIds. |
| Chooses which locale should be used to load translations | No | Options are described in the translations section |
| Define the stand-alone component that will be used | Yes | Only work when need stand-alone components |
Configuration
In order to have a working widget a configuration must be created, this is handled by the operations team.
Here you can take a deep dive and understand how the configuration model works. This is mostly for developers since operations should interact with this through UI Multisport GameTracker Configuration
Translations
In order to use any other than the default language, it needs to be translated.
Sport | Default Value |
|---|---|
Football |
Available Translations
default (english)