I'm using some kind of a server setup that uses Node.js/Express to build a web-application (a collaborative whiteboard).
The way I have things setup on my server is this.
My user visits this URL:
roomName part is not really a subpage. I redirect to page
www.sitename.io/go/ via my server-setup(Express Routes) and I use the last part of my URL as a parameter of some sort to create some WebSocket connections.
So for example all these addresses will land the user to the same page (which is
www.example.io/go/physicsRoom www.example.io/go/mathsRoom www.example.io/go/whateverRoom www.example.io/go/helloWorldRoom
Long story short:
The last part of the URL is not an actual "page". It's simply used as somekind of a parameter.
The issue I'm seeing is erroneous/unreliable Google Analytics tracking data.
There are certain cases where I should be getting in Google Analytics a certain 2:00 hours Avg. Time on Page but instead it records it as 0:00. In general I seem to be getting unreliable/erroneous tracking.
What I think is the issue.
I'm thinking that the whole setup where my URL does not redirect to the last part of the URL(it's not an actual page but is simply there to be used as a parameter), is what's confusing/causing incompatibility issues with Google Analytics.
Here's the Google Analytics data (I'm getting 0:00 time in places where I should be getting at least 2hours +).