.png)
Launch monitor glossary
Understand the numbers behind your driver fit
Launch monitor data tells the fitter how you create speed, how the ball launches, how it curves, and whether that performance is repeatable enough to trust.
- Metrics
- 18
- Core Inputs
- 5
- Current Fit
- Driver
What do launch monitor metrics tell a fitter?
They turn a golf swing into a pattern the fitter can actually test. In Smart Golf Fitting, the driver engine uses the core fields to build a reliable baseline, then uses optional fields to add detail around strike, flight, direction, loft delivery, and setup.
| Layer | What it tells us | How the driver engine uses it |
|---|---|---|
| Core baseline | Club speed, ball speed, launch, spin, and offline distance describe the minimum pattern needed for a driver fit. | These fields drive quality checks, baseline confidence, shaft speed bands, flight-window reads, and dispersion priority. |
| Optional depth | Carry, smash, height, descent, spin axis, start direction, face/path, attack angle, dynamic loft, and spin loft explain why the core pattern happened. | These fields refine head family scoring, loft choice, hosel direction, playing-length caution, and the plain-English explanation in the report. |
| Consumer outcome | The important question is not whether one number is good or bad. It is whether the numbers work together for distance, control, and repeatability. | The engine avoids single-number recommendations and looks for agreement across speed, strike, flight, direction, and delivery. |
Which launch monitor metrics are used in the fit?
The current driver engine has five required launch monitor fields and a wider set of optional fields that deepen the explanation when your launch monitor provides them.
| Metric | Role in this driver fit | What it tells us | How the engine uses it |
|---|---|---|---|
| Club Speed | Core required | The speed of the clubhead just before impact, used to estimate distance potential and shaft loading requirements. | Club speed is the engine's main speed-band input. It helps set the expected shaft flex and weight range, the starting loft window, and the launch and spin ranges that make sense for the player's speed. |
| Ball Speed | Core required | The launch speed of the ball after impact, created by club speed, strike quality, delivered loft, and energy transfer. | Ball speed is the main output of the strike. The engine uses it to check strike stability, distance efficiency, and whether the player is turning club speed into useful speed off the face. |
| Launch Angle | Core required | The upward starting angle of the golf ball after impact, controlled mainly by delivered loft, attack angle, strike, and ball speed. | Launch angle tells the engine how high the ball starts. It is used with spin and speed to decide whether the fit needs more launch help, less launch, or a more neutral flight setup. |
| Spin Rate | Core required | The ball’s rotation rate at launch, which strongly influences height, carry distance, roll, curvature stability, and stopping power. | Spin rate tells the engine whether the ball is climbing, falling, or staying in a playable driver window. It is used with speed and launch before the engine rewards low-spin heads or shafts. |
| Offline Distance | Core required | The left-or-right distance a shot finishes or lands from the target line, used as an outcome measure for dispersion and directional control. | Offline distance tells the engine where the shot finishes relative to the target line. It is the core dispersion field for forgiveness, direction pattern, and control priority. |
| Smash Factor | Supporting strike signal | The energy-transfer ratio between ball speed and club speed, used to judge strike efficiency for a specific club. | Smash factor shows how efficiently club speed became ball speed. The engine uses it when available, and can also infer the relationship from club speed and ball speed. |
| Carry Distance | Supporting distance signal | The airborne distance of the shot before bounce and roll, used for club gapping, hazard carry, and approach control. | Carry distance shows how much usable distance the ball produced before bounce and roll. The engine uses it to judge whether speed and launch conditions are creating real yardage. |
| Total Distance | Supporting rollout context | The full shot distance including carry and estimated rollout, most useful when driver or long-club rollout matters. | Total distance adds estimated roll to carry. The engine keeps it as context, but it does not let rollout outweigh carry, dispersion, launch, and spin. |
| Launch Direction | Optional direction signal | The ball’s start direction, used to separate face-orientation issues from curvature and strike-location issues. | Launch direction shows where the ball starts. The engine uses it with offline distance and spin axis to separate start-line problems from curve problems. |
| Spin Axis | Optional curve signal | The ball-curvature metric that translates impact conditions into draw, fade, hook, or slice tendency. | Spin axis shows the tilt that makes the ball curve. The engine uses it with launch direction and offline distance to understand whether the miss is start line, curve, or overall dispersion. |
| Attack Angle | Optional loft-delivery signal | The up-or-down delivery angle of the clubhead at impact, which affects launch, spin, dynamic loft, and distance potential. | Attack angle shows whether the club is travelling upward or downward through impact. The engine uses it mainly for loft and launch guidance. |
| Club Path | Optional delivery signal | The in-to-out or out-to-in delivery direction of the clubhead, used to interpret shot shape, face-to-path, and directional bias. | Club path shows the horizontal direction the club is moving through impact. The engine uses it with face angle to understand face-to-path and avoid overcalling directional bias. |
| Face Angle | Optional delivery signal | The target-relative face direction at impact, a major contributor to the ball’s start direction. | Face angle shows where the clubface points relative to the target. The engine uses it to explain start direction and to support or reject directional setup changes. |
| Face to Path | Optional delivery signal | The face-versus-path relationship at impact, widely used to explain curvature and spin-axis tilt. | Face to path shows how open or closed the face is relative to the club path. It is one of the clearest delivery signals for curve. |
| Dynamic Loft | Optional loft-delivery signal | The delivered loft at impact, which can differ substantially from the static loft printed on the club. | Dynamic loft is the loft actually delivered at impact. The engine uses it to tell whether launch and spin are coming from the club setup, the player's delivery, or both. |
| Spin Loft | Optional loft-delivery signal | The impact geometry between delivered loft and clubhead direction, used to explain spin creation and strike efficiency. | Spin loft links delivered loft and attack angle. The engine uses it to explain why spin and smash may be moving together. |
| Peak Height | Optional flight-window signal | The apex of the shot trajectory, used to judge whether launch, spin, and ball speed are producing a playable flight window. | Peak height confirms how high the ball actually flew. The engine uses it to check whether launch and spin produced a playable flight window. |
| Descent Angle | Optional flight-window signal | The landing steepness of the ball flight, used to predict rollout, stopping power, and whether approach shots can hold greens. | Descent angle shows how steeply the ball lands. The engine uses it with launch, spin, and peak height to understand rollout and flight control. |
How do the metrics work together inside the driver engine?
A fitter does not read these fields as separate scorecards. The engine groups them into fitting questions: can we trust the data, is speed becoming distance, is the flight playable, is direction controlled, and does loft delivery explain the launch and spin?
Data quality and trust
The engine first checks whether the core data is complete and whether any shots look like outliers. Missing core fields, impossible speed relationships, launch outliers, spin outliers, and very large offline misses can reduce confidence or remove a shot from the baseline.
Metrics in this read
- Club Speed
- Ball Speed
- Launch Angle
- Spin Rate
- Offline Distance
- Smash Factor
Distance efficiency
This group answers a simple fitting question: is the player's speed becoming useful distance? The engine compares speed, smash, and carry so it can protect efficient distance or look for easier launch, better strike retention, and more forgiveness.
Metrics in this read
- Club Speed
- Ball Speed
- Smash Factor
- Carry Distance
- Total Distance
Flight window
This group explains whether the ball is flying too flat, too spinny, too high, or broadly playable. It affects low-spin head support, launch-help support, shaft launch bias, selected loft, and hosel loft guidance.
Metrics in this read
- Launch Angle
- Spin Rate
- Peak Height
- Descent Angle
- Carry Distance
Direction and delivery
This group separates where the ball started, how it curved, and where it finished. It helps the engine decide whether the fit needs forgiveness, draw bias, a hosel direction check, or no directional correction at all.
Metrics in this read
- Offline Distance
- Launch Direction
- Spin Axis
- Club Path
- Face Angle
- Face to Path
Loft delivery
This group explains why launch and spin are happening. When coverage is strong, it can move the selected loft; when coverage is thinner, it stays as advisory context so the report does not overclaim.
Metrics in this read
- Attack Angle
- Dynamic Loft
- Spin Loft
- Launch Angle
- Spin Rate
What if my launch monitor does not export every field?
That is normal. The driver fit can run from the core fields, and optional fields add explanation depth when available. Missing optional data makes that part of the read more conservative; it does not automatically make the whole fit unreliable.
Core file
Club speed, ball speed, launch angle, spin rate, and offline distance let the engine build the driver baseline.
Richer file
Fields like carry, peak height, descent, spin axis, face/path, attack angle, dynamic loft, and spin loft help the report explain the reason behind the recommendation.