Geocortex Analytics 1.3 returns the number of sessions at future time that has not yet come.
Hi All,
Despite the fact that the Geocortex optimizer succeeds to display the number of sessions at correct time required to read these sessions, Analytics fails to do so.
For example, at 11:00 AM, the optimizer read only the number of session at 11:00 AM.
However, the analytics read the number of session at 11:00 am and 12:00 pm even though this time has not coming yet.
Kindly find the attached screenshots to understand the issue well.
What could be the issue here?
All the Best,
Fatin Rimawi
0
-
Hi Fatin,
The time that is shown in the reports comes from the client relay. If your users are in a different time zone, or have their clocks set differently on their PCs, the time that is reported in Analytics will reflect the time on their PCs.
I hope this helps!
Thanks,
Danny0 -
Hi Daniel,
Thank you for your replay.
Why should the time on Analytical relay on the client? The reported time should depend on the server time.
It does not make sense to reflect the time depends on time for each client.
Why not to cumulate the number of sessions for all users from all zones depending on the server time(screenshot).
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrmI&feoid=Body&refid=0EM60000000Ujto" _/_img_
What do you think?
Best,
Fatin0 -
Hi Fatin,
The reason for that is that the client relay has no knowledge of the information on the server. The client relay can determine the time on the client, but not on the server. In theory, you could record that time field as the time that the entry gets written to the database, but you'd run into trouble if the message queue was backed up, because the time would be offset.
That being said, if you'd like to see the way the time is recorded changed or improved, I'd encourage you to submit this to the ideas section!
Thanks,
Danny0 -
Hi Daniel,
Those are not ideas! This is who the Optimizer is behaving and functioning! Yes, we need the analytics to “record” the time according to the server clock but not depending on the client. Please, have a look on the screenshot below. Optimizer is respecting the server time and thus never records time in the future!
It appears that we are ending up by reporting every single behavior in Optimizer that is not yet implemented in Analytics
What do you think?
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrnQ&feoid=Body&refid=0EM60000000Ujty" _/_img_0 -
Hi guys,
I had a chat with the product manager about this, and I think I've misspoken here. I apologize for the confusion, let me try and clarify:
The time is collected from the user's browser and converted to UTC. It is then sent to Analytics. Analytics displays the time in reports in the report viewer's local time (converted back from UTC).
That being said, you should not be seeing times that are hours or days ahead. Can you please open a support case at your convenience, so we can collect your logs and data for analysis?
Thanks!
Danny0 -
As the GA 1.3 still fails to display the time the application is accessed by users as the GO 1.7 does, this minimizes the chance to feel the process.
By the way, do you have DEMO for GA 1.3 that’s is linked for example to GE4.7\GVH2.8? this way, one can see the expected behavior.
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrqK&feoid=Body&refid=0EM60000000Ujvu" _/_img_
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000GrqK&feoid=Body&refid=0EM60000000Ujvz" _/_img_0 -
Hi Jamal,
We do have a demo site, but it's not public. Please reach out to your account manager if you would like to see it!
Thanks,
Danny0 -
Thanks Danny.
What do you mean by the account manager? It is the reseller?0 -
No problem Jamal! Yes, in this case, you would want to reach out to your reseller. Sorry for the confusion, I forgot you were a customer through a reseller :)
Thanks!
Danny0 -
Hi Daniel,
I am working on the last version of GA 1.4.3 and I have the same issue, GA reads sessions at future time that has not yet come (future hours and days) and this is not making sense if it still reads the end user date and day
How we can solve this issue, can we change the link we put it in the GA integration to read the server time instead of client. What do you think?
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=907f2000000XdTE&feoid=Body&refid=0EMf2000000YB7y" _/_img_
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=907f2000000XdTE&feoid=Body&refid=0EMf2000000YB83" _/_img_
Best,
Lubna0
Please sign in to leave a comment.
Comments
10 comments