---
title: "Receive MMS tracking notifications"
method: POST
path: "receive-mms-tracking-notification"
tags: ["channels", "mms", "logs-and-status-reports-mms"]
---

# Receive MMS tracking notifications

`POST receive-mms-tracking-notification` (webhook)

For every message you send, we offer the option to send you clicked events. To enable this feature, you need to specify your endpoint URL in [tracking](https://www.infobip.com/docs/api/channels/mms/send-mms-messages) parameters when sending the MMS, or alternatively, configure it through [Subscriptions management](https://www.infobip.com/docs/cpaas-x/subscriptions-management). If you need assistance with this process, please contact support@infobip.com.<br/>Use this data to monitor user engagement, analyze campaign performance, and trigger automated workflows based on user interactions. For more details, visit our dedicated pages on [URL shortening](https://www.infobip.com/docs/url-shortening) and [tracking options](https://www.infobip.com/docs/url-shortening/tracking).

## Payload

- Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bUrlTrackingWebhook
  - `notificationType` string: Tells the type of user event that took place. Possible events: CLICKED
  - `recipient` string: Recipient of the message.
  - `url` string: The link the recipient has clicked.
  - `sendDateTime` integer: This is timestamp epoch millis when we received event for CLICK.
  - `messageId` string: The ID that uniquely identifies the message sent to the recipient.
  - `bulkId` string: The ID that uniquely identifies a list of messages. This is either defined by user in the request or auto generated.
  - `callbackData` string: The callback data sent through the callbackData field in your fully featured message.
  - `recipientInfo` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bRecipientInfo: Recipient information such as device type, OS, device name.
    - `deviceType` string: The type of device used by the recipient to do the user action.
    - `os` string: The type OS present in the device used by the recipient.
    - `deviceName` string: Device name of the action originating device.
  - `geoLocationInfo` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bGeoLocationInfoWrapper: Geolocation data such as Country and City.
    - `countryName` string: Country where the user action is recorded.
    - `city` string: City where the user action is recorded.
  - `applicationId` string: Used when specifying an application in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
  - `entityId` string: Used when specifying an entity in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).

## Acknowledgement `200`

Your server returns this code if it accepts the callback.

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)