You need some custom logging. Create a new database table.

If cookies are used, otherwise from the login page, get UserID and log that with each page hit. Then you can sort the table results by column and UserID.

There are a number of methods. Just keep in mind that in these days of GDPR you might run afoul of collecting PII (personally identifiable information, ie: tracking).

Then again, that's the intent, right? :)

Well we don't need personal info.
We just need to find a way to identify which pages are more interesting for signed-in members. For the free/standard visitors we can check the standard metrics, but there is more value behind the registered members.

@Kendo
how to create this database table and where?

how to create this database table and where?

Are you using a CMS like Wordpress, Drupal, Joomla or Moodle for the website? What are you using for member login management?

@jediviper ...

I suspect most of us missed this the first time around:

through Google Analytics or Tag Manager

Answer is "NO".

That kind of detail will never be revealed in g's free analytics or tag manager tools.

You can, of course, do this on your own as noted above. :)

For Google Analytics, have a look at the user id feature: [support.google.com...]

You can then track all the activity of logged in users separately from those who don't log in.

You can then track all the activity of logged in users separately from those who don't log in.

How would Google know who is logged in or not?

How would Google know who is logged in or not?

When a user is logged in, you're basically sending an identifier to Google alongside the general tracking. So, there is a small amount of technical setup, but this method 100% separates logged in and non-logged in users.

OP wants to track visitors signed in on OPs site, not g's... Just making sure we're all talking about the same thing.

OP wants to track visitors signed in on OPs site, not g's... Just making sure we're all talking about the same thing.

Yes - to track users who login on your site (with Google Analytics) you use the User ID feature.

User ID feature of what? On some sites I use UserID, MemberID and AuthorID. Google will not have the foggiest idea of which session variable is being used or if it is logged in or not.

UserID may be retrieved from a cookie but it may not be logged in. Again, Google will have no idea of what to track here no any idea of what cookie params are used. So the only way to track logged in users is to add some custom logging to whatever solution is providing the login validation.

We still haven't heard what he is using for member management.

So the only way to track logged in users is to add some custom logging to whatever solution is providing the login validation.

Yes - I noted this above: "...you're basically sending an identifier to Google alongside the general tracking. ".

you're basically sending an identifier to Google alongside the general tracking.

But Google doesn't know that you are sending other than what it requires for its usual tracking.

But Google doesn't know that you are sending other than what it requires for its usual tracking.

I don't know if I'm misunderstanding your comment, but the basic process is:

- Enable the User ID feature
- Send a user ID value alongside the page-view tracking

Google Analytics then records who is logged in and who isn't. It works perfectly well and I am using it it numerous accounts.

Logged in where?