What is this article about?
Recorded data field
Information that can be sent to Userlane based on the Portal configuration |
Purpose |
---|---|
Userlane Application and Company ID |
To identify which application Userlane is loaded upon and fetch relevant content. |
URL |
To identify which application Userlane is loaded upon and fetch relevant content. The URL is also used within HEART analytics and App Discovery if the corresponding options are enabled in the Portal. For more information, please check below the type of events that Userlane can collect based on your configuration.* |
URL patterns |
To have the Userlane Browser Extension detect whether Userlane should be loaded on that page. |
User ID |
To identify the same user again when returning to the underlying application. The User ID is automatically generated by Userlane when the Browser Extension is used. Once the user is identified, Userlane shows how many Guides have been completed, whether the Announcement was already shown, etc. |
Origin |
To identify how the user was created (e.g., whether it was generated by the Userlane JavaScript snippet, BX, via email invite, etc.) |
User Email Address |
To authenticate the user on the Browser Extension. Depending on the application setup, the user may have to share the email address:
|
User Data (optional) |
To segment users with the help of attributes. Attributes are never automatically collected by Userlane. They can be passed in the following way:
|
User session |
It passes user session-related information that is used to calculate various analytics-related metrics in Userlane. For more information, please check below the type of events that Userlane can collect based on your configuration.* |
Browser |
To guarantee browser compatibility. |
Browser language and page language |
To guarantee that the content will be shown in the correct language. |
Sign-up time |
To be able to use date/time-related segments. For example, by knowing the sign-up time, you can show certain onboarding materials only for one month. |
* When the end user interacts with certain underlying apps or Userlane elements, data is sent to Userlane Cloud in the form of raw events. To learn more about Userlane-related events, please check the following wiki documentation.