User gets unexpected user_id

[tachybrady]

Our OAuth flow works fine for most users.

One has found that despite resetting, and making new accounts, we consistently get a user_id from the Fitbit API that does not match the one that the user expects (and uses with their devices). It's the same wrong user_id after making (and expecting) a new one. Could this be related to cookies on the user's browser? The Fitbit app itself?

[JohnFitbit]

Hi @tachybrady,

Welcome to the forums!

This is actually a common scenario that we've prepared documentation for. Sometimes users create a Fitbit account and consent to a 3rd party app, but forget the account later down the line, thus resulting in the creation of a new Fitbit account and going through the onboarding flow again. This is why you might see two different user ids come from the same user. To identify which user id you're pulling data from, refer to our Data Synchronization troubleshooting guide.

I hope this helps. Let me know if you have any additional questions.