If your steps are increasing in Pacer but your distance stays at 0 (or doesn’t change), it usually means Pacer is receiving step data but doesn’t have enough information to calculate distance—or the screen you’re looking at is using a distance-only rule (e.g., GPS-only challenges).

Below is a quick explanation of why this happens and exactly what to check.

Why this happens

1) Steps and distance can be measured differently

It’s normal for steps to update even when distance doesn’t, because:

• Steps can be counted from motion sensors (accelerometer) without GPS. 
• Distance often needs either GPS or a valid stride-length estimate (steps × stride length). Fitbit explicitly documents this: Distance = Steps × Stride Length, and GPS activities use GPS distance instead. 
• Samsung Health similarly notes that distance is calculated from steps using an estimated stride length (affected by height and cadence). 
• On iOS, Apple’s “Motion Calibration & Distance” setting affects distance/pace accuracy by using location calibration.

2) Your current “distance view” may be GPS-only

In some Pacer contexts (especially certain challenges), distance may count only GPS-tracked distance, not step-estimated distance. Distance Challenge can be GPS-only, meaning “normal daily steps won’t count.”

3) Your step source provides steps faster than distance (or distance sync is delayed)

If your steps come from Apple Health / Google Fit / Samsung Health / wearables, distance may update later due to syncing and data merging. Google Fit’s developer FAQ notes that differences can be caused by syncing delays and that merged values align once synced.

Quick diagnosis: which situation are you in?

A) Daily steps increase, but daily distance stays 0

Most common causes:

• Pacer is using a source that provides steps but not distance, or distance needs a stride estimate/profile. 
• The app/source hasn’t synced distance yet.

Go to Fix #1 and Fix #2 below.

B) You started an outdoor walk/run, but distance stays 0

Most common causes:

• Location permission is off, “Precise Location” is off, GPS not acquired, or power saving restricted tracking.

Go to Fix #3 below.

C) Challenge distance stays 0, but steps increase

Most common causes:

• The challenge is set to Distance and may be GPS-only (steps won’t contribute).

Go to Fix #4 below.

Fix #1 — Confirm your Step Source (the #1 key step)

Distance behavior depends on your step source.

iOS step sources: Phone, Apple Health, Apple Watch, Fitbit, Garmin

Android step sources: Phone, Google Fit, Fitbit, Garmin, Samsung Health

Then follow the matching section below.

Fix #2 — If your source uses “steps → distance” (stride-based distance)

If your source is Fitbit

Fitbit calculates distance as Steps × Stride Length (unless GPS activity is used). If stride/profile data is missing or wrong, distance can be wrong or effectively unusable.

What to do

1. Confirm your Fitbit profile info (height/sex) is correct (since stride length is derived from this). 
2. If distance still looks wrong, update stride length by: 
   • tracking a GPS run/walk, or 
   • measuring stride manually (Fitbit provides a method: walk a known distance, count steps, divide). 
3. After updating, allow time for data to sync into Pacer.

If your source is Samsung Health (Android)

Samsung states distance is calculated from steps using an estimated stride length influenced by height and cadence.

What to do

1. Confirm Samsung Health profile basics (height) are correct. 
2. Update Samsung Health + device software (Samsung recommends keeping both updated). 
3. Re-check after sync.

If your source is Google Fit (Android)

Google Fit merges data from multiple sources and differences can occur temporarily due to sync delays.

What to do

1. Make sure Pacer is connected to the correct Google account. 
2. Open Google Fit and Pacer while connected to the internet to force sync. 
3. If values remain stuck, disconnect/reconnect the integration (recommended as a separate troubleshooting article).

Fix #3 — If you expect GPS distance (Outdoor tracking) but it stays 0

iOS (iPhone / Apple Watch)

1. Ensure Location Services is ON. 
2. Ensure Motion Calibration & Distance is ON: 
   • Settings → Privacy & Security → Location Services → System Services → Motion Calibration & Distance 
3. If using Apple Watch, calibration improves distance accuracy (especially when GPS is weak). 
4. Start an Outdoor activity (not “Indoor”) when you want GPS distance.

Android

1. Confirm Pacer has Location permission (Allow while in use / all the time if your design requires it). 
2. Turn off Battery Saver / Power Saving during outdoor tracking. 
3. If distance works only when the app is open, your phone may be restricting background tracking.

Fix #4 — If this is happening in a Challenge

Pacer challenges can score Steps or Distance, and some distance challenges can be GPS-only, so step-based distance won’t count.

What to do

1. Open the challenge → Rules/Details 
2. Confirm: 
   • What counts (Steps vs Distance) 
   • Whether GPS-only is enabled 
3. If it’s GPS-only, start a GPS-tracked activity (Outdoor walk/run) for progress.

Common mistakes

• Looking at a Distance (GPS-only) challenge and expecting step distance to count. 
• Location Services enabled, but Motion Calibration & Distance disabled on iOS. 
• Using a wearable/source that calculates distance from stride length, but profile info is missing or incorrect.

Still not fixed? Send Support this info

To resolve quickly, include:

• Your Step Source (Phone / Apple Health / Apple Watch / Fitbit / Garmin / Google Fit / Samsung Health) 
• Whether this happens on: 
  • Daily total distance 
  • A GPS activity distance 
  • A Challenge distance (and whether it’s GPS-only) 
• Screenshots of steps vs distance and the relevant settings screen