Zum Hauptinhalt gehen

How can you see unique user names for individual viewers in Analytics?

Permanently deleted user
How can you see unique user names for individual viewers in Analytics?

 

I'm just starting out with GTX Analytics 1.1 - I can't seem to find where you can view unique username statistics for viewers, number of visits, frequency etc, anywhere in the user manuals or videos? (We are using GTX Identity Server)
0

Kommentare

10 Kommentare

Datum Stimmen
  • Permanently deleted user
    Hi James,

     

    Those stats are tracked under:

     

    Trends > Geocortex Applicaitons > Viewer name 

     

    Note that you need to configure the client relay for user stats to be reported.  See the Administrator guide (Section 8.8) for details about that.  

     

    I hope that helps!

     

    Thanks,

     

    Danny
    0
  • Permanently deleted user
    Hi again James,

     

    I just reviewed the documentation, and it looks like there's 2 missing items in there.  I've filed an improvement to fix that but in the meantime, 2 things to note:

     

    1) You need to configure an external URL for your client relay. If you just point the viewer to http://servername/Geocortex/Analytics/ClientRelay then external clients will not be able to relay to the server.  Talk to your IT team for assistance configuring an external URL.

     

    2) When you configure the client relay, you need to add the configured URL to the HTML5 viewer's proxy.config file, as follows:

     

    <serverUrl url="http://external-url-that-you-configured-in-step-1.com" matchAll="true"></serverUrl>

     

    If you need some one on one assistance getting this configured, please let me know, or open a support case so we can assist you!

     

    Thanks,

     

    Danny
    0
  • Permanently deleted user
    Thanks Danny,

     

    I was looking for some documentation on the client relay as I wasn't totally clear about about it's configuration.  I'm configuring both html5 and some older silverlight viewers so will take note of item 2 for the html5.  I'll let you know how it goes.

     

    Thanks!

     

    James
    0
  • Permanently deleted user
    Hi Daiel,

     

    I have the same issue. I tried to do the steps that you have mentioned it but with no effect and the report still back with “no information available”. may I do something wrong! could you please see the below screenshots:

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000PDOJ&feoid=Body&refid=0EM60000000HT5S" _/_img_

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000PDOJ&feoid=Body&refid=0EM60000000HT5X" _/_img_

     

     

     

    best,

     

    Lubna

     

     
    0
  • Permanently deleted user
    Hi Lubna,

     

    If you're still having trouble seeing your users, you can look at the traffic in your viewer using Fiddler.  Look for a request to your Analytics server that contains proxy.ashx in the URL, and if that's coming back with a 200, then the client relay is working.  

     

    Another issue that can come up, is if the URL you are using to access the viewer does not match the one that Analytics has discovered (which you should be able to tell by looking at the status tab, and then at your C1 viewer). If they do not match. the results returned by the client relay will not be shown in reports.  An important part of Analytics, is that the URL that is being used to access the viewer must match the one in your reports.  

     

    Check out section 9.5.2 in the Administration guide for some info about configuring URL substitution.

     

    If that doesn't work, I would suggest reaching out to your reseller for support on this issue.

     

    I hope this helps!

     

    Thanks,

     

    Danny
    0
  • Ethan Granger
    Fiddler is showing a 403 response for the proxy.ashx call. All URLs appear to be correct. Relay url is not external, but neither am i (and it resolves for me). How can I get rid of the 403 error?
    0
  • Permanently deleted user
    Hi Ethan,

     

    If you are getting a 403 error, the problem is likely that you have not added the entry to the HTML5 viewer proxy.config file (per the instructions earlier in this thread, second reply down).  Can you please confirm whether you have allowed proxying to the Analytics server?

     

    Thanks!

     

    Danny
    0
  • Ethan Granger
    You mean this:

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000Cg5z&feoid=Body&refid=0EM600000001QoU" _/_img_
    0
  • Permanently deleted user
    Hi Ethan,

     

    That too, but you also need to configure the proxy.config file in the viewer directory in your wwwroot folder.  The default location is C:\intepub\wwwroot\Html5Viewer\proxy.config

     

    Thanks,

     

    Danny
    0
  • Permanently deleted user
    Hello, I am only getting a report of one or two users max for our viewer when I know for a fact that there should be more. I had seen it report on each user that was logged in prior, but not sure what may have been switched off or configured to stop reporting on users. 

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=907f2000000fxdE&feoid=Body&refid=0EMf2000000k9mB" _/_img_
    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post