Track Experience Events

This API tracks impressions (shown) and user interactions (clicked) for accurate experience reporting. To report an impression or click for your experience via API, use the following endpoint.

POST /experiences/events

cURL

Impression Existing User

curl --request POST \
  --url https://sdk-{dc}.moengage.com/v1/experiences/events \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --header 'MOE-APPKEY: <moe-appkey>' \
  --data '
{
  "elements": [
    {
      "customer_id": "<unique user identifier like email or phone number. Eg: [e-mail]>",
      "user_timezone_offset": 19800,
      "actions": [
        {
          "action": "MOE_PERSONALIZATION_MESSAGE_SHOWN",
          "moe_event_uuid": "aa886712-4537-47c1-b126-2686efda2e26",
          "event_time": 1725258666,
          "platform": "web",
          "attributes": {
            "cid": "66d55ae445921e4d35ae4368_F_T_WP_AB_2_P_0_AU_5A",
            "experience": "Test Server side experience",
            "moe_locale_id": "0",
            "moe_variation_id": "2",
            "audience_name": "All Users",
            "audience_id": "5A",
            "type": "Web Personalization"
          }
        }
      ]
    }
  ]
}
'

200

{
  "status": "success",
  "message": "Your request has been accepted and will be processed soon.",
  "req_id": "SKuSLFnX"
}

If you do not call this endpoint, your MoEngage analytics dashboard will show zero impressions and zero clicks, and campaign reporting will be empty.

Authorizations

Authorization · string · header · required

Authentication is done via Basic Auth. This requires a base64-encoded string of your credentials in the format 'username:password'.

• Username: Use your MoEngage workspace ID (also known as the App ID). You can find it in the MoEngage dashboard at Settings > Account > APIs > Workspace ID (earlier app id).
• Password: Use your API Key, which you can find within the Personalize tile.

Note: After you generate and save the Personalize API Key (SECRET KEY), DO NOT generate a new key unless there is a security breach. After you generate a different key and save it, API calls using the older key won't work.

For more information on authentication and getting your credentials, refer here.

Headers

MOE-APPKEY · string · required

This is the Workspace ID of your MoEngage account that must be passed with the request. You can find it in the MoEngage dashboard at Settings > Account > APIs > Workspace ID (earlier app id).

Example:

"Workspace ID"

Body

application/json

elements · object[]

Array of user-event objects. Each element represents one user. You can batch up to 100 users per request.

Maximum array length: 100

Show child attributes

Response

200

application/json

Success The event was accepted by the MoEngage ingestion pipeline.

Note on idempotency: Events are deduplicated using moe_event_uuid. On retry, reuse the same UUID from the original attempt — MoEngage will not double-count it. For a new event, always generate a fresh UUID.

status · string

Acknowledgement status, for example success.

message · string

Human-readable acknowledgement message.

req_id · string

Server-assigned request identifier. Include this when contacting support about a specific call.