: Debugging a User-Scope Custom Dimension in Google Analytics I am currently trying to configure a User Scope dimension that is set on an Admin section of a website. Reason being, so that I can

@Odierno851

If you just want to filter out a certain section of the site (like /admin/ for example) you can do that with a filter in Google Analytics of type traffic to the subdirectories.

If it's not as straightforward as that You could use a Hit scoped custom dimension for individual pages and pass values like admin, content, archive, etc. and use that to filter your reports.

Also I assume you actually have an exclude filter set for this dimension in the GA back-end?

EDIT

This is important since the debugger will not show you the relevant information since the user scope of this is handled by GA in the back-end, not the front-end. Keep in mind that seeing dimension: 'admin', page: '/xyx.html in the debugger is expected behavior since everything is sent to GA and GA then does the post-processing of deciding what should be included in your view and what should not.

Vote Up Vote Down

@Vandalay111

You will not see the value persist in the Google Analytics debugger as the dimension's persistance it set within the Google Analytics platform.

The simplest way to explain dimensions, is that they will always be set at the last value sent for the relevant scope. For example:

User Level: The last value sent about a single user. This value will be attached to all sessions regardless of whether this value is sent again. If a new value is sent to Google Analytics, this new value will override the previous value.

Session Level: The last value sent within the session. This value will be attached to the entire session, regardless of what was sent to the session earlier. For example, if a random number is sent to Google Analytics as an ID on every hit, the last value sent through to Google Analytics will be the 'ID. for the session.

Vote Up Vote Down