The User ID feature lets you associate engagement data from multiple devices and different sessions with unique IDs. In order to use the User ID feature in Analytics you must
- use Google Tag Manager for your Analytics tracking
- be able to generate your own unique IDs
- create a new Analytics account for User ID reporting
- all of the above
The user id feature lets you associate engagement data from multiple devices
The User ID lets you associate engagement data from multiple devices and different sessions with unique IDs.
Each unique User ID is considered to be a unique user in Analytics, so you get a more accurate user count in your reports. When you send Analytics an ID and related data over the course of multiple sessions, you can also put individual user actions in context and start analyzing ongoing relationships.
User ID lets you associate a persistent ID for a single user with that user’s engagement data from one or more sessions initiated from one or more devices.
Analytics interprets each unique user ID as a separate user, which provides a more accurate user count in your reports.
When you send Analytics an ID and related data from multiple sessions, your reports tell a more unified, holistic story about a user’s relationship with your business.
- How User-ID works
- Session Unification
- Next steps
- Related resources
How User-ID works
User-ID enables the association of one or more sessions (and the activity within those sessions) with a unique and persistent ID that you send to Analytics.
To implement User-ID, you must be able to generate your own unique IDs, consistently assign IDs to users, and include these IDs wherever you send data to Analytics.
For example, you could send the unique IDs generated by your own authentication system to Analytics as values for User-ID. Any engagement, like link clicks and page or screen navigation, that happen while a unique ID is assigned can be sent to Analytics and connected via User-ID.
In an Analytics implementation without the User-ID feature, a unique user is counted each time your content is accessed from a different device and each time there’s a new session. For example, a search on a phone one day, purchase on a laptop three days later, and request for customer service on a tablet a month after that are counted as three unique users in a standard Analytics implementation, even if all those actions took place while a user was signed in to an account. While you can collect data about each of those interactions and devices, you can’t determine their relevance to one another. You only see independent data points.
When you implement User-ID, you can identify related actions and devices and connect these seemingly independent data points. That same search on a phone, purchase on a laptop, and re-engagement on a tablet that previously looked like three unrelated actions on unrelated devices can now be understood as one user’s interactions with your business.
Session unification is a User-ID setting that allows hits collected before a user ID is assigned to be associated with the ID.
To set up User-ID, you must first enable the feature in your Analytics account (Edit permission required), and then modify your tracking code. Learn more
You can verify your setup by checking the data in the User-ID Coverage report.