Hyper LiveScore
Quick Start
Go to ENGAGE → Hyper → LiveScore
Find your fixture using filters or search
Click the fixture to open Message Stream
Filter by incident type or Message ID
Copy Message ID for support or investigation
1. What is Hyper LiveScore?
Hyper LiveScore is a self-serve investigation tool in Arena360 that shows exactly what Hyper sent for any match in near real-time.
What you can see:
What was sent (incident type & values)
When it was sent (timestamps & ordering)
How certain it was (confidence score)
Message ID for reference and troubleshooting
It turns raw live incidents into a practical investigation experience that improves transparency, speeds up troubleshooting, and reduces escalation to engineering.
When to Use Hyper LiveScore
Typical scenarios:
A customer claims a goal arrived late → verify exact send time
Trading wants to confirm which signal suspended a market → check confidence scores
Support needs proof of what was sent at a specific second → copy Message ID
Integration team sees a mismatch vs their ingestion → compare incident values and timing
Compliance requires audit trail for a disputed incident → export evidence
2. How to Access
Navigation: ENGAGE → Hyper → LiveScore

Access Requirements:
Arena360 access under relevant Account
Active Hyper LiveScore entitlement
3. Fixture Selection
The Fixture List is your starting point to find the match you want to investigate.
3.1 Sport Types Panel
Filter fixtures by sport using the left panel. The number shows available fixtures per sport.
Features:
Click any sport to filter
Expandable for location/competition drill-down (> arrow)
Real-time fixture counts

3.2 Filters & Search
Use the top filter bar to narrow results:
Filter
Purpose
Fixture ID / Team Name
Text search
Start Date
Date picker (Apply/Clear)
Fixture Status
Multi-select dropdown
Clear all
Reset all filters

Start Date Picker
Click Start Date dropdown
Navigate month using arrows
Select date (highlights blue)
Click Apply

Fixture Status
Multi-select with "Select All" option. Click Apply to filter.

Available Statuses:
Status
Description
NSY
Not Started Yet
In Progress
Match currently live
Finished
Match concluded
Cancelled
Match cancelled
Postponed
Postponed to later date
Interrupted
Match interrupted
Abandoned
Match abandoned
Lost Coverage
Data feed lost
About to Start
Starting imminently
3.3 Results Table
Each row represents a fixture. Click any row to open Message Stream.
Columns:
Column
Description
Example
Start Date
Scheduled start
2026 Jan 20, 20:00
Location
Country/region
International 🏴
League
Competition name
UEFA Champions League
Fixture ID
Unique ID with #
#17470784
Home / Away
Team names
Olympiakos vs Leverkusen
Status
Current status
Finished
Table Features:
Sortable columns (click headers)
Pagination (30/50/100 per page)
Clickable rows

4. Message Stream
Message Stream shows every incident Hyper sent for the selected fixture.

4.1 Message Stream Table
Each row is a single incident message.
Columns:
Column
Format
Description
Send Time
HH:MM:SS:MS
When Hyper sent the message
Incidents
Icon + Text
Incident type with icon
Values
Varies
Incident data (scores, players, stats)
Confidence
Percentage
System confidence at send time
Game Time
MM:SS
Match clock when incident occurred
Message ID
#UUID
Unique message identifier
4.2 Filters
Narrow down incidents quickly:
Filter
Type
Usage
Message ID
Text search
Find specific message
Incidents
Dropdown
Filter by incident type
Send time
Sort
Sort by timestamp
Confidence
Dropdown
Filter by confidence %
Clear all
Button
Reset all filters
Best Practice: Use Incidents filter to focus on specific event types (goals, substitutions, etc.)

4.3 Sorting by Send Time
How to sort:
Click Send time dropdown in filter bar, OR
Click Send Time column header
Toggle between ascending (oldest first) and descending (newest first).
4.4 Copy Message ID
Every message has a unique ID for reference.
How to copy:
Locate Message ID in rightmost column
Click directly on the Message ID
Automatically copied to clipboard ✓

When to use Message ID:
Support tickets - Reference specific messages
Audits - Track incidents in your systems
Cross-referencing - Match with backend logs
Debugging - Investigate discrepancies
Last updated
Was this helpful?