INinfobip
channels
mms
logs-and-status-reports-mms

Receive MMS tracking notifications

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 parameters when sending the MMS, or alternatively, configure it through 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 and tracking options.

postWebhookreceive-mms-tracking-notification

Payload

notificationTypestring

Tells the type of user event that took place. Possible events: CLICKED

recipientstring

Recipient of the message.

urlstring

The link the recipient has clicked.

sendDateTimeinteger

This is timestamp epoch millis when we received event for CLICK.

messageIdstring

The ID that uniquely identifies the message sent to the recipient.

bulkIdstring

The ID that uniquely identifies a list of messages. This is either defined by user in the request or auto generated.

callbackDatastring

The callback data sent through the callbackData field in your fully featured message.

applicationIdstring

Used when specifying an application in outbound send requests. It is also returned in notification events. For detailed usage, refer to the documentation.

entityIdstring

Used when specifying an entity in outbound send requests. It is also returned in notification events. For detailed usage, refer to the documentation.

Response

Your server returns this code if it accepts the callback.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.