WebEngage
Overview
The WebEngage Conversions API destination connector is intended to send conversion events from your workspace to WebEngage.
At this time, the connector can validate credentials during setup, but loading/syncing data is still in development. Attempting to run a sync will fail with an error indicating the destination loading is not yet implemented.
Setup
Before configuring the destination, gather the following from WebEngage:
- License Code (your WebEngage account identifier used in the API path)
- API Key (used as a Bearer token)
You’ll also need the Base URL for the WebEngage API you are targeting.
Authentication
This destination authenticates using:
- Bearer token authentication via your WebEngage API Key
During credential validation, the connector makes a request to:
GET {base_url}/v1/accounts/{license_code}/events
A successful response indicates the credentials are valid.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
base_url | string | Yes | Base URL for the WebEngage API (the connector will safely handle a trailing /). |
license_code | string | Yes | Your WebEngage account/license code used in the API path. |
api_key | string | Yes | WebEngage API key used as a Bearer token for authentication. |
Streams / Data model
This destination is designed to write events to the WebEngage Conversions API.
However, data loading is not yet available, so there are no supported streams/mappings to configure at this time.
Hashing and normalization
This destination connector does not currently expose field-level hashing controls in its public configuration.
Data contract
A stable, user-configurable data contract (required fields, supported event schema, and mappings) is not yet available because destination loading is still in development.