This page addresses frequently encountered questions regarding widget integration, configuration, and troubleshooting.
The Client ID is a 32-character unique identifier automatically generated during account provisioning. This identifier serves as the primary authentication mechanism for all widget integrations.
Key characteristics:
To obtain a Client ID, contact our Sales Team to initiate account setup.
Widgets integration follows the same pattern, with widget-specific details. For general info, see Getting Started Guide, for widget-specific details see documentation for specific widgets
For comprehensive integration examples and implementation patterns, refer to the Getting Started Guide.
All widgets expose an onTrack callback property that enables event-driven monitoring of widget lifecycle states (e.g. when widget has loaded) and user interactions.
For detailed explanation and usage examples see Tracking Guide.
For widget integration or runtime issues, follow a systematic diagnostic approach, as documented in the Troubleshooting Guide.
Widget names follow a namespaced naming convention (e.g., match.statistics, tournament.preview) and are required for both the addWidget() method and data-sr-widget attribute.
Resolution methods:
The Widgets Demo provides an interactive configuration interface for visual customization and code generation.
Customization options vary by widget type. Refer to individual widget documentation for available configuration parameters.
See Theming Guide and Customization Guide for advanced explanation.
Match IDs are numeric identifiers required for match-specific widget instantiation. These can be obtained through the Widgets Demo interface or via API endpoints.
Retrieval via Widgets Demo:
matchId parameter from the browser URLExample URL structure:
https://widgets.sir.sportradar.com/live-match-tracker#matches:(matchId:29524624,sportId:1)In this example, the Match ID is 29524624.
Licensing errors occur when authentication fails or when attempting to access products outside your subscription scope.
Common causes:
For detailed licensing troubleshooting and resolution procedures, consult the Licensing Errors.
Widget errors encompass runtime exceptions, configuration issues, and data availability problems.
Error categories:
For a comprehensive error code reference and resolution strategies, refer to the Widget Errors Documentation.
Live Match Tracker (LMT) coverage varies by sport, competition, and geographic region.
Coverage assessment:
Review the Coverage Page to determine LMT availability for specific sports and competitions.
Coverage tiers:
LMT-specific errors are frequently related to licensing constraints or coverage limitations.
Diagnostic approach:
Most LMT errors stem from licensing issues. Consult the Licensing Documentation for resolution procedures.
widget-name value.Example: The Match Statistics widget uses the name match.statistics
The Live Score column is the primary indicator of LMT availability. LMT coverage typically aligns with the Live Score coverage tier for each competition.