A Chrome extension that helps golfers identify and fix incorrectly tracked shots in Garmin Connect. This tool scans your golf scorecards to find suspicious shots that are likely GPS errors or tracking bugs, such as putts recorded at 60+ meters, wedge shots at unrealistic distances and other clubs with way too long distances.
Made because finding these shots in the Garmin app or on the web is a hassle. Instead of checking every scorecard manually, this script will do it for you.
Garmin golf watches sometimes record incorrect shot distances due to:
- GPS signal issues
- Accidental button presses
- Auto-shot detection errors
- Syncing problems
These errors affect your club statistics, and if using one of the Approach watches, the virtual caddy will use these statistics to suggest clubs. This extension helps you quickly find and review these problematic shots so you can correct them in Garmin Connect.
Example: A Gap Wedge shot incorrectly recorded at 594 yards - exactly the kind of error this extension helps you find and fix.
- 🔍 Automatic Shot Analysis - Scans all your golf scorecards to find suspicious shots
- ⚙️ Customizable Club Ranges - Set your own maximum distances for each club
- 🎯 Direct Links - Click to jump directly to problematic shots in Garmin Connect
- 📊 Smart Detection - Uses both default and personalized thresholds
- 🔄 Background Scanning - Continue browsing while the extension analyzes your data
-
Clone or download this repository:
git clone https://github.com/loekensgard/garmin-club-fix.git
-
Open Chrome and navigate to
chrome://extensions/ -
Enable "Developer mode" in the top right corner
-
Click "Load unpacked" and select the
garmin-club-fix/srcfolder -
The extension icon will appear in your Chrome toolbar
- Open Garmin Connect and log in
- Open Chrome DevTools (F12 or right-click → Inspect)
- Go to the Network tab
- Navigate to your golf scorecards in Garmin Connect
- Look for any API request (e.g.,
/scorecard/summary) - Click on it and find the
Authorizationheader - Copy the bearer token (starts with
Bearer eyJ...)
- While viewing your golf data in Garmin Connect, check the URL
- Look for a UUID like
12345678-abcd-1234-5678-123456789abc - This is your user ID - copy it
- Click the extension icon in Chrome toolbar
- Paste your bearer token in the first field
- Paste your user ID in the second field
- Click "Save Settings"
- Navigate to connect.garmin.com
- Click the extension icon
- Click "Scan for Bad Shots"
- Wait for the scan to complete (progress bar shows status)
- Review the suspicious shots grouped by scorecard
- Click any shot link to open it in Garmin Connect for correction
- Click "Fetch My Clubs" to load your golf clubs
- Review your average and max distances
- Adjust the "Max Distance" for each club based on your abilities
- Click "Save Club Settings"
- Future scans will use your custom ranges
The extension uses these default maximum distances (in meters):
| Club Type | Max Distance | Common Issues |
|---|---|---|
| Driver | 350m | GPS glitches on tee shots |
| 3 Wood | 280m | Auto-detection errors |
| Irons (5-9) | 200-170m | Wrong club selected |
| Wedges (PW/SW/LW) | 150-120m | Chip shots marked as full swings |
| Putter | 20m | Most common error - GPS jumps |
Most common issue! This happens when:
- GPS signal is lost in woods/buildings
- Watch auto-detects a practice swing as real shot
- You forget to mark the shot and GPS jumps to next tee
Usually occurs when:
- Wrong club is selected on watch
- Shot detection triggers during cart ride
- GPS correction happens mid-round
- Make sure you're logged into Garmin Connect in the same browser
- Try refreshing the Garmin Connect page
- Tokens expire after 24-48 hours
- Get a new token from DevTools and update in extension
- Your shots might be within normal ranges
- Try adjusting club ranges if you have unusual distances
- Check if you have any scorecards in your account
- Ensure you're on connect.garmin.com
- Check that bearer token is saved
- Try reloading the extension
- Check Chrome console for errors (F12 → Console tab)
- Local Storage Only - All data is stored locally in your browser
- No External Servers - Direct communication with Garmin Connect only
- Token Security - Bearer token never leaves your browser
- Open Source - Review the code yourself for transparency
Contributions are welcome! Feel free to:
- Report bugs via GitHub issues
- Submit pull requests with improvements
- Suggest new detection algorithms
Built with:
- Chrome Extension Manifest V3
- Vanilla JavaScript (no frameworks)
- Garmin Connect private API
- Chrome Storage API for persistence
This is an unofficial tool not affiliated with Garmin. Use at your own risk. Always verify suggested corrections before making changes to your scorecards.
