Multisport GameTracker and examples

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, American Football (CFL), Tennis and Basketball.

This is possible because using the fixtureId (match identifier) the widget can identify the sport to display.


GameTracker Environments

Features by sport

Components

 

Pitch

Team Stats

Player Stats

Play By Play

Lineups

 

Pitch

Team Stats

Player Stats

Play By Play

Lineups

Football

YES

YES

NO

YES

YES

Basketball

YES*

YES

YES

YES

NO

American Football

NO*

YES

YES

YES

NO

Tennis

YES

YES

NO

NO

NO

Layouts

 

Regular

Desktop

Stand alone

Side by Side

 

Regular

Desktop

Stand alone

Side by Side

Football

YES

YES

YES

YES

Basketball

YES

NO

YES

YES

American Football

YES

NO

YES

NO

Tennis

YES

NO

YES

YES

If the widget receives a fixtureId for an unsupported sport, it won't be able to load data and will show an error instead. For other sports please use the Multisport Scoreboard

Layouts and integration

The Multisport game tracker supports multiple layouts to provide flexibility that the customer can choose how to render the different components. A single configuration can be used to show the widget in several layouts.

Regular

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. This is the default layout. Tabs can be removed and/or added on our side.

EXAMPLE LINK

Integration example

<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>
  • Integration looks the same for all supported sports, the important part is to pass the right fixtureId

  • When a tab has no data, that tab will be hidden until the data is available. When the tab is not supported on that sport, the tab will remain hidden.

  • Dimensions can be modified as long as it isn’t smaller than 300x300

  • Make sure you set the right productName

Screenshots

image-20240202-203835.png

 

Desktop

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 or the whole window.

EXAMPLE LINK

Integration example

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>
  • At the moment this only works for Football

  • When some data is not available to render the component, it will be hidden and the layout will adapt based on elements that can be displayed properly

  • Dimensions can be modified, iframe height should be at least 580px in order to have a properly functioning widget and its container should be at least 900px wide

  • Make sure you set the right productName

Screenshots

Side by Side

This layout renders a pitch/court component alongside other tabs such as team stats and lineups.

When the available space in terms of width reaches a certain breakpoint, it will behave just like regular layout does.

EXAMPLE LINK

Integration example

To render the desktop view is required to pass the query parameter layout with the value sideBySide

<iframe id="gsm-game-tracker" scrolling="no" src="https://gsm-widgets-uat.betstream.betgenius.com/multisportgametracker?fixtureId=9937582&productName=gsmdemo&layout=sideBySide" width="100%" height="320px" style="border: 0; allowtransparency"></iframe>

Screenshots

 

 

 

Stand Alone

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 example

In order to use the stand-alone version, the query param widget is passed with the component that will be rendered as value.

ScoreBoard

To use the scoreboard stand-alone, the widget query parameter should be equal to the scoreboard

Pitch/Court/Field

To use the Pitch stand-alone , the widget query parameter should be equal to the court

Lineups

To use the lineups stand-alone , the widget query parameter should be equal to the lineups

Play By Play

To use the play-by-play stand-alone, the widget query parameter should be equal to the playByPlay

Team Stats

To use the team stats stand-alone , the widget query parameter should be equal to the teamStats

 

Query parameters

Game Tracker

Name

Purpose

Mandatory

Notes

Name

Purpose

Mandatory

Notes

productName

Dictates which configuration should be used to render the Game Tracker(customer)

Yes

It’s a string that would be provided by Genius Sports.

fixtureId

Defines what content should be rendered.

Yes

Supports Genius Sports fixture IDs and customer fixture IDs.

To use the customer fixture IDs, the IDs need to be sent to Genius Sports for mapping.

layout

Defines the layout that will be displayed

No

The layout name would be provided by Genius Sports, the default layouts are default(tabs), sideBySide or desktop

Should not be used alongside widget

widget

Define the stand-alone component that will be used

No

Allows usage of stand alone component. Should not be used alongside layout

culture

Chooses which locale should be used to load translations

No

Options are described in the translations section

Translations

 

  • To utilize this feature, append the parameter &culture={language-code} to the URL. The {language-code} should adhere to this ISO format. If translation files for the specified language are available, they will be used; otherwise, the default language will be en-GB. To utilize a language other than the default, it must first be translated.

  • Each supported language in the system has a dedicated file containing translations for all available sports. Note that the coverage for a specific sport may vary depending on the language.

  • This applies to nearly all text within the widget, with the exception of team names, competition names, and play descriptions for American football fixtures.

  • Language management is global across all customers, meaning that no customer-specific translations are permitted; all customers will experience the same language settings.

  • Each supported sport in the multisport game tracker has its own unique structure or set of strings that require translation.

  • Every translatable string follows this format, where customers should only modify the text within the translation key. Descriptions are often provided to clarify which label each string corresponds to.

  • Given the global nature of languages, we already provide support for a wide range of them. If you have inquiries regarding the current status of a specific language, please feel free to ask. Additionally, if there are any files missing that need to be completed, or if you require the most recent starting file for a particular language, do not hesitate to request that information.

Sport

Default

Sport

Default

Football

 

 

Basketball

 

 

American football (CFL)

 

 

Tennis