: Analytics Reporting Using Custom Dimensions With Changing Values I'm looking to segment users on my website by those who are logged in and those who are not, and I'm a bit confused as to how

@LarsenBagley505

Does a "logged in" state define a user in his characteristics, or a "state" in which he is during a moment (a session)?
It's the second one.

The dimension you're talking about should be something like "Registered user".
"Logged in" should be session level. Use these two for different purposes. In fact, for session level dimensions, if a user do something (some hits) when unlogged, then log in your website, all previous hits will be overwritten.


For example, if your website offers users the ability to login, you
can use a custom variable scoped to the session level for user login
status. In that way, you can segment visits by those from logged in
members versus anonymous visitors.

For example, if your websites offers premium content to paying subscribers, you can set a visit(user)-level custom variable to analyze which users are paying members, at which level of payment, and which users are using the free level of service for the site. You would likely set this custom variable as a one-time function, since the value would persist across the life of the visitor cookie.

developers.google.com/analytics/devguides/collection/gajs/gaTrackingCustomVariables#sessionLevel

Vote Up Vote Down

@Megan663

From March 20 to 30, you will have both "yes" and "no". For the 20th to the 24th, the user will fall into the "no" bucket (and "yes" for the 25th to 30th). This is because of how user-scoped CDs work. If the value of the CD is changed (or applied) for a particular session, then all the hits for the current session as well as all the future hits for future sessions will have that value. Past sessions are unchanged.

You can read more about the differences between the different scopes in this resource about Custom Dimensions.

Vote Up Vote Down