1. Home
  2. Getting Started
  3. What Data Does WalkMe Collect?

What Data Does WalkMe Collect?

Updated on October 17, 2018
Download PDF

WalkMe allows you to gain insights about user behavior with WalkMe and on your site. To gain this insight, WalkMe collects information such as Walk-Thrus completed and WalkMe widget opens.

Does WalkMe Collect Sensitive Information?

By default, WalkMe does not collect personally identifiable information (PII) other than IP addresses in logs for security purposes, End Users’ approximate geolocation (country and city in which they are located) and masked IP addresses for the ongoing operation of the WalkMe System, and assigns collected metadata to anonymous random GUID. Moreover, WalkMe collects and transfers environment properties such as browser and OS, page URL, and title. By default, the analytics information is anonymized aggregated usage statistics related to WalkMe usage.  By default, end-user analytics leverage an anonymized WalkMe ID.  You can add additional criteria to collect for analytics purposes.  This can be configured by the customers’ WalkMe Administrators.

Want to see for yourself? Take a look at exactly what data is being sent to WalkMe in the Network tab of the Developer’s console.

Example Analytics Parameters

Below is a list of the most common API calls used to collect information. As you can see, WalkMe does not collect sensitive information specific to your site.

AddWidgetOpen:

  • mtjQuery – The WalkMe lib id and version that is being used
  • userId – WalkMe account ID
  • fullUrl – The URL of which the request is coming from
  • source – Whether the snippet is production or test (0 – production, 1- test)
  • browser – Browser type and version
  • os – Operation system
  • permutationId – Only relevant in case AbTesting is activated. otherwise always -1.
  • endUserGuid – A generated GUID to identify the user uniquely, does not tell us any information about the user
  • _ – A jQuery functionality to avoid files caching. The current date is added to this parameter.

AddStepLogs:

  • mtjQuery – The lib id and version the is being used
  • stepActionSerialized – All the data of our step audits (which step was played, what was the result)
  • TutorialId – The WalkThru ID
  • StepId – The current step ID
  • stepIndex – The current step index in the WalkThru
  • totalSteps – The amount of steps in the current WalkThru
  • playGuid – A unique identifier for the play event of the WalkThru
  • userId – WalkMe account ID
  • TicksSince – Time of the play (with some hash)
  • stepStatus –  The current status of the step (shown/clicked next etc.)
  • playInitiator – How the play was started – Widget/AutoStart/Launcher etc.
  • source – Whether the snippet is production or test. 0 – production, 3 – test.
  • customFieldsSerialized – Some custom fields used for analytics. Can be controlled from API.
  • browser – Browser type and version
  • os – Operation system
  • domain – The domain of which the request is coming from
  • permutationId – only relevant in case AbTesting is activated. otherwise always -1.
  • endUserGuid – A generated GUID to identify the user uniquely, does not tell us any information about the user
  • _ – A jQuery functionality to avoid files caching. The current date is added to this parameter.

 

 

Was this article helpful?

Related Articles