Live Match Tracker for a Betting Site: 2D vs 3D, and When It Increases In-Play Bets
What a live match tracker shows next to the markets, how to choose between the 2D and 3D modes, when it helps in-play betting, and how to embed it without an empty block.
A live score tells the user what has already happened. A live tracker shows what is happening right now: where the ball is, who is pressing, and why the odds just moved. That is the whole reason to add one. It turns a live section from a table of numbers into something people watch, and it does so without video rights or heavy streams.
Below: what the user actually sees, how to choose between the 2D and 3D modes, when a tracker helps in-play betting and when it doesn’t, how it gets onto a page in four steps, and the mistakes that make it look broken.
What “1–0, 67th minute” hides
Picture a user on the live page of a football match. The line says 1–0, 67th minute. Next to it, the odds on the next goal have just shifted. Why? The text gives no answer.
Now the same moment with a tracker above the markets. The trailing team has pinned the leaders in their own half. The ball is on the edge of the box, an attack is building on the left, a corner has just been marked on the event feed. The user does not need anyone to explain the odds movement — they can see the pressure.
This is the gap a tracker closes. A score is a result. A tracker is the context around it: rhythm, territory, danger. For a betting product that context sits right next to the bet slip. For a live-score service it is the difference between checking a number and staying on the page.
What the viewer actually sees
Live 3D Tracker draws the playing field or court and plays the match on it as a visual scene. Depending on the sport, the user sees:
- the ball position and the direction of attacks;
- dangerous moments as they build up;
- score, timer, and periods;
- match events: shots, cards, serves, possession changes;
- key statistics alongside the action.
The tracker can run in a 3D or a 2D mode where available, adapts its width to the container, and has a separate mobile layout. You can switch it to the interface language of your site; team names come from the data provider and may stay as they are.
What the tracker is not: it is not a video stream and not a data source. It visualizes match data that it receives for a selected live match. The list of matches, odds, and statistics still come from your sports line.
Score, tracker, or video: what each one gives
| Bare score | Live 3D Tracker | Video stream | |
|---|---|---|---|
| What the user understands | The result only | Result, territory, attacks, danger | Everything, if the user keeps watching |
| Rights | Not needed | Part of the service | Separate broadcasting license |
| Weight on the page | Minimal | One embedded block | Heavy stream |
| Mobile and slow internet | Works | Works, compact layout | Often struggles |
| Keeps users near the markets | Weakly | Yes, sits next to the bet slip | Pulls attention away from them |
The tracker is the middle ground. It does not compete with video, but it covers the many matches where video is unavailable or simply not worth the cost, and it keeps the user on your page instead of a third-party stream.
2D or 3D: which mode to choose
The tracker has two display modes. The standard connection lets you pick the one available for the sport with the view parameter, view=2d or view=3d, and switch it later without reloading the page.
| 2D | 3D | |
|---|---|---|
| What the user sees | A top-down pitch or court with the ball, zones and events | The same match as a three-dimensional scene |
| Reads best in | Small blocks: match cards, side panels, phones | Large blocks: the match page, a live centre |
| Strength | Clarity at a glance: where the ball is and who is attacking | Presence: closer to watching the game |
| Typical place | Next to the bet slip, in a list of live matches | The top of a single match page |
Three rules of thumb. Use 2D where space is tight or several matches share the screen. Use 3D as the main block of a match page, where it has room. And if your users are split, give them a switch: the update() method changes view on the fly. Which modes exist for a sport is easiest to check on the demo page before you design the layout.
When a tracker helps in-play betting, and when it doesn’t
A tracker doesn’t create bets by being on the page. It helps in specific situations, and it’s worth knowing which ones before you move your layout around it.
It helps when:
- There’s no video for the match. That’s most matches. The tracker is then the only picture of the game next to the markets.
- The player would otherwise leave to see what’s happening. A second tab with a stream or a live-score site is a player who may not come back. A tracker keeps the game and the bet slip on one screen.
- The odds move and the reason isn’t visible. Pressure, dangerous attacks and set pieces explain a price change better than a number does, and a player who understands the move decides faster.
- Sessions are long and on a phone. The compact layout works on a slow connection where video struggles.
It doesn’t help when:
- the page is prematch only, or the match has no
zp; - the block sits far below the markets, where nobody scrolls during a live match;
- video is already the main element of the page; then the tracker belongs on the matches without video;
- your users bet from a list without opening a match; then a small 2D block in the list does more than a large 3D one on a page they don’t visit.
The size of the effect depends on the sport, the audience and where the block sits, so measure it on your own pages. Show the tracker to half of the visitors of match pages where zp is present, and compare three numbers over a couple of weeks: time on the match page, the share of visitors who open the bet slip, and bets per live session.
Where the tracker earns its place
Sportsbook live sections. The user sees the game and the markets on one screen. They do not need to open another tab to understand why a price changed.
Live-score and statistics services. A match page with a tracker becomes something to watch, not just to check. The visit lasts longer than a glance at the score.
Sports media and prediction sites. A live block under a preview or a forecast keeps readers on the article while the match is on.
Mobile apps. The compact layout fits a phone screen better than a stream and does not drain traffic.
Where it adds little: prematch pages (the tracker works only for live matches) and pages without a live section at all.
Which matches can show the tracker
The tracker currently supports 17 sports, including football, ice hockey, basketball, tennis, baseball, volleyball, rugby, handball, table tennis, cricket, darts, and esports. Each has a numeric ID that you pass in the sport parameter; the full table is in the tracker integration guide.
But the sport is only the first condition. The real switch is a single field in the match data. Every match in the sports line has a zp field described in the Sport Line API match model. If it contains a number, that number is the tracker ID. If it is null, there is no tracker for this match, and the block should not appear.
So the rule for the interface is simple. Show the tracker only when all three are true:
- the match is live;
- the sport is included in your plan;
zpis notnull.
If the sport is not in your plan, the tracker itself displays a message saying so. That is a plan question for the manager, not a bug in your code.
How it gets onto the page: four steps
- Get a key for your domains. Send the manager your production domain, a test domain, and
localhostif the developer will integrate locally. The key works only on those domains. - Connect the sports line. The tracker does not provide a list of matches. Take a live match from the line and read its
zp. - Pass
zpasgameidtogether with the sport ID and the interface language. - Choose the embedding method. A plain
iframeis enough for most pages:
<iframe
src="https://bet-embed-sport-tracker.vercel.app/?key=pk_live_yourkey&gameid=745829876&sport=1&lang=en"
style="width: 100%; height: 360px; border: none;"
title="Live tracker"
></iframe>
If the page needs to switch matches without a reload, use the embed.js loader and call update() with the new gameid and sport. The recommended height is 360–420 px on desktop and 220–280 px on mobile.
Standard options — language, height, mobile layout, your logo, 2D or 3D mode, match switching — need no custom development. Colors, icons, animations, or a full redesign to your brand can be done separately on request.
Mistakes that make the tracker look broken
- Showing the block for every match. If
zpisnull, the user gets an empty frame. Check the field first and show statistics instead, or hide the block. - Forgetting the test domain. The key is tied to domains. On an unlisted domain or
localhostthe widget returns a403error, and it looks like a broken integration. - Calling
update()too early. Right afterinit()the widget inside the iframe may not be ready. Wait for theREADYmessage before switching matches. - Sending the wrong sport ID.
gameidfrom a basketball match withsport=1will not work. Take the sport ID from the same match record. - Fixed desktop height on phones. 400 px of tracker on a phone pushes the markets off the screen. Use the mobile height range.
- Keeping the tracker after the final whistle. The tracker works only for live matches. When the match ends, replace it with the final score and statistics.
How to try it with SportAPI
Start with the demo page, which shows how the Live 3D Tracker looks for each supported sport. The demo uses no real live data — it is about the look.
Then test it on your own pages: the manager will issue a key for your test domain, and you can embed the tracker into a real live section next to the Sport Line API data you already use or plan to use. Pricing starts from $50 per month for one sport, so you can launch your key sport first and see how users react before expanding coverage.
If the tracker does not appear, the cause is almost always one of five things: the domain is not added to the key, the key is disabled, the match is not live, zp is null, or the sport ID is wrong. Send support the page link, the gameid, the sport ID, and a console screenshot, and they will tell you which one.
FAQ
Does the tracker replace a video stream?
No. It shows the course of the match as a visual scene, not the real picture. Its strength is that it works where video is unavailable, unlicensed, or too heavy, and keeps the user on your page.
Can I use the tracker without the SportAPI sports line?
No. The tracker needs a gameid, and that value comes from the zp field in the sports line data. Without the line there is no way to know which matches have a tracker.
Does it work for prematch matches?
No. The tracker shows live matches only. On a prematch page, show the line, team form, or statistics instead.
Will the tracker match my site’s design?
The standard connection already lets you set the language, height, mobile layout, logo, and 2D or 3D mode. Colors, icons, animations, or a complete redesign are evaluated separately based on your requirements.
Why do team names stay in English on a localized page?
The lang parameter changes the interface and event names. Team names come from the sports data provider and may not be translated.
Is 2D or 3D better on a phone?
2D reads better in a small block, so it’s the safer default for match cards and narrow screens. 3D earns its place as the main block of a match page. Both use the mobile layout, and you can let users switch.
When the tracker is worth adding
Add it if your product has a live section and your users make decisions during the match — bettors, fans following several games, readers of live coverage. In those cases the tracker turns a number into a story and keeps people next to your markets and content. Skip it if you work only with prematch or historical data.
Ready to see it on your own pages? Message the SportAPI manager on Telegram with your domain and the sports you need, and get a key to test the tracker on real live matches.