End User Update API Integration

Updated on December 5, 2019 Download PDFDownload as PDF
Download PDF

Brief Overview

End-User Update API is an Integration that allows you to call a customer-facing API to update end users’ attributes of a specific end-user. This can be used to send server-side update calls from any SaaS service that can send callbacks to an endpoint (i.e. URL).

This provides the ability to receive real-time updates to WalkMe’s End User Object, the integration set up allows you to identify the fields you want to import from any payload (whitelist) that will be stored in WalkMe’s end-user object and will later be available for filtering on Insights, reporting, and segmentation.

Incoming integrations are currently available for all WalkMe platforms except WalkMe Mobile.

Use Cases

  • Update WalkMe’s end-user object in real-time when a new end-user is registered.
  • Update WalkMe’s end-user object in real-time when an end-user upgrades from a free to a paying user – and having this data available for content segmentation evaluation.
  • Update WalkMe’s end-user object in real-time when a customer churns.
  • Set up a webhook in your CRM to update WalkMe’s end-user object whenever a customer reaches over $1M ARR and can be defined as a “premium customer”.

Creating an End User Update API Integration

Step 1 – Create a new End User Update API Integration

  1. Navigate to Insights
  2. Go to the Integrations tab (bottom left on the menu)
  3. Click on API to WalkMe – this will open up the integration wizard 

Step 2 – Define the Integration

  1. Give the Integration a Name – Notice this is the name that will be shown on the Editor’s Segmentation Center rule engine as well as on Insights so use a meaningful name.
  2. Provide the User Identifier Property – Enter the field that will hold the end-user identifier as identified in WalkMe – for example, if your selected End User Identifier method is a variable containing the end user’s email, the field entered should be the field in the payload JSON that will hold the end user’s email. If your payload is in a format of a JSON object use dot-separated names (<object name>.<field name>)
  3. Enter the Properties to Import – Enter the fields and their type from the payload JSON that you wish to Import into WalkMe. These are the fields that will be available for Segmentation, Filtering on Insights and Reporting. If your payload is in a format of a JSON object use dot-separated names (<object name>.<field name>).
  4. Click on Continue

Step 3 – Get Integration Endpoint and Test

  1. The integration now displays the endpoint to send your API request to.
  2. Copy this Endpoint to the service you are using to send WalkMe the requests
  3. Click on TEST INTEGRATION and send a sample test call to the endpoint copied in 2. The test results will be shown on the screen. If the Test failed, you will receive the reason.
Please Note:

The specified conditions are only evaluated on page load.

Using the End User Update API for Segmentation

  1. Once the Integration is set up – Perform an empty publish so you can segment based on the imported fields in your Editor.
  2. In WalkMe’s Editor, go to the Manage Segments Menu
  3. Create a new segment or edit an existing one
  4. In the rule engine – select group “user attributes” → select your integration name (given in Step 2- Define your Integration) → select the field from the list you wish to segment by
  5. Define your condition (notice the operators shown are defined by the type of the field you inserted in Step 2 – Define your Integration)
  6. Click Done

Using the End User Update API for Filtering Data in Insights 

  1. In Insights – create a new Filter or update an existing one.
  2. Select USER → Click on the field you imported in Step 2 – Define your Integration. Notice the descriptive text next to each field in the list since you can have multiple fields with the same name coming from several integrations
  3. Define your condition (notice the operators shown are defined by the type of the field you inserted in Step 2 – Define your Integration)
  4. Click Save Filter

Best practices

  1. When modifying an integration, changes will be updated immediately.
  2. Once the End User Update API is called – the End User object will be updated immediately. Keep in mind that the conditions are evaluated at every WM load, so if the end-user clicked on a button that is connected to a webhook sending this call (for example a button for upgrading the account) – the condition will only be re-evaluated on the next WM load (next page or refresh).
  3. Less is more – Be sensitive with the total number of attributes that you integrate to WalkMe. We allow a total of 30 attributes total across all incoming integrations.
  4. It is important to emphasize that unlike other Incoming Integrations, the End User Update API will only be updated once the API is called, and only for the specific End User that the API was called with.
  5. If you want to batch-set the attributes for all their end-users ahead of time, they can use the Incoming Integration – CSV Upload.
    In this case, please note that the 2 integrations will set 2 different attributes, so:

    1. The limitation of the 30 attributes is across all integrations – both the API and the Incoming batch integration – so if they have all fields in both that will decrease the actual limit to 15.
    2. In terms of rule definition for segmentation, they will have to build it with two rules and use an “OR” relation in between. For example:
      Incoming Integration customer type = ‘paying’ OR API integration customer type = ‘paying’.

 

Was this article helpful?

Related Articles