Google Analytics has launched a new Report (still in beta) called the ‘User Explorer‘. You can find this report by navigating to Audience menu > User Explorer in your GA view:

As the name suggest, this report provides detailed insight into individual user’s activity on your website.

Quick recap of Client ID

For Google Analytics, (by default) a user is a combination of unique random number and the first time stamp. This combination is called the ‘Client ID‘.

Following is an example of a Client ID: 14525672358.86738999

Here, ‘14525672358’ is unique random number and ‘86738999’ is the first time stamp.

Client ID is assigned to each unique user of your website/app.

The client Id is set by _ga cookie (which is the Universal Analytics Cookie).

To learn more about client ID, read this article: Understanding Users in Google Analytics

Introduction to the new ‘Client id’ dimension

The User Explorer Report, show website usage data (sessions, average session duration, bounce rate, revenue etc) for each user, via the new ‘Client ID‘ dimension :

At present, the ‘Client ID’ dimension is available only in the ‘user explorer’ report. You can not use this dimension in a custom report, yet.

In the mean time, if you wish to use ‘client ID’ in a custom report, then you need to create your own custom dimension which can retrieve the client IDs.

The ‘client ID’ dimension is a high cardinality dimension. What that means, this dimension can have tens of thousands or even hundreds of thousands of unique values assigned to it.

Google Analytics reports which contain high cardinality dimensions are usually sampled.

Whenever a report includes high cardinality dimension, Google Analytics will notify you by following yellow colour notification message at the top of the report:

If you have got considerable data sampling issues, then the ‘user explorer’ report won’t be very accurate.

Also worth noting that, the client ID exist only on the device/browser where it has been set up. Because of this reason,

The ‘User explorer’ report of a non-user ID view, will show user’s activities, only for a single device and browser.

If the user changes his device/browser while interacting with your website, then that user activity won’t be reported in the ‘User explorer’ report of a non-user ID view.

Thus you may not always get the complete picture of a user’s journey on your website.

Consequently, if you do multi channel marketing and/or get considerable amount of traffic and conversions from different devices, then this report may in fact provide, muddy insight.

Quick recap of User ID

User id is a unique set of alphanumeric characters (like dfrgdKer5535925) assigned to a user, so that he can be identified across devices/ browsers.

Google Analytics cannot generate unique IDs for you, that can be used as user ids. You need to generate your own unique ids and assign these IDs to new and returning users through your user authentication system (like website login).

Example of a user ID is a login ID.

Any website which lets user login, can use the user ID feature.
User id view is the GA view which collects only the data related to user ID session.

In the case of user id views, GA calculates unique users by counting the number of unique users IDs assigned, instead of counting the number of unique clients IDs assigned to users.

To learn more about the user ID and user ID view, read this article: Guide to Cross device tracking with User Id in Google Analytics

Introduction to the new ‘User id’ dimension

If you have implemented User ID tracking, the ‘user explorer’ report in your ‘user ID’ view will include user IDs’ instead of the client IDs:

The user explorer report in a user id view, show website usage data (sessions, average session duration, bounce rate, revenue etc) for each user, via the new ‘User ID‘ dimension :

At present, the ‘User ID’ dimension is available only in the ‘user explorer’ report of a user ID view. You can not use this dimension in a custom report, yet.

In the mean time, if you wish to use ‘User ID’ in a custom report, then you need to create your own custom dimension which can retrieve the User IDs.

The ‘User ID’ dimension can also be a high cardinality dimension and can thus create data sampling issues in the ‘user explorer’ report.

Also worth noting that, the user id can exist accross devices/browsers. Because of this reason,

The ‘User explorer’ report of a user ID view, can show user’s activities, across devices and browsers.

You get a better picture of a user’s journey on your website through ‘user explorer’ report of a user ID view.

User Explorer report in Mobile App Views

The ‘user explorer’ report is also available in mobile app views.

This report is similar to the ‘user explorer’ report available in a non-user ID view.

However, it shows mobile app usage data (sessions, average session duration, bounce rate, revenue etc) instead of website usage data for each user, via the new ‘Client ID’ dimension.

This report provides detailed insight into individual user’s activity on your mobile app (instead of your website).

User Explorer report in a AMP View

Though ‘user explorer’ report would be available in any GA view, you create, the one in the AMP view is worth mentioning.

AMP stands for ‘Accelerated Mobile Page‘.

It is an open source mobile page format which is used to build mobile web pages with static content that loads instantly on mobile devices.

To learn more about AMP, read this article: Setting up & Tracking AMP Pages in Google Analytics

AMP view is that GA view which includes only the AMP traffic.

The ‘User explorer’ report in AMP view is similar to the ‘user explorer’ report available in a non-user ID view. However it, shows website usage data for each mobile user, via the new ‘Client ID’ dimension.

Also worth noting is that the format of the client ID is quite different:

By default, a client ID is a combination of unique random number and the first time stamp.

But in case of AMP, client ID is a string which starts with the word ‘amp-‘ and contains alphanumeric characters.

What does that mean, if your website has got mixture of regular mobile pages and AMP pages, then same mobile user can be counted as two different users. This is because when a user navigate from a non-AMP page to a AMP page (either in same or different sessions), he will be assigned a new client ID.

This new client ID will make him a new unique user.

To fix this issue, do not mix AMP pages with non-AMP pages.

Introduction to ‘User Report’

The ‘user explorer’ report is made up of several individual ‘user reports’. To access a user report, click on one of the client IDs in user explorer report:

You will now see the ‘user report’. Pay special attention to the highlighted components of this report:

From this report, we can conclude following:

#1 The report is about a user whose client ID is: 1155437348.1457350989

#2 This user was first acquired on Jan 07, 2016. See the ‘Acquisition Date‘ column on the left hand side of the report.

#3 The user was first acquired through social media. See the ‘Acquisition Channel‘ column on the left hand side of the report.

#4 The user was first acquired through a desktop device. See the ‘Device Category‘ column on the left hand side of the report.

#5 The user has generated total of 168 sessions, on the website so far.

#6 The user has spent 20 hours, 25 minutes and 45 seconds in total, on the website so far.

#7 The user has generated zero revenue on the website (as the website is not an ecommerce website).

#8 The user last visited the website on April 10, 2016.

#9 On April 10, 2016, the user had total of 18 interactions (pageviews, goal completions, purchase and/or events) with the website.

#10 At 4:36 pm (my local time and not the user’s local time), the user triggered an event called ‘reading’ on the article page titled ‘Beginners guide to Google Analytics Debugging‘:

Before 4:36 pm, the user triggered the ‘reading’ event at 4.28 pm but on a different article page, titled ‘Google and Universal Analytics Cookies – Complete Guide‘

On a side note, the ‘Reading’ event is triggered when a user is actually reading an article and not just skimming it.

In order to see more details for a particular user’s interaction, just click on it:

You can scroll down further to see the user’s activities for older dates:

That’s how you can read the ‘user report’.

Interactions in user report

In the user report, all of the users’ interactions are grouped into following 5 categories:

#1 Pageview

#2 Appview (available only in mobile app views)

#3 Goal

#4 Ecommerce

#5 Event

To see these categories, click on the ‘Filtered by’ drop down menu:

As the name suggest, through this menu, you can filter out particular type of user’s interactions like events.

Note:

Eye symbol denotes pageview or appview

Star symbol denotes goal conversion

Shopping cart symbol denotes purchase

Bell symbol denotes event

With ecommerce tracking enabled, the ‘user report’ becomes super useful in understanding the purchase journey.

Read the User report in Ascending order

Before you read the ‘user report’, sort it in ascending order (by default the report is sorted in descending order) by using the ‘Sort by‘ drop down menu:

By reading the ‘user report’ in ascending order, you can see the user activities from the start to finish in your selected time period.

When you read the ‘user report’ in descending order, you are then forced to read the report backwards, from finish to the beginning.

I am not sure, why Google choose to sort the user report in descending order, by default. It should be sorted in ‘ascending order’ by default.

Creating advanced segments in User report

You can also create advanced segment through user report. To do this, follow the steps below:

Step-1: Select the user’s interactions you want to use as conditions for your advanced segment:

Step-2: Once you select one or more user’s interactions, the ‘create segment’ (shown above) will become enabled.

Click on this button. This will open the ‘create segment’ dialog box:

Step-3: Name your segment, select the GA view, where you want this segment to be available, click on the checkbox ‘Apply the segment to user explorer report after saving’, if you want to apply this segment to the ‘user explorer’ report.

How to use the ‘User Explorer’ report

Analyse the journey of people who are making a purchase or completing a goal conversion, to better understand their conversion path.

Analysing the user journey of random people is pointless and this is very true in case of ‘user explorer’ report, where you are more likely to see tens of thousands of ‘users’ report, one for each unique client/user ID. 

So sort the user explorer report by revenue, transactions or goal conversion rate before you read it or access a particular ‘user report’.

The post Understanding User Explorer report in Google Analytics appeared first on Optimize Smart.

via Optimize Smart http://ift.tt/20ZD95Z