Getting Solid Player Stats From a Blue Jays-Tigers Game
The first thing most people get wrong is where they look for stats. They go to the main box score page and think they are done. That gives you batting average, home runs, RBIs — the usual stuff. It does not tell you why a play happened or what the pitcher was actually doing. If you want stats that mean anything, you need to go past the surface layer. When a game like this comes up, especially one framed as a "Battle For Supremacy," the stats available online are all over the place. Some sites show tracking data from Statcast, others use older pitching metrics, and a few just copy-paste from MLB's official feed without any cleanup. The result is a mess if you are trying to compare anything meaningful between players. My approach is to pull from at least three sources and cross-reference. I started doing this seriously after a 2023 playoff chase when I was running a fantasy platform and nobody could agree on who was actually driving in runs versus who was just getting unearned credit from fielder choices. That cost us about two weeks of arguing with users. I stopped trusting single-source dashboards after that.
Where to Find the Data
MLB.com's Gameday page is the baseline. It has the official play-by-play and the standard stat lines. The problem is it defaults to whatever the scorer decides counts, and scoring decisions can vary. A ground ball that would be a hit in one ballpark gets scored as an error in another because the fielder looked sluggish. Statcast data comes from the trackman and hawk-eye systems. You get exit velocity, launch angle, sprint speed, and pitch movement. This is the raw tracking info MLB collects. It shows up on MLB.com under the Statcast tab, on Baseball Savant, and on several third-party sites. The catch is that Statcast data only exists for games played after the systems were installed across all stadiums, which is most recent games but not everything going back in history. BrooksBaseball.net is probably the most useful free resource for pitch-level detail. It breaks down every pitch by movement, location, and type. The graphs are ugly but the data is clean. You can filter by batter, pitcher, count, and even game situation. I use it every time I need to understand why a specific hitter struggled against a particular pitch type in a high-leverage moment.
What Actually Matters in These Matchups
People obsess over batting average and home runs. Those numbers tell you nothing about consistency or matchup value. When I evaluate a Blue Jays batter against Tigers pitching, I look at strikeout rate, whiff rate, and chase rate. A player with a .240 average but a 22% whiff rate against breaking balls is a completely different risk than someone with a .260 average and an 11% whiff rate. For pitchers, the metric that matters most is stuff+ and location+. These are adjusted ratings that account for the quality of contact allowed, not just ERA. An ERA can lie because of defense, ballpark, and luck on balls in play. Stuff+ measures how good a pitcher's pitches are regardless of outcome. Location+ measures how well they place them. Both are available on Baseball Savant and give you a much clearer picture than standard stats. I ran into a specific edge case last season with a reliever whose ERA was 4.87 but whose stuff+ was in the 90th percentile. The problem was he was getting hit hard on ground balls because of a defensive alignment issue in his bullpen. His peripheral numbers were fine. The walk rate and strikeout rate told the real story. I learned to ignore ERA for bullpen matchups entirely and focus on walk rate plus contact quality allowed.
Get the Full Details
How to Pull the Stats Yourself
Go to Statcast search on MLB.com. Set the date range to the specific game. Filter by team and opponent. You will get a table with every batted ball event, pitch type, velocity, and location. Export it if you need to work with it in a spreadsheet. On BrooksBaseball, select the teams and date. It gives you a pitch-by-pitch breakdown with visual spin maps. This is where you find things like how much a slider moved horizontally for a specific pitcher, or whether a hitter was consistently late on inside fastballs. The official MLB app has a game center section that shows advanced stats for each batter and pitcher in real time. It is not as detailed as the web versions but it is convenient if you are watching the game live and want quick context.
Common Pitfalls
One big mistake is comparing players across different ballparks without adjusting for park factor. The Blue Jays play in Toronto, which is a pitcher-friendly park due to the wind patterns and dimensions. The Tigers play in Detroit, which leans slightly hitter-friendly. A home run in Toronto is worth more than a home run in Detroit when you are evaluating true offensive value. Another issue is small sample size. One game, even a high-profile one, does not establish a trend. If a Tigers pitcher allowed three home runs in a single start, that does not mean his stuff declined. It could be one bad outing, a weather shift, or a hitter having a career day. Look at the last ten games minimum before making any call about a player's current form. I also want to note that Statcast data can have gaps. Sometimes the tracking system drops frames during a play, especially in outdoor stadiums with interfering structures like scoreboard cameras or crane-mounted units. When this happens, exit velocity and distance estimates can be off by five to ten percent. I learned this the hard way when a stat I cited in a discussion was later corrected by the official tracking crew after manual review.
When the Data Fails You
Sometimes the numbers simply cannot tell you what happened. Mental mistakes, injury limitations, and clubhouse dynamics do not show up in any spreadsheet. I have seen pitchers with excellent stuff+ numbers fold under pressure because of a mechanical hitch that only appeared in high-leverage situations. There is no stat for that yet. If you are looking for a single source that covers everything cleanly, it does not exist. The best approach is to use Statcast for tracking data, BrooksBaseball for pitch detail, and the official box score for scorer-decided outcomes. Cross-check the numbers, flag the discrepancies, and form your conclusion from the overlap. That is the only way to get something close to accurate. The full matchup stats for this game should be available on all three sources within twenty-four hours of the final pitch. If you need help interpreting anything specific from the data, the process is straightforward once you know which numbers actually predict future performance versus which ones are just noise.
