Guida all'integrazione con Garmin
Almost every guide to connecting a Garmin shows you the same thing: a button, an approval screen, a tick. The button is not the hard part. The hard part is knowing what actually crosses that link, what quietly does not, and why a connection that is working perfectly can look broken for a day or two.
Here is the short version. Linking your Garmin account gives the app permission to read your data from Garmin's servers — not from the watch on your wrist. Completed activities come across with their detail. Daily health data comes across where your watch records it. Things you typed into Garmin Connect by hand, and metrics your model does not measure, generally do not.
What crosses, and what does not
This is the table the other pages leave out. Treat the right-hand column as the realistic expectation rather than a guarantee: Garmin's feature set varies enormously between a budget band and a top-end multisport watch.
| Data | Does it travel? | What to expect |
|---|---|---|
| Completed activities — runs, rides, swims, strength, hikes | Yes | The core of the connection. Sport type, start time, duration, distance |
| Lap and interval detail | Yes, usually | Splits with their own pace and heart rate, so an interval session reads as intervals rather than one average |
| Heart rate, pace, distance and elevation within a session | Yes | The second-by-second record your watch captured |
| Resting heart rate | Yes | Daily, from the watch's own all-day measurement |
| Overnight HRV | Where your watch records it | Newer models measure it nightly; older and simpler ones do not have the feature |
| Sleep | Where your watch records it | You have to have worn the watch overnight. A night on the charger is a night of missing data |
| Stress and Body Battery | Where your watch records it | Both are derived from HRV, so they travel on the models that produce them and are absent on the ones that do not |
| A session still sitting on the watch | No | Nothing reaches the app until the watch has sent it to Garmin Connect first |
| Activities you typed into Garmin Connect by hand | Often not | Hand-made entries are treated differently from recorded ones, and when they do travel they arrive with no heart rate and no splits |
| Metrics your watch model does not measure | No | No connection can invent data the hardware never collected |
| Edits you make in Garmin Connect afterwards | Unreliable | Renaming a session or correcting its sport type later may not reach anything already synced |
| Social activity — kudos, comments, photos, friends | No | None of it is training data and none of it is shared |
The pattern is worth stating plainly: a connection moves what your watch measured, not what you remember doing. That sentence explains most of the surprises below.
Why a working connection looks broken
Four causes account for nearly all of the "my data is not showing up" reports, and none of them is a fault in the link itself.
Your watch has not synced to Garmin Connect yet
This is the big one, and it follows directly from how the connection works. A training app reads Garmin's servers. If your run is still on your wrist, there is nothing on those servers to read. The watch normally pushes to Garmin Connect through the phone app over Bluetooth, and on some models over Wi-Fi as well — but it has to happen, and it does not always happen the instant you finish. Open Garmin Connect and confirm the session is visible there before you go looking for a fault anywhere else.
Your history is still arriving
When you first connect, your past training is requested from Garmin in bulk. That request is queued on Garmin's side and comes back in batches rather than all at once, so an account with years of history can look half-empty shortly after connecting and complete a while later. Nothing is lost; it has simply not arrived yet. Check again later before reconnecting, because disconnecting and reconnecting usually restarts the queue rather than speeding it up.
The session was recorded in the wrong sport profile
A tempo run started in a cycling profile, or a treadmill session recorded as generic cardio, syncs perfectly and is then read as the wrong kind of training. Pace looks nonsensical and the effort lands in the wrong place in your week. The data is fine — the label on it is wrong. The fix is at the watch end, by choosing the right profile before you press start, and it is worth checking whenever one session looks absurd and everything around it looks normal.
Your watch does not record that metric
If sleep, HRV or Body Battery never appears while your activities arrive reliably, the connection is working and the hardware is the limit. Feature availability differs sharply across the Garmin range and across generations of the same family. Before assuming a sync problem, check whether the number exists in Garmin Connect at all — if it is not there, it cannot travel. Our guide to every Garmin metric covers which numbers come from where and what each one is actually measuring.
What to check, in order
- Is the session visible in Garmin Connect itself? If not, the watch has not synced and nothing else matters.
- Did you connect recently? Historical data arrives in batches, so give it time.
- Was it recorded in the right sport profile? A mislabelled session syncs fine and reads badly.
- Does the missing metric exist in Garmin Connect? If your watch does not measure it, no connection can supply it.
- Was the activity typed in by hand? Expect no heart rate and no splits.
Getting the data across is the easy half
Your watch is very good at measuring and quite bad at telling you what to do next. Once your sessions and your overnight numbers sit in one place, the useful question stops being "did it sync" and becomes "what should tomorrow look like". That is a different job. If you own no Garmin at all, the Strava connection covers what that brings instead, and Apple Watch and iPhone users have their own route in.
Frequently asked questions
What Garmin data does a training app actually get?
Your completed activities with their lap detail and their within-session heart rate and pace, plus the daily health data your watch records — resting heart rate, and on capable models sleep, overnight HRV, stress and Body Battery. It does not get anything your watch never measured, and social features such as kudos and comments are not shared.
Why have none of my past activities appeared?
Because your history is requested from Garmin in bulk and returned in batches rather than instantly. A long training history takes a while to come through in full. Give it time before disconnecting — reconnecting generally restarts the queue instead of speeding it up.
Why is my sleep or HRV missing when my activities sync fine?
Usually because the watch did not record it. Sleep needs you to have worn the watch overnight, and overnight HRV is only available on models that have the feature. Check whether the number exists in Garmin Connect first: if it is absent there, the connection has nothing to pass on.
Does an activity I entered by hand in Garmin Connect sync?
Often not, and when it does it arrives without heart rate or splits, because none were ever measured. If a session matters to your training record, record it on the watch rather than typing it in afterwards.
My run synced but the analysis looks wrong. Why?
Check the sport profile it was recorded in. A run captured under a cycling or generic cardio profile transfers perfectly and is then read as the wrong type of training, so pace and effort come out as nonsense. If the zones look wrong rather than the sport, suspect your heart rate zone settings.
Does connecting a training app drain my watch battery?
No. The connection runs between Garmin's servers and the app, so your watch is doing nothing it was not already doing when it synced to Garmin Connect.
Turn the sync into a decision
A connection that works still leaves you with a screen full of numbers and no plan. Lactate Training syncs your Garmin activities and health data, then builds and adapts a training plan around them, with zones anchored to your lactate threshold rather than an age-based guess.