Skip to content

Integrating SailPoint with WebEngage

WebEngage is a customer engagement platform that enables organizations to track users, manage campaigns, and analyze user behavior. It provides APIs to access internal users (team members), roles, and customer data. This document provides instructions to configure a new direct connection to a WebEngage source. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The WebEngage connector supports the following:

Account Management

  • Aggregate Team Members

Entitlement Management

  • Aggregate Roles

Important

Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:

  • Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
  • Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.

These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

Prerequisites

Ensure the following prerequisites are met before proceeding with the configuration:

  • Access to an active WebEngage account.
  • The Base URL for WebEngage APIs. For example, https://api.webengage.com/v2.
  • A Service Account created in WebEngage.
  • Valid Service Account credentials (API key or token).

  • The Account ID for your WebEngage account.

    Note

    The Account ID used in API requests is the same as the License Code displayed in the WebEngage dashboard. Example Account ID (from dashboard URL), https://dashboard.webengage.com/accounts/<ACCOUNT_ID>/...

Required Permissions

  • WebEngage supports API access using both Personal API Keys and Service Accounts. For more information, refer Getting Started in the WebEngage documentation.

    Important

    Personal API Keys are being deprecated. WebEngage recommends using Service Accounts, which provide a secure, non-human identity for integrations.