With this feature, you can send precise user IDs for your end-users, enabling you to provide a continuous and consistent experience for a user on different browsers or devices. 

Also, this cancels out MAU's dependency on unique browser sessions. So instead, you start defining your exact MAU count (user base) with the IDs you send us.

For instance, if you send 2000 ids for 2000 different users, only those people can see the live UG contents (guide, checklist, etc.) you have. And, your MAU count will be 2K.

This feature has additional perks, such as having persistent user data at UG, detecting event history for specific users, and accessing our user API.

How to Enable User User Identification

You can enable User Identification in UserGuiding Panel > Settings > Installation.

  • Click on Enable Identification.

  • There you'll find the directions to start and complete this process successfully.

You can add the recommended code (having the identify method) to any place within your Js file. However, do not add it inside your UserGuiding Container Code. Instead, you can add the code right after the container.

Once you add it successfully, click on the Enable Identification button (at the bottom) to see if your implementation is done correctly.

Pro Tip: Click on the publish changes button and visit the embedded pages as an end-user to successfully initialize the process.

To test if the implementation is done successfully, you can follow the steps given here.

Establishing the User Identification Feature

This part of the implementation requires technical knowledge and access to your source code. You may ask for the help of your developer colleague.

More information can be found here if you want to implement user identification with Google Tag Manager.

window.userGuiding.identify(userId, *customAttributes)

The first argument inside the identify method should be the user's ID. The rest is optional; you can send custom attributes with the same method.

1st row in the example below is a sample ID sent with the identify method. The 2nd implementation includes custom attributes being sent after the user ID (the first argument)

Important: We only support strings, numbers, booleans, and these specific date formats. We do not accept arrays, lists, or nested objects as valid user attributes.


window.userGuiding.identify('1Ax69i57j0j69i60l4', {
name: 'John Lennon',
email: '[email protected]',
created_at: 123456789,


  • We store user_id as a string, so you can use any data type that can be converted to a string. 

  • You can add the code above to any place in your JS file that suits you. However, please don't add it to the container we've given you.

  • If you already have active guides, they'll stop showing from the moment we activate the feature for you until you set the user ID correctly.

  • The MAU calculation is based on the user IDs you've set with this option. 

  • The storage is independent of the browser's local storage, so clearing cookies or application data won't affect UserGuiding history.

  • With this option, you can ensure your user sees Guides only once, even on different browsers or devices.

Did this answer your question?