You can get the userID by calling the action "Request Player Data" or Player's Friends userID "Request Social" then you will receive a JSON with the player data :
> {name:"playerName", firstName: "John", lastName: "Wick", highScore:1000, avatar:url, userID: 123456, coins:1000}
Then you can use the userID for "Request Player Replay" or "Request Player SaveState"
Check this JS Wiki for better understanding github.com/gameeapp/gamee-js/wiki/advanced-usage or the Construct Documentation : github.com/gameeapp/gamee-js-construct
The problem is that we can't see any of this data within Construct 2's debug mode. This means that testing these features are like pulling teeth unfortunately. It's a lot of trial and error.
For example, I have a bug now where it's pulling up the wrong data, but the only way to test it is with the CTRL-SHIFT-J approach, which gives me:
{"c2array":true,"size":[4,3,1],"data":[[[55681],[55681],["data:image/jpeg;base64,/9j/4RHlRXhpZgAAT
Etc... etc... The actual amount of this small array's JSON is significantly longer in console, and I mean 84996 characters long...
This makes searching through all of the code insanely time consuming.
Is there a reason why we can't have access to the Gamee dummy data while using Construct's debug? Or are we forced to use the emulator?
*EDIT*
As a heads up to people, it turns out that the huge amount of data I was seeing was only appearing while trying to access the Avatar icons. If you don't access these (at least during testing) you'll have a lot less data to sort through :)
Hope that helped!!!