Hyper LiveScore

Quick Start

1. Go to ENGAGE → Hyper → LiveScore
2. Find your fixture using filters or search
3. Click the fixture to open Message Stream
4. Filter by incident type, Message ID, or Incident Key
5. Copy a Message ID or Incident Key for support or investigation

---

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)
• Which messages belong to the same incident (incident key)
• Whether each message was delivered to your subscription (Sent indication)
• 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.

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

---

How to Access

Navigate to ENGAGE → Hyper → LiveScore in Arena360.

Requirements:

• Arena360 access under relevant Account
• Active Hyper LiveScore entitlement

---

Fixture Selection

The Fixture List is your starting point to find the match you want to investigate.

Sport Types Panel

Filter fixtures by sport using the left panel. The number shows available fixtures per sport. Click any sport to filter; use the > arrow for location/competition drill-down.

Filters & Search

Filter	Purpose
Fixture ID / Team Name	Text search
Start Date	Date picker (Apply/Clear)
Fixture Status	Multi-select dropdown

Available Fixture 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

Results Table

Each row represents a fixture. Click any row to open Message Stream.

Column	Description
Start Date	Scheduled start
Location	Country/region
League	Competition name
Fixture ID	Unique ID
Home / Away	Team names
Status	Current status

Table supports sortable columns, pagination (30/50/100 per page), and clickable rows.

---

Message Stream

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

Message Stream Table

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
Period	—	Game phase the incident occurred in
Message ID	#UUID	Unique message identifier
Incident Key	string	Shared ID for all messages belonging to the same incident
Sent	Icon	Delivery status of the message to your subscription

Incident Key

A single incident often produces more than one message as it is confirmed from different sources (or providers), re-sent, or cancelled. The Incident Key groups those messages: every message reporting the same incident shares one key, so you can follow one incident instead of reading the stream line by line. A change in value is a new incident with its own key — 0:1 and 1:1 are separate incidents.

Use the Incident Key to trace one incident end to end, search to isolate every message for that incident, copy the key for support and cross-referencing, or group messages by incident when you export to CSV.

Cancelled Incidents

When an incident is cancelled after it was sent, it remains visible in the Message Stream for transparency — but is visually marked so it's immediately clear it is no longer valid.

How cancelled incidents appear:

• The entire row is grayed out — text, icons, and values are all dimmed
• A Cancel badge appears on the right side of the row

This applies consistently across all incident types (goals, fouls, cards, and others). No incidents are removed from the stream — cancelled ones stay visible so you have a full audit trail of everything that was sent.

Sent Indication

The Sent column shows whether each incident message was delivered to your subscription. It gives you a per-message delivery record without leaving the tool.

• Delivered — the message reached your subscription
• Failed — delivery did not succeed; hover the indicator to see the reason
• Neutral — no delivery record for the message

The Sent column appears only for fixtures in your subscription. For fixtures you are not subscribed to, there is no delivery data, so the column is hidden.

Filters

Filter	Type	Usage
Message ID / Incident Key	Text search	Find a specific message, or all messages sharing one incident key
Incidents	Dropdown	Filter by incident type
Send time	Sort	Sort by timestamp
Confidence	Dropdown	Filter by confidence %

Copy Message ID

Every message has a unique ID. Click directly on the Message ID in the rightmost column — it is 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

Incident Key works the same way — click the value to copy it to your clipboard. Search the copied key to pull up every message reporting that same incident.

Download Message as JSON

Hover over any message row and click the download icon. The file saves as JSON to your device.

Export to CSV

Available on both the Fixture screen and Message Stream screen. Click the Download button → a CSV file with all fixtures or incidents downloads to your computer. The Message Stream CSV includes the Incident Key column alongside Message ID, so you can group messages by incident in your own tools.