One player, from a Wyscout or Hudl match event export. Nobody watches the match — every number is counted from his row in the file.
The same key your Match and Player tools use — it covers every tool.
The file stays on this machine. Only the counted summary is sent.
What this tool is, in four steps.
.json. One match per file.A provider export records what a player did with the ball and what happened around him. It does not record what he did off it — where he stood, who he pinned, when he pressed and when he held. Those areas appear in the record table marked absent, and that is the Data Preview working, not failing.
So this is a screening document, not a verdict. It tells you whether a live viewing is worth the trip. Then it opens the right Player tool with his name already in it, so the questions the numbers raised are the ones sitting in front of you at the ground.
A provider export tells you what happened. It cannot tell you why, and nobody watched the match to write it. So the Data Preview carries a watch list: the questions the numbers raised and only someone watching can answer.
Every item on that list is answerable in the one match you are about to watch. Not a run of games, not a season — the ninety minutes in front of you. If a question needs a count across matches, it does not belong on the list.
A number with no eye behind it is a guess. An eye with no number behind it is an opinion. The watch list is how you get both.
When you have read the watch list, the button under it opens the Player tool you named, with the player already on it. You are not starting a recording from nothing — you are going to answer a list.